On Wed, Aug 07, 2019 at 05:00:01PM +0200, Michael Biebl wrote:
Full downstream bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933930
Hi, comparing a successful run to a failed one, the only difference visible from logs is that sometimes the server replies with a NAK instead of an ACK. Aug 07 14:06:14 <trace> [1565179574.0438] libsystemd: DHCP CLIENT (0x1bf948fc): OFFER Aug 07 14:06:14 <trace> [1565179574.0439] libsystemd: DHCP CLIENT (0x1bf948fc): received message was not an ACK, ignoring Aug 07 14:06:14 <trace> [1565179574.0439] libsystemd: DHCP CLIENT (0x1bf948fc): REQUEST (requesting) Aug 07 14:06:14 <trace> [1565179574.0441] libsystemd: DHCP CLIENT (0x1bf948fc): received message was not an ACK, ignoring Aug 07 14:06:14 <trace> [1565179574.0448] libsystemd: DHCP CLIENT (0x1bf948fc): NAK: requested address not available Aug 07 14:04:28 <trace> [1565179468.2149] libsystemd: DHCP CLIENT (0x299b0344): OFFER Aug 07 14:04:28 <trace> [1565179468.2150] libsystemd: DHCP CLIENT (0x299b0344): received message was not an ACK, ignoring Aug 07 14:04:28 <trace> [1565179468.2151] libsystemd: DHCP CLIENT (0x299b0344): REQUEST (requesting) Aug 07 14:04:28 <trace> [1565179468.2164] libsystemd: DHCP CLIENT (0x299b0344): ACK Aug 07 14:04:28 <trace> [1565179468.2417] libsystemd: DHCP CLIENT (0x299b0344): lease expires in 23h 59min 57s Aug 07 14:04:28 <trace> [1565179468.2418] libsystemd: DHCP CLIENT (0x299b0344): T2 expires in 20h 59min 58s Aug 07 14:04:28 <trace> [1565179468.2418] libsystemd: DHCP CLIENT (0x299b0344): T1 expires in 11h 59min 59s Would it be possible to capture a dump of DHCP packets for a success and for a failure? And also with dhclient (but perhaps this is not necessary). Do you know which DHCP server it is? Beniamino
-------- Weitergeleitete Nachricht -------- Betreff: Re: [Pkg-utopia-maintainers] Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works Datum: Wed, 7 Aug 2019 15:58:04 +0200 Von: Vincent Lefevre <vincent vinc17 net> An: Michael Biebl <biebl debian org> Kopie (CC): 933930 bugs debian org On 2019-08-07 12:57:37 +0200, Michael Biebl wrote:<thaller> mbiebl_, Unclear what is not working. Could you ask for level=TRACE logs? See https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28 , preferably without ratelimiting from journal (see also the comment)I've attached an archive with 3 log files of tests with the internal dhcp client: * nm-1.19.90-failing (with network-manager 1.19.90-2). I had to wait for more that one minute to get an IP address, and this was not even the correct one (I normally have a fixed IP address). Sometimes, this is worse, e.g. after each of the following reboots REBOOT in 1s REBOOT in 2s REBOOT in 4s REBOOT in 8s REBOOT in 16s REBOOT in 32s REBOOT in 1min 4s I got "NAK: requested address not available". I did not wait longer. * nm-1.19.90-working (with network-manager 1.19.90-2). I got the correct IP address (140.77.13.17) after 5 seconds. This is OK. * nm-1.20.0-failing (with network-manager 1.20.0-1). After each of the following reboots REBOOT in 1s REBOOT in 2s REBOOT in 4s REBOOT in 8s REBOOT in 16s REBOOT in 32s REBOOT in 1min 4s I got "NAK: requested address not available". I did not wait longer. I tried several times and could not make it work. Still no issues with dhcp=dhclient.
Attachment:
signature.asc
Description: PGP signature