Network Manager fails to bring up network in Intrepid

Bug #303056 reported by Russel Winder
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have just upgraded my Ubuntu boxes from Hardy to Intrepid. One of them appears to have a problem with NetworkManager -- the problem is new this machien worked fine with Hardy.

Booting happens fine (except for a NIS problem but that is for another report).

NetworkManager appears to start but fails to make any form of connection. Doing a grep on /var/log/syslog reveals that every 2 mins some form of action is being undertaken but the report is:

NetworkManager: <info> Trying to start the supplicant...
NetworkManager: <info> Trying to start the system setting daemon...

nm-tool indicates that eth0 has started correctly, it is just disconnected.

DHCP is working as all the other machines boot fine (as far as I can tell, at least they are connected to the network as they should be).

Revision history for this message
Russel Winder (russel) wrote :

Sorry I should note that this is a workstation that is failing not a laptop, it only has a wired conenction r8169 driver, and that my filestore is mounted over NFS so I cannot actually login except via a virtual terminal.

Revision history for this message
Russel Winder (russel) wrote :

If I kill NetworkManager and run:

sudo ifconfig eth0
sudo dhclient eth0

then the network starts fine.

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 303056] Re: Network Manager fails to bring up network in Intrepid

Russel Winder wrote:
> If I kill NetworkManager and run:
>
> sudo ifconfig eth0
> sudo dhclient eth0
>
> then the network starts fine.
>
>
did you configure your device in /etc/network/interfaces? if so, remove
your config from there.

 status incomplete

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Russel Winder (russel) wrote :

No, the /etc/network/interfaces file is the default:
{code}
auto lo
iface lo inet loopback

{code}
and has not been edited since the clean Hardy install.

The machine has just been switched on after it Christmas holiday and it behaved exactly the same: the network is not started on boot, I have to login and run dhclient (and also hostname) manually, then manually mount the filestores. After that everything is fine.

Revision history for this message
Victor Vargas (kamus) wrote :

Since this report have a long time without activity, could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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