On Mon, Jun 19, 2017 at 10:11 AM, Stuart Henderson <[email protected]> wrote:
> On 2017-06-18, Christer Solskogen <[email protected]> wrote: > > I'm running the latest snapshot, and I suspect that there is something > > wrong with dhclient. > > (or at least, that is the symptom) > > > > > > Jun 18 20:50:14 tugs dhclient[79331]: DHCPDISCOVER on re2 - interval 1 > > Jun 18 20:50:14 tugs dhclient[79331]: DHCPOFFER from 51.174.112.1 > > (00:02:00:01:00:01) > > Jun 18 20:50:14 tugs dhclient[79331]: lease declined: invalid host name > in > > host-name > > Please capture the packets: > > tcpdump -ni re2 -vvs1500 -X port bootps or bootpc > > > I've got this from Kenneth R Westerback: "This would indicate that the DHCP option 12 (host-name) has a value that is not a invalid DNS domain name. It appears I inadvertantly made this a fatal error in recent changes, which it probably wasn't before. i.e. the same error should be in your logs from before the latest snapshot, but the lease was accepted. I will check this out. Thanks."
