dhclient fails to obtain the IP address from some WiFi networks

Nash Kaminski nashkaminski at gmail.com
Sat Mar 23 16:42:58 UTC 2019


It appears that you actually may have had an  address assigned, but then
had it removed ~30 seconds later when the interface was brought down by
wpa_supplicant.

Can you confirm the period of time that you checked and saw that you had no
address assigned?

Was it within the ~30 second window of time after these log lines were
printed, but before the next line, reporting the interface was brought down?

Mar 22 09:55:15 sw dhclient[3435]: New IP Address (wlan0): 10.99.52.90
Mar 22 09:55:15 sw dhclient[3436]: New Subnet Mask (wlan0): 255.255.255.0
Mar 22 09:55:15 sw dhclient[3437]: New Broadcast Address (wlan0):
10.99.52.255
Mar 22 09:55:15 sw dhclient[3438]: New Routers (wlan0): 10.99.52.1
Mar 22 09:55:16 sw dhclient[3440]: New Routers (wlan0): 10.99.52.1


- Nash

On Sat, Mar 23, 2019, 11:30 AM Christian <ctanghe at gmx.de> wrote:

>
> Hi,
> I have had a similar case last week with an old notebook, and learned that
> some network cards didn‘t support a feature called PMF - Protected
> Management Frames (ieee 802.11w-2009).
>
> So I disabled this ( more or less senseless, as the internet says) Feature
> on my fritzboxRouter and the card went online.
> --
>
> > Am 23.03.2019 um 11:07 schrieb Eugene Grosbein <eugen at grosbein.net>:
> >
> > 23.03.2019 1:31, Yuri wrote:
> >
> >> The laptop was getting the wifi connection right away, but dhclient was
> consistently failing to obtain the IP address.
> >>
> >>
> >> Here are the ktrace dumps of the dhclient process of two instances of
> such failure:
> >>
> >> * https://people.freebsd.org/~yuri/dump-dhclient-failure-1.txt
> >>
> >> * https://people.freebsd.org/~yuri/dump-dhclient-failure-2.txt
> >>
> >>
> >> The wifi driver was if_run.
> >>
> >>
> >> Can anybody tell why did dhclient fail?
> >
> > There was several important changes to dhclient not so long ago.
> > Please describe the case in detail, including exact branch and revision
> of your FreeBSD system
> > and relevant messages of "dmesg -a" output. And output of tcpdump too,
> if possible.
> >
> >
> > _______________________________________________
> > freebsd-net at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-net
> > To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>


More information about the freebsd-net mailing list