Date: Mon, 26 Dec 2011 12:40:38 +0400 From: Eygene Ryabinkin <rea@freebsd.org> To: Doug Barton <dougb@FreeBSD.org> Cc: Pyun Yong-Hyeon <pyunyh@gmail.com>, d@delphij.net, Garrett Cooper <yanegomi@gmail.com>, Gleb Smirnoff <glebius@FreeBSD.org>, freebsd-rc@freebsd.org Subject: Re: Annoying ERROR: 'wlan0' is not a DHCP-enabled interface Message-ID: <KjrN1twOoYYUBTKZXsHphbGonrU@g5jH1yj%2BTnAiSdLOy3xs5Jutvhc> In-Reply-To: <4EF82E3B.6040601@FreeBSD.org> References: <n2Hlz4MXZMNcNzN56fSf6/or7Ig@YnbH/K3/Y1Z96RV2jTofcGuSPJI> <4EF6401E.3080902@FreeBSD.org> <20111224215649.GA12789@stack.nl> <4EF80CA7.3070303@FreeBSD.org> <ooDmUS7742YMCurT/5XDO19d%2BS4@g5jH1yj%2BTnAiSdLOy3xs5Jutvhc> <4EF82E3B.6040601@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--BZziOT8Kz25R/m/E
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Mon, Dec 26, 2011 at 12:20:11AM -0800, Doug Barton wrote:
> On 12/26/2011 00:17, Eygene Ryabinkin wrote:
> > The error message "'$ifn' is not a DHCP-enabled interface" is not
> > generated when $ifn is DHCP-enabled interface,
>=20
> That's precisely the failure I'm concerned about.
Doug, how that can be a failure? If dhclient will say "foo0 is not
a DHCP-enabled interface" when foo0 has DHCP activated, then it will
be a failure. But what you're saying now looks funny: do you really
insist that I should say "it is not a DHCP-enabled interface" for the
interface that is DHCP-enabled?
If dhclient would deny to say "DHCP configuration of '$ifn' failed" in
the case of quietstart, then it will be the failure. But my version
says the other thing "It is pointless to try DHCP on this interface,
because it is not DHCP-enabled". May be we should change "it is not a
DHCP-enabled" to "DHCP is not enabled on this interface", but what
you're saying contradicts either with logics or my understanding of
what "'$ifn' is not a DHCP-enabled interface" means to a native
speakers of English language.
My dusty magic ball tells me that you may be talking about the other
paragraph from my last mail,
{{{
The only way to miss the diagnostic message is to rely that devd will
configure your interface automagically while one forget to enable DHCP
on the interface he expect to automagificy. That's pity, but the lone
'service dhclient start $if' or 'service netif start $if' will reveal
the truth.
}}}
but then you're quoting the wrong part of my message.
Otherwise, please, clarify, what the failure is and how it can be
repeated.
> Also, can you please respond to the bit where I asked for
> configuration examples that produce the error?
OK, here we go:
{{{
ifconfig_msk0=3D"inet XXX.XXX.XXX.XXX/24 media autoselect"
}}}
but the bare
{{{
ifconfig_msk0=3D"up"
}}}
or 'ifconfig msk0 up' from the command-line will be sufficient:
we just need to generate the IFUP event for devd and interface should
be in the "up" state for that.
Boot up the system or have the booted one with at interface in the
"up" state, unplug the Ethernet cord once it is fully booted and plug
it back (to simulate link loss) and watch your /var/log/messages.
If you won't be able to simulate this using what I just said, I will
need the contents of your
- /etc/rc.conf (only interface configuration and things related
to devd and syslog)
- /etc/devd.conf
- /etc/syslog.conf
- /etc/rc.d/dhclient
--=20
Eygene Ryabinkin ,,,^..^,,,
[ Life's unfair - but root password helps! | codelabs.ru ]
[ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]
--BZziOT8Kz25R/m/E
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)
iF4EAREIAAYFAk74MwYACgkQFq+eroFS7PvCwgD/d0XCgbUTsfAIWQhdr7Tz6o1D
+swvHyeItwX4w+eDd5sA/RFUy6g085M0Jhs/dJw/y7t8TT37Nwqzg87EAQHzVqm7
=m5uR
-----END PGP SIGNATURE-----
--BZziOT8Kz25R/m/E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?KjrN1twOoYYUBTKZXsHphbGonrU>