On Thu, Dec 03, 2015 at 04:26:20PM +0100, Andreas Kurth wrote: > after upgrading to 0.8.1 the dhclient command line changed to > > "dhclient -v -pf /run/dhclient.eth1.pid -lf > /var/lib/dhcp/dhclient.eth1.leases \ > -I -D LLT -df /var/lib/dhcp/dhclient6.eth1.leases eth1" > > Because of the "-D LLT" argument dhclient is unable to retrieve an IP4 > address, at least in my environment. When I run the exact same command > omitting the "-D LLT" argument everything works fine and IP6 as well > as IP4 addresses can be acquired. Also, downgrading to 0.7.54 fixes > the problem, since the dhclient command line looks like this then: > "dhclient -v -pf /run/dhclient.eth1.pid -lf > /var/lib/dhcp/dhclient.eth1.leases eth1". > > I don't understand exactly what the -D option does, but it leads to an > unusable system with unconfigured network interface and no nameserver > in resolv.conf. > > Please let me know if you need additional information to track down > this issue.
It would be great if you could tell me which DHCP server is running on
your network, or the make and model of your gateway device.
Also, if you could capture the packets exchanged while dhclient runs on
eth1 with tcpdump, that would be very helpful. Use this command:
tcpdump -i eth1 -w dhclientdump.pcap
After testing on several networks, I thought the -D LLT option would be
safe even if the server didn't support it, but apparently that's not the
case. I'll turn it into an option which is off by default, at least
until dhclient is resilient enough to handle servers that don't like it.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@debian.org>
signature.asc
Description: Digital signature
