Network Problem

freddy311082 · 2012-01-15 03:54:09

Hi to everyone...

I'm using KDE and I have a problem with mi networkmanager.

I have a laptop HP G62, and I'm connected to internet using a LAN connection. When I remove and put my network cable, the network manager dosen't recognize that the cable was set it again... after that, I had restarted the network manager manually (sudo rc.d restart networkmanager) and I had get the same result. For that reason, I stoped the networkmanager deamon and I was trying with the network deamon and nothing happened.

To have network connection again, I have to restart computer....

what can I do ???

somebody help me please !!!

best regards...

pyther · 2012-01-15 04:15:50

What network module are you using?

ewaller · 2012-01-15 04:20:30

sudo rc.d restart networkmanager)

That should be sudo /etc/rc.d/networkmanager restart.

To have network connection again, I have to restart computer....

Well, there are better ways than that, networkmanager not withstanding.
You could say sudo ifconfig eth0 up. If you are using dhcp, you might also need a sudo dhcpcd eth0

But, back to the networkmanager issue... When you disconnect then reconnect the cable, is there anything of interest at the end of the logs (dmesg or /var/log/everything.log)?
After you reconnect the cable, what is the output of ip addr ??
What client are you using to control networkmanager?
Are you configuring your network in /etc/rc.conf ?? (You might post it)
I've more questions, but let's start with those.

/dev/zero · 2012-01-15 04:26:13

I don't use network manager, but I expect the cable plug/unplug events will be handled by udev. Therefore, show us what happens when you try plugging and unplugging the cable while you also have this running in a terminal:

udevadm monitor

Also, telling us what sort of laptop it is doesn't help much. Laptops are just collections of parts, like any other computer, and I'm not going to google your laptop to find out what's inside. To let us know about your hardware, supply the following information:

lspci -nnmk | grep -i "network\|ethernet"

lsmod

Finally, is this a clean install or have you already been using it for a while?

Oh, btw, it's a good idea to demonstrate that you've already made some attempt to solve your problems without help. Eg, what have you googled? Does anything on the wiki or forums look similar but not quite the same? Keep in mind, this isn't your free personal help desk, we're just people who like Arch.

Edit: fixed typo edev -> udev.

Last edited by /dev/zero (2012-01-15 04:30:06)

freddy311082 · 2012-01-15 22:59:06

/dev/zero wrote:

I don't use network manager, but I expect the cable plug/unplug events will be handled by udev. Therefore, show us what happens when you try plugging and unplugging the cable while you also have this running in a terminal:
udevadm monitor
Also, telling us what sort of laptop it is doesn't help much. Laptops are just collections of parts, like any other computer, and I'm not going to google your laptop to find out what's inside. To let us know about your hardware, supply the following information:
lspci -nnmk | grep -i "network\|ethernet"
lsmod
Finally, is this a clean install or have you already been using it for a while?
Oh, btw, it's a good idea to demonstrate that you've already made some attempt to solve your problems without help. Eg, what have you googled? Does anything on the wiki or forums look similar but not quite the same? Keep in mind, this isn't your free personal help desk, we're just people who like Arch.
Edit: fixed typo edev -> udev.

For that:

lspci -nnmk | grep -i "network\|ethernet"

this is the answer:
02:00.0 "Network controller [0280]" "Ralink corp. [1814]" "RT5390 Wireless 802.11n 1T/1R PCIe [5390]" "Hewlett-Packard Company [103c]" "U98Z077.00 Half-size Mini PCIe Card [1636]"
03:00.0 "Ethernet controller [0200]" "Realtek Semiconductor Co., Ltd. [10ec]" "RTL8101E/RTL8102E PCI Express Fast Ethernet controller [8136]" -r02 "Hewlett-Packard Company [103c]" "Device [1426]"

udevadm monitor

this ddidn't show anything when I unplug and plug my network cable... what it's mean that the Archlinux dosen't know where I plug my network cable after I unpluged it...

Well, there are better ways than that, networkmanager not withstanding.
You could say sudo ifconfig eth0 up.  If you are using dhcp, you might also need a sudo dhcpcd eth0

I'm using DHCP, and after remove my cable, the command "sudo dhcpcd eth0" give the error "time out"...

That should be sudo /etc/rc.d/networkmanager restart.

sudo rc.d restart networmanager = sudo /etc/rc.d/networkmanager restart, and I had use the both way and nothing happend....

Finally, is this a clean install or have you already been using it for a while?

For that reasson I've reinstalled my computer 3 times... the last time was the last 10/01/2012 (one week ago)

I can't solve the problem.... help me please.... what do you think that I must to do ???

best regards

ewaller · 2012-01-15 23:04:18

ewaller wrote:

But, back to the networkmanager issue... When you disconnect then reconnect the cable, is there anything of interest at the end of the logs (dmesg or /var/log/everything.log)?
After you reconnect the cable, what is the output of ip addr ??
What client are you using to control networkmanager?
Are you configuring your network in /etc/rc.conf ?? (You might post it)

