Ubuntu
network-manager package

[Hardy] Network manager failing in roaming mode

Bug #209280 reported by Brian Pontarelli
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

I have a single wired connection (eth0) that is set to use roaming mode. NetworkManager starts up fine when I log in but then begins to spin. It is trying to get a DHCP connection over and over. If I change the connection to not use roaming mode and just use DHCP it works fine. The error from my syslog looks like this (it is repeated many times over).

Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Will activate connection 'eth0'.
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Device eth0 activation scheduled...
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) started...
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Mar 30 10:16:17 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Mar 30 10:16:19 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
Mar 30 10:16:19 bpontarelli-desktop NetworkManager: <info> Couldn't send DHCP 'up' message because: name 'com.redhat.dhcp.OperationInProgress', message 'interface eth0 is being released. Please try again la
ter.'.
Mar 30 10:16:19 bpontarelli-desktop NetworkManager: <info> Activation (eth0) failure scheduled...
Mar 30 10:16:19 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Mar 30 10:16:19 bpontarelli-desktop NetworkManager: <info> Activation (eth0) failed.
Mar 30 10:16:19 bpontarelli-desktop NetworkManager: <info> Deactivating device eth0.

I'm also seeing something from dhcdbd:

Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <WARN> nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Will activate connection 'eth0'.
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Device eth0 activation scheduled...
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) started...
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <WARN> nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) failure scheduled...
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Activation (eth0) failed.
Mar 30 10:08:38 bpontarelli-desktop NetworkManager: <info> Deactivating device eth0.

I've attached my syslog for you to work with.

Revision history for this message
Brian Pontarelli (brian-pontarelli) wrote :
Revision history for this message
Brian Pontarelli (brian-pontarelli) wrote :

As it turns out this bug is slowly becoming a blocker. This is now happening even with roaming mode disabled, using DHCP or static IPs. My network is completely unstable and at random will stop working completely.

Revision history for this message
Brian Pontarelli (brian-pontarelli) wrote :

I'm managed to calm the networking stack by rebooting and then taking everything out of roaming mode and placing it into static IP addresses. The reboot was necessary because after these failures occurred the Network Management application kept telling me that I didn't have permissions to change the networking information. This seems like a related issue, but something else that should be investigated.

Revision history for this message
Kivech (kivech-deactivatedaccount) wrote :

I can confirm this bug. Switching to DHCP made my connection more stable, but in roaming my connection is more down than active.

On my other PC which runs Vista, the connection is noticeably faster and perfectly stable. They both use the same modem/router to access the internet.

Revision history for this message
Psykotik (linux-ikiru) wrote :

Confirming also this error log, even if I'm not really aware of its consequences on my network.

Revision history for this message
lusepuster (thoeger) wrote :

Confirming the problem that showed up today, never before. My wireless is useless in roaming mode. It works fine in OpenSuse on the same machine.

Revision history for this message
hopelessone (shanehill) wrote :

I too have this...The logs are HUGE...

internet keeps dropping out every 3-4mins...very annoying when you got a P2P applications...

How did you set the eth0 to DHCP?

Thanks

Revision history for this message
hopelessone (shanehill) wrote :

OK fixed...

Revision history for this message
Graham Patterson (grahampatterson) wrote :

I can confirm this bug after upgrading my ThinkPad T60 (no wired connection, wireless on wlan0) from Gutsy to Hardy. With Gutsy, everything was fine. Now with Hardy, when I boot with Network Manager in roaming mode, it tries and fails repeatedly to get a connection. However if I disable roaming mode, everything works fine. I have several other boxes running Gutsy, SuSE, XP and Vista, on all of which the wi-fi works perfectly.

Revision history for this message
Alexander Sack (asac) wrote :

you have another dhclient running while doing this. not sure what exactly could cause this, but some manual network configuration is surely a good bet. try to not configure anything manually ... only use network manager and all should work better.

If you still see this issue, reopen this bug and attach your /etc/network/interfaces as well as the _complete_ syslog taken directly _after_ reproducing this issue.

Changed in network-manager:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.