From e5148d43ea4c5315fa939e0c8fa2852774ec330c Mon Sep 17 00:00:00 2001 From: patrick Date: Thu, 12 Aug 2021 12:31:40 +0000 Subject: [PATCH] One some access points we receive an unsolicited assoc status event directly after having successfully associated. In that case we should ignore the message, because otherwise we re-scan, re-associate and then get stuck in a loop. Ignoring the unsolicited assoc status even leads to a successful connection. Found by and ok gerhard@ --- sys/dev/ic/bwfm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sys/dev/ic/bwfm.c b/sys/dev/ic/bwfm.c index ea245574f62..a4af90501dc 100644 --- a/sys/dev/ic/bwfm.c +++ b/sys/dev/ic/bwfm.c @@ -1,4 +1,4 @@ -/* $OpenBSD: bwfm.c,v 1.84 2021/04/22 22:14:30 patrick Exp $ */ +/* $OpenBSD: bwfm.c,v 1.85 2021/08/12 12:31:40 patrick Exp $ */ /* * Copyright (c) 2010-2016 Broadcom Corporation * Copyright (c) 2016,2017 Patrick Wildt @@ -2464,7 +2464,7 @@ bwfm_rx_event_cb(struct bwfm_softc *sc, struct mbuf *m) if (ntohl(e->msg.status) == BWFM_E_STATUS_SUCCESS && ic->ic_state == IEEE80211_S_ASSOC) ieee80211_new_state(ic, IEEE80211_S_RUN, -1); - else + else if (ntohl(e->msg.status) != BWFM_E_STATUS_UNSOLICITED) ieee80211_begin_scan(ifp); break; case BWFM_E_DEAUTH: -- 2.20.1