On 2019-08-09 09:42:10 +0200, Beniamino Galvani wrote: > On Thu, Aug 08, 2019 at 06:07:41PM +0200, Vincent Lefevre wrote: > > On 2019-08-08 13:37:04 +0200, Michael Biebl wrote: > > > Bringing Vincent into the loop here. > > > > > > Vincent, can you gather the information Beniamino is asking for? > > > > > > Am 08.08.19 um 09:51 schrieb Beniamino Galvani: > > > > Would it be possible to capture a dump of DHCP packets for a success > > > > and for a failure? > > > > Each time after DHCP Request, there are 1 NAK packet (from 10.0.1.1) > > and 2 NAK packets (from 140.77.1.11 and 140.77.1.12), but not always ^^^ ACK
Grrr... I meant "ACK". Sorry. Being a bit tired... > > in the same order. > > > > With the internal DHCP client, this seems to be a success only if an > > ACK packet comes first. There is no such issue with the external one. By an ACK packet, I meant, one of the 2 packets from 140.77.1.*. > > Do you need more information? > > Could you capture DHCP packets with: > > tcpdump -i enp0s25 -s 0 -w dhcp.pcap udp port 67 or port 68 > > when using dhclient and the failing internal client, and attach the > files? dhcp-dhclient.pcap - using dhclient (success, though NAK came first) dhcp-int-failure.pcap - using the internal client (failures until I stopped the capture; ACK never came first) dhcp-int-success.pcap - using the internal client (success after several requests, once ACK came first) -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
dhcp-dhclient.pcap
Description: Binary data
dhcp-int-failure.pcap
Description: Binary data
dhcp-int-success.pcap
Description: Binary data