Network connection failed after booting (Dapper 6.0.6)

[EdSpra]

On Dapper 6.0.6, my Ethernet comes up deactivated after booting. It is physically connected to my Router and should be able to receive an IP via DHCP.
Activating it in the Network Settings works after restarting my computer, but I think Ethernet should come up activated, given that it is the only interface I have configured.

[eswar (eswar-quanta)]

This happens with my Toshiba Satellite A80-154 laptop too. It has Marvell Yukon 88e8086 Fast ethernet controller. Moreover, i connect my system in office lan, so it has a static IP. And in many posts people mostly complain about DHCP and the network problems occur because of the DHCP. But this happens with static IP too. I actually upgraded from Breezy to Dapper, thru update manager. I never had this problem with Breezy. Since, I suspected that anything wrong might have happened during the upgradation, I checked with LIVE CDs, still the problem persists. And I tried installing XUbuntu on another partition just to check.. The network has the same problem!!

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[EdSpra (sprot)]

I have recently updated to UBUNTU 6.10 and in this version the bug is not
present.
But in UBUNTU 6.0.6 LTS it was still an issue.

Regards

2007/3/20, Brian Murray <email address hidden>:
>
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. You reported this bug a while ago and there hasn't been any
> activity in it recently. We were wondering is this still an issue for
> you? Thanks in advance.
>
> ** Changed in: Ubuntu
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>
> --
> Network connection failed after booting (Dapper 6.0.6)
> https://launchpad.net/bugs/54911
>

[Brian Murray (brian-murray)]

Based on your comment EdSpraDo regarding your updating to Edgy I would like to close this bug as we won't be able to get the information we need about Dapper.

eswar - are you still using dapper and is this an issue for you?

[Sjors Robroek (sjors)]

This is still a problem, at least for me. I've bought 2 new Dell desktop machines to test, so hopefully they can replace our old custom-built desktop machines. These machines are Dell optiplexes 745 with a broadcom onboard network (exact type unknown atm, uses the tg3 driver)

However, with our current Dapper installation (x86 and x64) we have this problem. After booting, /etc/init.d/networking hangs for a short while, afterwards no network interface is up.

However, the file /var/run/networking/ifstate still contains the following:

lo=lo
eth0=eth0

and as such, ifup -a won't bring up the network interfaces. ifup -a --force works as well, as does /etc/init.d/networking restart. However, doing ifup -a --force inside /etc/init.d/networking does not solve this problem.

I've never had this problem with any of our other machines, so it basically means we can't use these computers until feisty is released and production-quality.

[Brian Murray (brian-murray)]

Could you please add the contents of your '/etc/network/interfaces' file? Thanks in advance.

[Sjors Robroek (sjors)]

Pretty much default:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

[Sjors Robroek (sjors)]

This problem is dhcp3-client related. Setting a fixed ip-address in /etc/network/interfaces is a workaround, and installing pump fixes the problem, allowing me to use dhcp with these network controllers.
Is pump the default in edgy/festy by any chance, because dhcp-client has been causing so much trouble for me over the years it's no longer fun. If not, i would seriously be a proponent of making pump the default in some future release.

Thanks for the help anyways :)

[Philip Paquette (pcpaquette)]

Setting package to dhcp3, so this bug gets out of the list of bugs without a package.
Can you confirm this bug still happens in edgy/feisty?
You seem to say the bug is fixed, should I close it then or is it just a workaround?
Thanks.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Do you still have this issue with the latest stable release of Ubuntu ?

[Sjors Robroek (sjors)]

On our current testing desktops (running feisty) it seems to work.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you, I'm marking this as fixed.