When using net-misc/dhcpcd-6.10.3 I can solicit an IPv4 address from my ISP: # dhcpcd wan0 wan0: soliciting a DHCP lease wan0: offered 132.147.80.xx from 172.16.3.36 wan0: leased 132.147.80.xx for 259200 seconds wan0: adding route to 132.147.80.0/24 wan0: adding default route via 132.147.80.1 forked to background, child pid 7657 When using net-misc/dhcpcd-6.11.0 I get truncated packet errors: # dhcpcd wan0 wan0: soliciting a DHCP lease wan0: truncated packet (295) from 132.147.80.1 wan0: truncated packet (295) from 132.147.80.1 wan0: probing for an IPv4LL address wan0: using IPv4LL address 169.254.79.81 wan0: adding route to 169.254.0.0/16 forked to background, child pid 6071
DHCP is a BOOTP extension BOOTP minimum size is 300 bytes, so your ISP isn't RFC compliant. Patch here fixes it: http://roy.marples.name/projects/dhcpcd/vpatch?from=ac4e95dcbdeba0ea&to=3fd740f3ed17e902
I've also observed this behaviour - using dhcpcd-6.11.0 results in a truncated packet and IPv4LL address being assigned, and downgrading to dhcpcd-6.10.3 assigns addresses correctly. I don't use IPv6 internally so don't know if that's affected.
If someone can get more information on #582808 then I'll make a new release. (In reply to Sam Jorna (wraeth) from comment #2) > I don't use IPv6 internally so don't know if that's affected. It isn't.
My network connections dhcp server is included in OpenWRT router with DD-WRT v3.0-r29621 giga (05/10/16) and I get the exactly same results as James Chew with dhcpcd 6.11.0 . Downgrading to 6.10.1 fixed my problem. Checking the dhcp transactions (bootp protocol) with wireshark show only packages larger than 300 bytes.
(In reply to Juho-Mikko Pellinen from comment #4) > Checking the dhcp transactions (bootp protocol) with wireshark show only > packages larger than 300 bytes. If you're suffering from this issue, then the BOOTP part of the message is less than 300 bytes. If you're seeing more then that is probably the IP (20 bytes) and UDP (8 bytes) headers. Depending on the software you're using to see the whole trace, you could also see the Ethernet header (14 bytes).
(In reply to Roy Marples from comment #5) > (In reply to Juho-Mikko Pellinen from comment #4) > > Checking the dhcp transactions (bootp protocol) with wireshark show only > > packages larger than 300 bytes. > > If you're suffering from this issue, then the BOOTP part of the message is > less than 300 bytes. > > If you're seeing more then that is probably the IP (20 bytes) and UDP (8 > bytes) headers. Depending on the software you're using to see the whole > trace, you could also see the Ethernet header (14 bytes). True. The Bootp -part of DHCP Offer is just 292 bytes. I just tested the 9999 -version of the application which contains the patch mentioned earlier and it is now working well.
(In reply to Roy Marples from comment #1) > Patch here fixes it: > http://roy.marples.name/projects/dhcpcd/ > vpatch?from=ac4e95dcbdeba0ea&to=3fd740f3ed17e902 Applying said patch fixes the issue.
I can confirm that, upstream bug. http://roy.marples.name/projects/dhcpcd/tktview?name=3f10c9b871
dhcpcd-6.11.1 is now in the tree; this should be fixed in that release.
