Date: Tue, 17 Aug 2021 19:15:11 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 257229] net-mgmt/wifimgr with multiple Wi-Fi interfaces Message-ID: <bug-257229-7788-yDQRQmbrVH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257229-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-257229-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257229 --- Comment #16 from J.R. Oldroyd <fbsd@opal.com> --- Okay, I think it is the use of NOAUTO in the ifconfig_wlanN lines that was confusing wifimgr. It was looking for an associated network and, when none= was found, it was setting the GUI status to down, even though the interfaces we= re actually up. I have now added code to not look for associated networks, but to simply lo= ok at the interfaces' statuses when determining the GUI up/down status. New version is 1.17.11. By the way, I didn't answer your point about the delay before. The delay is due to waiting for the interface up command to complete. You can run "/etc/rc.d/netif start wlanN" and you will see the same delay. Once that command completes wifimgr does loop for up to 10s more waiting fo= r an associated network. However, in practice, this isn't needed as the interfa= ce will have associated before the "netif start" command returned. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257229-7788-yDQRQmbrVH>