dhcpcd-discuss

Re: dhcp v4 set hostname clobbered by slaac

Roy Marples

Tue Apr 21 22:45:11 2020

On 21/04/2020 22:41, Mark Davies wrote:
Sorry for the delay replying - perils of trying to test something
remotely in a lockdown.   I made the change on a remote machine and
rebooted it and for some reason it didn't come back and I won't be able
to get in and see why for at least a week.  So rather than potentially
taking another remote machine out I had to reproduce the setup locally.

Having done that I can confirm that your patch works.  And yes I have
force_hostname set to true, because if I don't do that the hostname ends
up being "archlinux" always.

I ended up going with your patch here:
https://roy.marples.name/cgit/dhcpcd.git/commit/?id=92a4102beb58d5f3b2c6aead6039d37a5f6b2d95

force_hostname is a bad idea though.
During the arch install you probably clicked "ok" to a default hostname.
Check this: https://wiki.archlinux.org/index.php/Network_configuration#Set_the_hostname

Then you can remove the force_hostname option.

Roy

Follow-Ups:
Re: dhcp v4 set hostname clobbered by slaacMark Davies
References:
dhcp v4 set hostname clobbered by slaacMark Davies
Re: dhcp v4 set hostname clobbered by slaacRoy Marples
Re: dhcp v4 set hostname clobbered by slaacMark Davies
Archive administrator: postmaster@marples.name