Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Jul 2018 17:24:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 226260] dhclient tells me $if is not dhcp-enabled even though it is
Message-ID:  <bug-226260-227-2e2dj1ct9r@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-226260-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-226260-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226260

jpicalau+freebsd_bugzilla@elmandria.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jpicalau+freebsd_bugzilla@e
                   |                            |lmandria.com

--- Comment #1 from jpicalau+freebsd_bugzilla@elmandria.com ---
I just found this report while in the process of figuring out the same issu=
e. I
figure I should just as well provide some details and findings.

The reason why that configuration doesn't work when placed in
/etc/rc.conf.d/netif is that the service that handles dhcp is dhclient, whi=
ch
goes and look for its configuration in /etc/rc.conf.d/dhclient.

Now, both netif and dhclient will also load /etc/rc.conf.d/network.
(`load_rc_config network' in both of those services file). However, there i=
s a
comment against this loading line in /etc/rc.d/netif stating that this is
loaded for compatibility, which I interpret as meaning that it might not wo=
rk
forever.

It seems like there is a more general issue with the /etc/rc.conf.d/ mechan=
ism
not being well-suited for handling variables used in network.subr. Any rc
script including network.subr could start making use of a functionality that
depends on one of those variables in the future and result in breakage for
people having one of those set in /etc/rc.conf.d, but for another script. It
would be good to get some clarity here in order to avoid such unexpected
configuration issues.

In the meanwhile, I think it is prudent to use /etc/rc.conf for any variable
that ends up being "shared" between rc scripts in this fashion.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226260-227-2e2dj1ct9r>