Network problems (wired and wireless) after upgrading to Feisty
After upgrading to Feisty I've run into this problem where the network manager applet is constantly rotating with one green light. It does this even when trying to connect to my wired network. However I can still connect to the internet. Network-manager seems to reset the connection very frequently though, this is not an issue when connected to the wired network, but it asks me for the wireless password every minute or so.
Here's a snippet from my /var/log/syslog:
Apr 25 14:18:30 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:30 sacharya-laptop dhclient: There is already a pid file /var/run/
Apr 25 14:18:30 sacharya-laptop dhclient: killed old client process, removed PID file
Apr 25 14:18:30 sacharya-laptop dhclient: DHCPRELEASE on eth0 to 192.168.42.1 port 67
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IDHCP daemon state is now 14 (normal exit) for interface eth0
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IDHCP daemon state is now 14 (normal exit) for interface eth0
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^INo DHCP reply received. Automatically obtaining IP via Zeroconf.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop dhcdbd: message_handler: message handler not found under /com/redhat/
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IWill activate connection 'eth0'.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:32 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:32 sacharya-laptop dhclient: There is already a pid file /var/run/
Apr 25 14:18:32 sacharya-laptop NetworkManager: <information>
Apr 25 14:18:32 sacharya-laptop NetworkManager: <information>^IDHCP daemon state is now 12 (successfully started) for interface eth0
Apr 25 14:18:34 sacharya-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Apr 25 14:18:34 sacharya-laptop dhclient: DHCPOFFER from 192.168.42.1
Apr 25 14:18:34 sacharya-laptop dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Apr 25 14:18:35 sacharya-laptop dhclient: DHCPACK from 192.168.42.1
Apr 25 14:18:35 sacharya-laptop dhclient: bound to 192.168.42.104 -- renewal in 39006 seconds.
Apr 25 14:18:58 sacharya-laptop NetworkManager: <information>^IOld device 'eth0' activating, won't change.
Apr 25 14:20:11 sacharya-laptop NetworkManager: <information>
Apr 25 14:20:11 sacharya-laptop dhclient: There is already a pid file /var/run/
Apr 25 14:20:11 sacharya-laptop dhclient: killed old client process, removed PID file
Apr 25 14:20:11 sacharya-laptop dhclient: DHCPRELEASE on eth0 to 192.168.42.1 port 67
This cycle of the the dhcp transaction timeing out continues forever. However, as I said earlier, I can connect to the network while this is happening.
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Suraj Acharya
- Solved:
- Last query:
- Last reply: