Intrepid fresh installation DHCP negotiation problem

[Olof Staffans]

I recently tried to install the beta version of intrepid (on a fresh partition). The installation went fine, but when I boot intrepid it cannot find the internet.

[Martin Pitt (pitti)]

Can you please open a Terminal window and copy&paste the output of this command:

  ifconfig

and attach /var/log/kern.log?

Thank you!

[Jem (jem-mawson)]

I too had this problem for several weeks. It has now gone away. When it happened to me I would:

sudo /etc/init.d/networking restart

This would enable networking until next reboot. Is this a similar situation to yours?

[Olof Staffans (olof-staffans)]

Dear Martin,

I will do so when I get back home to that computer, which happens only
next week-end.

I forgot to say that the intrepid beta DVD has no problems to find the
internet when it starts up. It is the version that is installed on the
hard disk that cannot find the internet.

Olof

Martin Pitt wrote:
> Can you please open a Terminal window and copy&paste the output of this
> command:
>
> ifconfig
>
> and attach /var/log/kern.log?
>
> Thank you!
>
> ** Changed in: apport
> Status: New => Invalid
>
> ** Also affects: ubuntu
> Importance: Undecided
> Status: New
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>

[Olof Staffans (olof-staffans)]

Dear Martin,

I enclose the data that you requested as two attachments. When I run
the ifconfig from an older kernel which has no problems to find the
internet I get the following output

eth0 Link encap:Ethernet HWaddr 00:13:d4:7f:1a:4d
           inet addr:192.168.1.51 Bcast:255.255.255.255 Mask:255.255.255.0
           inet6 addr: fe80::213:d4ff:fe7f:1a4d/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
           RX packets:1066 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1215 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:400401 (391.0 KB) TX bytes:176898 (172.7 KB)
           Interrupt:17

lo Link encap:Local Loopback
           inet addr:127.0.0.1 Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING MTU:16436 Metric:1
           RX packets:305 errors:0 dropped:0 overruns:0 frame:0
           TX packets:305 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:9409 (9.1 KB) TX bytes:9409 (9.1 KB)

Olof

Olof Staffans wrote:
> Dear Martin,
>
> I will do so when I get back home to that computer, which happens only
> next week-end.
>
> I forgot to say that the intrepid beta DVD has no problems to find the
> internet when it starts up. It is the version that is installed on the
> hard disk that cannot find the internet.
>
> Olof
>
> Martin Pitt wrote:
>> Can you please open a Terminal window and copy&paste the output of this
>> command:
>>
>> ifconfig
>>
>> and attach /var/log/kern.log?
>>
>> Thank you!
>>
>> ** Changed in: apport
>> Status: New => Invalid
>>
>> ** Also affects: ubuntu
>> Importance: Undecided
>> Status: New
>>
>> ** Changed in: ubuntu
>> Status: New => Incomplete
>>
>

[Olof Staffans (olof-staffans)]

I tried, but it does NOT help.

Olof

Jem wrote:
> I too had this problem for several weeks. It has now gone away. When it
> happened to me I would:
>
> sudo /etc/init.d/networking restart
>
> This would enable networking until next reboot. Is this a similar
> situation to yours?
>

[Martin Pitt (pitti)]

Thank you. From the kernel log and ifconfig I see that the Ethernet device is detected properly, but it wasn't configured (no IP, etc.). I tentatively assign it to network-manager, but I think I need some further information now.

Did you log into this system locally and start a GNOME session, or did you do something else? (Remote login through ssh, or text mode login, etc.). Can you please do a clean boot and then attach /etc/network/interfaces and /var/log/daemon.log?

Thank you!

[Alexander Sack (asac)]

this most likely is a dupe of bug 289466 ... clean your /etc/network/interfaces from configurations if you want NM to use that.

[Olof Staffans (olof-staffans)]

I logged in locally and started a KDE session (it is the kubuntu
version). I enclose the file that you requested from the same boot that
I made yesterday.

Olof

Martin Pitt wrote:
> *** This bug is a duplicate of bug 289466 ***
> https://bugs.launchpad.net/bugs/289466
>
> Thank you. From the kernel log and ifconfig I see that the Ethernet
> device is detected properly, but it wasn't configured (no IP, etc.). I
> tentatively assign it to network-manager, but I think I need some
> further information now.
>
> Did you log into this system locally and start a GNOME session, or did
> you do something else? (Remote login through ssh, or text mode login,
> etc.). Can you please do a clean boot and then attach
> /etc/network/interfaces and /var/log/daemon.log?
>
> Thank you!
>
> ** Changed in: network-manager (Ubuntu)
> Sourcepackagename: None => network-manager
>

[Olof Staffans (olof-staffans)]

I also enclose the relevant part of the syslog.

Olof

Olof Staffans wrote:
> I logged in locally and started a KDE session (it is the kubuntu
> version). I enclose the file that you requested from the same boot that
> I made yesterday.
>
> Olof
>
> Martin Pitt wrote:
>> *** This bug is a duplicate of bug 289466 ***
>> https://bugs.launchpad.net/bugs/289466
>>
>> Thank you. From the kernel log and ifconfig I see that the Ethernet
>> device is detected properly, but it wasn't configured (no IP, etc.). I
>> tentatively assign it to network-manager, but I think I need some
>> further information now.
>>
>> Did you log into this system locally and start a GNOME session, or did
>> you do something else? (Remote login through ssh, or text mode login,
>> etc.). Can you please do a clean boot and then attach
>> /etc/network/interfaces and /var/log/daemon.log?
>>
>> Thank you!
>>
>> ** Changed in: network-manager (Ubuntu)
>> Sourcepackagename: None => network-manager
>>

[Olof Staffans (olof-staffans)]

I took a closer look at the syslog (and I enclose the relevant bit). The
DHSP negotiation goes well, until the device is supposed to be
activated, and then it every time looses the carrier, like this:

Nov 2 17:44:59 Lady NetworkManager: <info> Activation (eth0)
successful, device activated.
Nov 2 17:44:59 Lady NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) complete.
Nov 2 17:44:59 Lady NetworkManager: <info> (eth0): carrier now OFF
(device state 8)
Nov 2 17:44:59 Lady NetworkManager: <info> (eth0): device state
change: 8 -> 2
Nov 2 17:44:59 Lady NetworkManager: <info> (eth0): deactivating device.

Martin Pitt wrote:
> *** This bug is a duplicate of bug 289466 ***
> https://bugs.launchpad.net/bugs/289466
>
> Thank you. From the kernel log and ifconfig I see that the Ethernet
> device is detected properly, but it wasn't configured (no IP, etc.). I
> tentatively assign it to network-manager, but I think I need some
> further information now.
>
> Did you log into this system locally and start a GNOME session, or did
> you do something else? (Remote login through ssh, or text mode login,
> etc.). Can you please do a clean boot and then attach
> /etc/network/interfaces and /var/log/daemon.log?
>
> Thank you!
>
> ** Changed in: network-manager (Ubuntu)
> Sourcepackagename: None => network-manager
>

[Olof Staffans (olof-staffans)]

I do not understand in which sense this could possibly be a duplicate of
bug 289466. I run KDE, not gnome, and I have no problem whatsoever with
the applet.

My problem is connected with eth0 and the interplay between the kernel
and the network manager: As soon as the dhcp negotiation is ready and
the eth0 is supposed to be made public, somebody (the kernel?) decides
to shut down the port and start all over again. As a result, I have no
connection to the internet while running intrepid. See the enclosed
piece of the syslog.

My physical connection is the following: The eth0 port is connected to a
Zyxel homepna modem, which is then connected by telehpone wire to the
server in the basement of our 6 story house. It seems like the kernel
reset (that you find in the syslog) causes the Zyxel modem to go off
line, which then starts the process all over again.

Martin Pitt wrote:
> *** This bug is a duplicate of bug 289466 ***
> https://bugs.launchpad.net/bugs/289466
>
> Thank you. From the kernel log and ifconfig I see that the Ethernet
> device is detected properly, but it wasn't configured (no IP, etc.). I
> tentatively assign it to network-manager, but I think I need some
> further information now.
>
> Did you log into this system locally and start a GNOME session, or did
> you do something else? (Remote login through ssh, or text mode login,
> etc.). Can you please do a clean boot and then attach
> /etc/network/interfaces and /var/log/daemon.log?
>
> Thank you!
>
> ** Changed in: network-manager (Ubuntu)
> Sourcepackagename: None => network-manager
>

[Olof Staffans (olof-staffans)]

This problem has now been essentially resolved. I downloaded the newest
alternate intrepid i386 image, burned it to a CD-rom, and upgraded the
distribution from the CD-rom. After a restart I was able to access the
internet through eth0.

The word "essentially" above means the following: There is still
something strange going on in the connection: The first time that the
dhcp negotiation is finished and suppose to be activated the kernel
still resets the connection, and everything has to start all over again.
  However, now the second time succeeds. Before it went into an
indefinite loop.

Olof

Olof Staffans wrote:
> I do not understand in which sense this could possibly be a duplicate of
> bug 289466. I run KDE, not gnome, and I have no problem whatsoever with
> the applet.
>
> My problem is connected with eth0 and the interplay between the kernel
> and the network manager: As soon as the dhcp negotiation is ready and
> the eth0 is supposed to be made public, somebody (the kernel?) decides
> to shut down the port and start all over again. As a result, I have no
> connection to the internet while running intrepid. See the enclosed
> piece of the syslog.
>
> My physical connection is the following: The eth0 port is connected to a
> Zyxel homepna modem, which is then connected by telehpone wire to the
> server in the basement of our 6 story house. It seems like the kernel
> reset (that you find in the syslog) causes the Zyxel modem to go off
> line, which then starts the process all over again.
>
> Martin Pitt wrote:
>> *** This bug is a duplicate of bug 289466 ***
>> https://bugs.launchpad.net/bugs/289466
>>
>> Thank you. From the kernel log and ifconfig I see that the Ethernet
>> device is detected properly, but it wasn't configured (no IP, etc.). I
>> tentatively assign it to network-manager, but I think I need some
>> further information now.
>>
>> Did you log into this system locally and start a GNOME session, or did
>> you do something else? (Remote login through ssh, or text mode login,
>> etc.). Can you please do a clean boot and then attach
>> /etc/network/interfaces and /var/log/daemon.log?
>>
>> Thank you!
>>
>> ** Changed in: network-manager (Ubuntu)
>> Sourcepackagename: None => network-manager
>>