Comment 6 for bug 94095

Hi Robert,
 My Feisty just got update few minutes ago (april 10). I rebooted and
the ethernet connection was not setup after reboot. I had to click again
on the small network applet in toolbar and select "Wired Connection".

I tried to change the config of the network interface in "Network
Settings" to enable Roaming mode. I rebooted and still the network
interface is not enabled after I logged in. So I disabled the "Roaming
mode", rebooted and did the following commands;

Immediately after reboot here is the state of my eth0;
$ sudo ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:2C:08:B9:02
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:46 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13852 (13.5 KiB) TX bytes:1216 (1.1 KiB)
          Interrupt:19 Base address:0x9800

Then I tried to bringup and got the following message;
$ sudo ifup eth0
ifup: interface eth0 already configured

Then I tried to bring down and bring back up and it worked;
$ sudo ifdown eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 4078
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
...

$ sudo ifup eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid
134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:50:2c:08:b9:02
Sending on LPF/eth0/00:50:2c:08:b9:02
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
DHCPOFFER from 192.168.0.175
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.175
bound to 192.168.0.100 -- renewal in 65270 seconds.

At that point the inerface is fine and up although the applet still
beleive the network interface is still off (this was expected).

Here is my interface file;
~$ sudo cat /etc/network/interfaces
# 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

iface eth0 inet dhcp

auto eth0

This bug is still not fixed.

Are you ok to re-open the bug?

Is there any test I can do on my machine or any files I need to check?

What should I do to re-open the bug, can we transition the bug from
fixed to non fixed. I guess the priority is at least medium if not high.

thanks
Steve

On Tue, 2007-10-04 at 15:28 +0000, Robert Clark wrote:
> This issue was apparently fixed through one of the feisty updates. I
> have not had any Ethernet configuration at startup up issues for over a
> week now.
>
> I consider this bug Fixed. Thanks Ubuntu Team!
>