Date: Sat, 23 Mar 2019 11:42:43 -0500 From: Nash Kaminski <nashkaminski@gmail.com> To: Christian <ctanghe@gmx.de> Cc: freebsd-net@freebsd.org, Yuri <yuri@rawbw.com> Subject: Re: dhclient fails to obtain the IP address from some WiFi networks Message-ID: <CAEF9=Z5Xt51KW2Ggn0G3EvWm1Nmaax=DEGGAnHpUNSWJA%2BAwnQ@mail.gmail.com> In-Reply-To: <EBA8C733-16FE-4DBE-AB46-4D20C48A12DE@gmx.de> References: <1718f323-6c12-9a4c-ca70-11bd15cbb7c5@rawbw.com> <c6cf454e-2578-0afe-e6bf-58a760d82434@grosbein.net> <EBA8C733-16FE-4DBE-AB46-4D20C48A12DE@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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@gmx.de> wrote: > > Hi, > I have had a similar case last week with an old notebook, and learned tha= t > some network cards didn=E2=80=98t support a feature called PMF - Protecte= d > Management Frames (ieee 802.11w-2009). > > So I disabled this ( more or less senseless, as the internet says) Featur= e > on my fritzboxRouter and the card went online. > -- > > > Am 23.03.2019 um 11:07 schrieb Eugene Grosbein <eugen@grosbein.net>: > > > > 23.03.2019 1:31, Yuri wrote: > > > >> The laptop was getting the wifi connection right away, but dhclient wa= s > 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@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEF9=Z5Xt51KW2Ggn0G3EvWm1Nmaax=DEGGAnHpUNSWJA%2BAwnQ>