Re: hostname is being reset, killing net on reboot
On Saturday, January 22, 2022 5:13:59 AM EST tomas@tuxteam.de wrote:
> On Sat, Jan 22, 2022 at 04:38:04AM -0500, gene heskett wrote:
> > On Saturday, January 22, 2022 2:04:32 AM EST tomas@tuxteam.de wrote:
> [...]
>
> > > Once that part is flying, tackle names :)
>
> I stay still by this :)
>
> > But, I found, quite by serendipity, in the raspios version of
> > bullseye, a fix. Look at the bottom of /etc/dhcpdcp.conf,
>
> ^^^^^^^
>
> ...that one looks like a typo to me. On my (not quite standard, because
> I avoid systemd) Debian buster, there is a /etc/dhcp hierarchy, with a
> dhclient.conf, which gets into action whenever my machine requests an
> IP address (typically when I do "ifup foo", for foo in eth0 or wlan0.
>
> The host name does figure there: it goes out with the request, in case
> the DHCP server wants to take decisions based on that. No DHCP server I
> interact with takes notice, but they might.
>
> This is the only connection I see.
>
> That filename directly at top-level looks to me pretty raspi-specific.
> Is it configuring some DHCP server, or your client?
>
> Cheers
its for its own eth0 on the rpi4b. And I guess it is raspi specific. It
doesn't exist on this x86-64 bullseye install.
Last post Tomas, we are contaminating the archive and the fix I published
with further discussion.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: