Need to manually ifup eth0 in feisty

[Christian Convey]

When I boot my feisty computer, the network doesn't appear to be initially up. This is evident because (a) the NetworkManager Applet shows no network connection and (b) programs like firefox / apt-get can't access the Internet.

All I need to do after booting is either of the following:
- In the NM applet, click on "Wired Network", or
- run "sudo ifdown eth0 && sudo ifup eth0"

I had no network problems under Edgy (that I recall), but I did do a clean re-install to get Feisty.

[Christian Convey (christian-convey)]

Output of uname -a:
Linux pascal 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

[Robert Collins (lifeless)]

NM had problems late last week, that are meant to be resolved. What version of network-manager do you have installed ?

[Christian Convey (christian-convey)]

0.6.4, which seems to be the current one on the repositories.

On 4/16/07, Robert Collins <email address hidden> wrote:
> NM had problems late last week, that are meant to be resolved. What
> version of network-manager do you have installed ?
>
> --
> Need to manually ifup eth0 in feisty
> https://bugs.launchpad.net/bugs/107123
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Stefan Pauwels (stefan-pauwels-ch)]

I can confirm this bug, although I did an upgrade from Edgy to Feisty, not a clean reinstall. Can I add some output here that could help whomever is fixing this?

[James Arentsen (j-arentsen)]

I have the same problem. A clean install of Feisty - every time I boot my box, no network connection. Selecting 'Wired Network' in network-manager starts a network connection without any problems.

[mike2357 (mike2357)]

It appears that since eth0 is not activated when the computer boots, firestarter fails to automatically start. I think this indicates that this problem is more than just an inconvenience; it is a security issue.

[Stefan Pauwels (stefan-pauwels-ch)]

As soon as I apt-get remove network-manager I don't have any network problems anymore. It's just up after booting.

[Yatin Mirakhur (ymirakhur)]

I agree. It seems to be that the networkManager service seems to disable that network connection at startup. I use kubuntu, so have KDE's knetworkmanager, which has no way to set a "preferred" network of any kind. Perhaps adding a feature that involved a "preferred" network, then this wouldn't be a problem.

A very convenient work around is to remove network-manager and knetworkmanager. It works flawlessly, unless of course you need some kind of network management software b/c you have a wireless network or multiple wired networks.

[shanen (Shannon Jacobs) (shanen)]

I suspect this is the same problem I discovered yesterday on a clean install directly to Feisty from the CD. The easiest work around I've found seems to be to just right click on the menu bar network connection icon (near the clock) and disable the network, then enable it again. Sometimes I have to do it more than once, but once it connects, things seem to be fine after that.

The new machine is a Sharp WA70. I've done about a dozen Ubuntu machines so far, and this is the first time I've seen this problem, but it's also the first time I've done a Sharp notebook. (Is there some place I should report the various minor problems I had to overcome along the way? This network thing is the only major unresolved one.)

[Alexander Sack (asac)]

can you please test if this is still an issue in latest gutsy? If you don't have a chance to upgrade, please test the livecd.

[Alexander Sack (asac)]

we don't touch any interface configured in /etc/network/interfaces with network-manager anymore. This should fix this bug because it was most likely a side effect mixing ifupdown with network-manager.

If you still see this with network-manager 0.6.5-0ubuntu14 or later, please reopen.