pyther · 2012-01-15 23:27:15

Are using the r8169 module by chance (it has had issue in the latest kernels)?

lsmod | grep r8169

What does /sys/class/net/eth0/operstate report when connected? Disconnected?

[root@tux ~]# cat /sys/class/net/eth0/operstate
up

Also what does ethtool show when connected? Disconnected?

ethtool eth0

I suspect networkmanager isn't at fault. I think there might be a hardware / software module issue. The above commands will tell us if the driver is detecting the link status correctly.

freddy311082 · 2012-01-16 13:13:32

Are using the r8169 module by chance (it has had issue in the latest kernels)?
[code]
lsmod | grep r8169
[/code]

yes, I'm using it

What does /sys/class/net/eth0/operstate report when connected? Disconnected?
[code]
[root@tux ~]# cat /sys/class/net/eth0/operstate
up
[/code]

when the cable is connected the answer is "up" and when the cable is disconnected the answer is "down".

Also what does ethtool show when connected? Disconnected?
[code]ethtool eth0[/code]

This is the resul when the cable is connected:
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes

And this is the result when the cable is disconnected:
Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available

I suspect networkmanager isn't at fault. I think there might be a hardware / software module issue. The above commands will tell us if the driver is detecting the link status correctly.

Well, i don't think that the problem is my hardware or something like that because I have Windows 7 installed too, and I don't have any problem with my network on Windows.

What client are you using to control networkmanager?

I'm using the Applet of Networmanager from KDE 4.7

But, back to the networkmanager issue...   When you disconnect then reconnect the cable, is there anything of interest at the end of the logs (dmesg or /var/log/everything.log)?

where the cable is connected the lasts lines in the log are:
Jan 16 07:53:23 localhost dhcpcd[3214]: version 5.2.12 starting
Jan 16 07:53:23 localhost NetworkManager[823]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Jan 16 07:53:23 localhost dhcpcd[3214]: eth0: rebinding lease of 10.30.131.150
Jan 16 07:53:26 localhost NetworkManager[823]: <info> WiFi now enabled by radio killswitch
Jan 16 07:53:26 localhost NetworkManager[823]: <info> (wlan0): bringing up device.
Jan 16 07:53:26 localhost kernel: [ 3544.131313] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 16 07:53:26 localhost NetworkManager[823]: <info> (wlan0): supplicant interface state: starting -> ready
Jan 16 07:53:26 localhost NetworkManager[823]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jan 16 07:53:26 localhost NetworkManager[823]: <info> (wlan0): supplicant interface state: ready -> inactive
Jan 16 07:53:33 localhost dhcpcd[3214]: eth0: broadcasting for a lease
Jan 16 07:53:33 localhost kernel: [ 3550.794956] eth0: no IPv6 routers present
Jan 16 07:53:34 localhost dhcpcd[3214]: eth0: offered 10.30.131.150 from 10.30.131.252
Jan 16 07:53:37 localhost dhcpcd[3214]: eth0: acknowledged 10.30.131.150 from 10.30.131.252
Jan 16 07:53:37 localhost dhcpcd[3214]: eth0: checking for 10.30.131.150
Jan 16 07:53:41 localhost dhcpcd[3214]: eth0: leased 10.30.131.150 for 3600 seconds
Jan 16 07:53:41 localhost NetworkManager[823]: <info> (eth0): DHCPv4 state changed preinit -> bound
Jan 16 07:53:41 localhost NetworkManager[823]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jan 16 07:53:41 localhost NetworkManager[823]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
Jan 16 07:53:41 localhost NetworkManager[823]: <info> address 10.30.131.150
Jan 16 07:53:41 localhost NetworkManager[823]: <info> prefix 24 (255.255.255.0)
Jan 16 07:53:41 localhost NetworkManager[823]: <info> gateway 10.30.131.252
Jan 16 07:53:41 localhost NetworkManager[823]: <info> nameserver '10.30.131.252'
Jan 16 07:53:41 localhost NetworkManager[823]: <info> domain name 'cbiomed.cu'
Jan 16 07:53:41 localhost NetworkManager[823]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jan 16 07:53:41 localhost NetworkManager[823]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Jan 16 07:53:41 localhost NetworkManager[823]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jan 16 07:53:42 localhost NetworkManager[823]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Jan 16 07:53:42 localhost NetworkManager[823]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
Jan 16 07:53:42 localhost NetworkManager[823]: <info> Activation (eth0) successful, device activated.
Jan 16 07:53:42 localhost NetworkManager[823]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jan 16 07:53:42 localhost dbus[797]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 16 07:53:42 localhost dbus[797]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

and when the cable is disconnected the lines are:

