On 06/18/17 14:38, Christer Solskogen 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
What is the `host-name` that it claims to be invalid?
Jun 18 20:50:14 tugs dhclient[79331]: DHCPDECLINE on re2 Jun 18 20:50:14 tugs dhclient[79331]: No acceptable DHCPOFFERS received. Jun 18 20:50:14 tugs dhclient[79331]: No working leases in persistent database - sleeping. Jun 18 20:50:15 tugs dhclient[79331]: DHCPDISCOVER on re2 - interval 1 Jun 18 20:50:15 tugs dhclient[79331]: DHCPOFFER from 51.174.112.1 (00:02:00:01:00:01) Jun 18 20:50:15 tugs dhclient[79331]: lease declined: invalid host name in host-name Jun 18 20:50:15 tugs dhclient[79331]: DHCPDECLINE on re2 Jun 18 20:50:15 tugs dhclient[79331]: No acceptable DHCPOFFERS received. Jun 18 20:50:15 tugs dhclient[79331]: No working leases in persistent database - sleeping. Jun 18 20:50:16 tugs dhclient[79331]: DHCPDISCOVER on re2 - interval 1 Jun 18 20:50:16 tugs dhclient[79331]: DHCPOFFER from 51.174.112.1 (00:02:00:01:00:01) Jun 18 20:50:16 tugs dhclient[79331]: lease declined: invalid host name in host-name Jun 18 20:50:16 tugs dhclient[79331]: DHCPDECLINE on re2 and it continues like this... I installed isc-dhcp-client to see if the problem was my ISP but with that client it works.
