svn commit: r336203 - in head: contrib/wpa contrib/wpa/hostapd contrib/wpa/hs20/client contrib/wpa/patches contrib/wpa/src/ap contrib/wpa/src/common contrib/wpa/src/crypto contrib/wpa/src/drivers c...
Cy Schubert
Cy.Schubert at cschubert.com
Thu Jul 19 13:20:18 UTC 2018
In message <2f0ab2c2-b7cc-3dae-2d65-ea3c4a9515cb at daemonic.se>, Niclas
Zeising w
rites:
> [ sending this again since I missed the list the first time, apologies
> if anyone receives a duplicate ]
>
> On 07/19/18 13:57, Kyle Evans wrote:
> > On Thu, Jul 19, 2018 at 4:51 AM, Alexey Dokuchaev <danfe at freebsd.org> wrote
> :
> >> On Thu, Jul 19, 2018 at 11:48:03AM +0300, Andrey V. Elsukov wrote:
> >>> ...
> >>> Yesterday I updated my notebook (with iwm(4)) and also noticed that
> >>> wi-fi connection periodically breaks. /etc/rc.d/wpa_supplicant restart
> >>> wlan0 helps. After your message I reinstalled wpa_supplicant from old
> >>> source and now it works stable already about 2 hours.
> >>
> >> So, right now, we have broken wpa_supplicant(8) in -CURRENT? :-/
> >
> > Well, "broken". It's incredibly stable outside of rekeying events, and
> > further testing shows that I don't actually notice these disconnects
> > most of the time because it reassociates fast enough. I noticed it the
> > first time because apparently I had both SSIDs from my AP uncommented
> > in my wpa_supplicant.conf and it decided at that point to connect to
> > the other one, which took a little longer.
> >
> > Contrary to Andrey's report, though, I don't have to kick
> > wpa_supplicant at all. It will reassociate on its own every single
> > time.
>
>
> Hi!
> I have the exact same problem as Andrey, with the same driver. I've not
> investigated very much, but when using the 2.8 wpa_supplicant the wifi
> network dies after a little while, and I have to restart it (usually
> with /etc/rc.d/netif restart). Then it works for a little while, before
> going down again. With the old wpa_supplicant I didn't have this problem.
>
> I don't have very much else to add except noting that I'm affected as
> well. I haven't had time to debug it properly (which is why I've never
> reported it)
Do these events happen at regular intervals as Kyle experienced or
randomly?
What sort of key_mgmt do you connect with to your AP? Could it be
WPA-EAP?
--
Cheers,
Cy Schubert <Cy.Schubert at cschubert.com>
FreeBSD UNIX: <cy at FreeBSD.org> Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
More information about the svn-src-all
mailing list