https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280913
Bug ID: 280913
Summary: [patch] Unexpected state of vnet-jails with
ifconfig_DEFAULT="DHCP" in rc.conf(5)
Product: Base System
Version: 14.1-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: conf
Assignee: [email protected]
Reporter: [email protected]
Created attachment 252894
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252894&action=edit
auto-switch DHCP rc.conf(5) directive to SYNCDHCP if devd(8) won't take over
Generally, if user defines DHCP as ifconfig pseudo-argument in rc.conf(5),
devd(8) and /etc/devd/dhclient.conf handle the setup task.
But since /etc/rc.d/devd has "nojail" keyword defined, devd(8) won't run in any
jail, while /etc/rc.d/dhclient is meant to be allowed in vnet-enabled jails
since /etc/rc.d/dhclient got keyword nojail changed to nojailvnet.
This change doesn't have any effect unless user defines "SYNCDHCP" instead of
"DHCP" as pseudo-ifconfig argument in rc.conf(5), which seems to be not well
documented.
My suggestion is an auto-switch to SYNCDHCP behaviour (i. e. /etc/rc.d/netif
will run /etc/rc.d/dhclient).
This applies outside jails too, if user disabled devd(8) startup.
If DHCP pseudo-arg is configured in a vnet-jail (no nojailvnet), the
auto-switch to SYNCDHCP will do what user expects - without spending a lot of
time to discover the to some degree misleading SYNCDHCP option, imho.
I'm not aware of any negative impact this auto-switch could have.
--
You are receiving this mail because:
You are the assignee for the bug.
