Date: Sat, 23 Mar 2019 09:57:26 -0700 From: Yuri <yuri@rawbw.com> To: Nash Kaminski <nashkaminski@gmail.com>, Christian <ctanghe@gmx.de> Cc: freebsd-net@freebsd.org Subject: Re: dhclient fails to obtain the IP address from some WiFi networks Message-ID: <90b207c1-1ad9-0f97-1144-9616b3f5c61c@rawbw.com> In-Reply-To: <CAEF9=Z5Xt51KW2Ggn0G3EvWm1Nmaax=DEGGAnHpUNSWJA%2BAwnQ@mail.gmail.com> References: <1718f323-6c12-9a4c-ca70-11bd15cbb7c5@rawbw.com> <c6cf454e-2578-0afe-e6bf-58a760d82434@grosbein.net> <EBA8C733-16FE-4DBE-AB46-4D20C48A12DE@gmx.de> <CAEF9=Z5Xt51KW2Ggn0G3EvWm1Nmaax=DEGGAnHpUNSWJA%2BAwnQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/23/19 9:42 AM, Nash Kaminski wrote: > > Can you confirm the period of time that you checked and saw that you > had no address assigned? I was checking continuously, wpa_gui maybe showed the IP briefly once or twice, but then it would disappear. wpa_gui is also quite sloppy, and doesn't show the IP address right away for some reason. The problem might also be that the IP address gets reset too quickly, not sure. I can go back there in a week or so, and do some more experimentation. But I'm not sure how to capture the essence of the problem. tcpdump? wireshark? ktrace at the wpa_supplicant supplicant level instead? Can wpa_supplicant write an exhaustive log of what's going on? Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90b207c1-1ad9-0f97-1144-9616b3f5c61c>