Jan 16 08:01:01 localhost /USR/SBIN/CROND[3250]: (root) CMD (run-parts /etc/cron.hourly)
Jan 16 08:01:05 localhost NetworkManager[823]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
Jan 16 08:01:05 localhost kernel: [ 4002.242548] r8169 0000:03:00.0: eth0: link down
Jan 16 08:01:05 localhost kernel: [ 4002.340708] r8169 0000:03:00.0: PME# enabled
Jan 16 08:01:10 localhost NetworkManager[823]: <info> (eth0): device state change: activated -> unavailable (reason 'carrier-changed') [100 20 40]
Jan 16 08:01:10 localhost NetworkManager[823]: <info> (eth0): deactivating device (reason 'carrier-changed') [40]
Jan 16 08:01:10 localhost dhcpcd[3214]: received SIGTERM, stopping
Jan 16 08:01:10 localhost dhcpcd[3214]: eth0: removing interface
Jan 16 08:01:10 localhost NetworkManager[823]: <info> (eth0): canceled DHCP transaction, DHCP client pid 3214
Jan 16 08:01:10 localhost dbus[797]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 16 08:01:10 localhost NetworkManager[823]: <warn> (pid 3214) unhandled DHCP event for interface eth0
Jan 16 08:01:10 localhost dbus[797]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

Are you configuring your network in /etc/rc.conf ??  (You might post it)

Yes, my network was configured in my rc.d... on my network we have a DHCP service

please help me, I had ansewred all of your quetions... please

ewaller · 2012-01-16 14:27:11

Okay, it looks like you are acquiring an address when you connect the cable (that would be 10.30.131.150) That is what ip addr would have told me, had you chosen to answer that question.

A 10.x.x.x network is a bit unusual. What type of network is it?
Can you ping 10.30.131.150? (your machine)
Can you ping 10.30.131.252? (Your gateway)
Can you ping 10.30.131.252? (Your Name server)

freddy311082 · 2012-01-16 15:44:07

yes, I can ping 10.30.131.252 and I can ping 10.30.131.150 when I am connected to my network, but that is not the problem... the problem is when I disconnect my network cable... that is the problem, because when I disconnect and connect again my network clable, the network dosen't restar automatically, and the networkmanager dosen't know that I had plugged again the network cable... that is the problem...

when I'm connected to my network everything work fine, the problem begin when I'm disconnected and try to connect again !!! that is the problem

pyther · 2012-01-16 17:22:06

This is the exact problem I have been having with the r8169 module.

1. Disable NM
2. ifconifg eth0 up
3. dhcpcd eth0 (do you get an ip)
4. Disconnect Ethernet
5. killall dhcpcd
6. Wait 30 seconds
7. Reconnect ethernet cable
8. dhcpcd eth0 (how about now)

Try this and report back.

I suspect you'll get an address the first time around, but the second time the dhcp request will fail.

Network Manager takes connect/disconnect messages from some system (udev possibly, I forget which). So if network manager isn't seeing the disconnect, it is likely the system isn't seeing the disconnect. I had this same exact problem on my thinkpad e420 laptop. Things have gotten better with the 3.1 and 3.2 kernels, but occasionally I'm forced to reboot my system to regain a connection.

Last edited by pyther (2012-01-16 17:33:56)

ewaller · 2012-01-16 20:43:41

I'm done. Good luck.

freddy311082 · 2012-01-17 15:39:58

pyther wrote:

This is the exact problem I have been having with the r8169 module.
1. Disable NM
2. ifconifg eth0 up
3. dhcpcd eth0 (do you get an ip)
4. Disconnect Ethernet
5. killall dhcpcd
6. Wait 30 seconds
7. Reconnect ethernet cable
8. dhcpcd eth0 (how about now)
Try this and report back.
I suspect you'll get an address the first time around, but the second time the dhcp request will fail.
Network Manager takes connect/disconnect messages from some system (udev possibly, I forget which). So if network manager isn't seeing the disconnect, it is likely the system isn't seeing the disconnect. I had this same exact problem on my thinkpad e420 laptop. Things have gotten better with the 3.1 and 3.2 kernels, but occasionally I'm forced to reboot my system to regain a connection.

I did everything what you told me and I've the same problem... my didn't knoe that my network cable was connected and the dhcp didn't give me an IP address...

what do you think now ??

Arch Linux

#1 2012-01-15 03:54:09

Network Problem

#2 2012-01-15 04:15:50

Re: Network Problem

#3 2012-01-15 04:20:30

Re: Network Problem

#4 2012-01-15 04:26:13

Re: Network Problem

#5 2012-01-15 22:59:06

Re: Network Problem

#6 2012-01-15 23:04:18

Re: Network Problem

#7 2012-01-15 23:27:15

Re: Network Problem

#8 2012-01-16 13:13:32

Re: Network Problem

#9 2012-01-16 14:27:11

Re: Network Problem

#10 2012-01-16 15:44:07

Re: Network Problem

#11 2012-01-16 17:22:06

Re: Network Problem

#12 2012-01-16 20:43:41

Re: Network Problem

#13 2012-01-17 15:39:58

Re: Network Problem

Board footer