I've no idea, bgscan is broken with atheros NICs because the driver still doesn't do background scan without dropping frames :( (one of many thing I'd love to fix, but life/time.) please do experiment though! I think wpa_supplicant's roaming logic would benefit from a lot more work. -adrian On Thu, 19 Sep 2019 at 15:21, Johannes Lundberg <johalun_at_freebsd.org> wrote: > > On 9/19/19 3:06 PM, Adrian Chadd wrote: > > So roaming in ifconfig/net80211 is what's set to manual. > > wpa_supplicant right now does RSSI threshold based roaming. All of the > roaming and network preferences when wpa_supplicant is running is done in > wpa_supplicant. That's where you have to look. Ideally wpa_supplicant would > be triggering bgscan too periodically rather than only when the RSSI is low. > > > > -adrian > > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert <cy.schubert_at_gmail.com> wrote: > >> On September 19, 2019 8:20:07 AM PDT, Adrian Chadd < >> adrian.chadd_at_gmail.com> wrote: >> >Roaming is done in wpa_supplicant when it's running.That's where the >> >smarts >> >need to be. :( >> > >> > >> > >> >-adrian >> > >> > >> >On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb >> ><bzeeb-lists_at_lists.zabbadoz.net> >> >wrote: >> > >> >> On 19 Sep 2019, at 12:28, Tom Jones wrote: >> >> >> >> Hi, >> >> >> >> freebsd-wireless might be a better list for all this .. >> >> >> >> >> >> > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp wrote: >> >> >> -------- >> >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477_at_FreeBSD.org> >> <707bcd3f-fa6b-82eb-fa8f-09c4b800f477_at_FreeBSD.org>, >> >> >> Johannes Lundber >> >> >> g writes: >> >> >> >> >> >>> For a long time now I have had this problem with iwm and wlan0. >> >> >>> Whenever >> >> >>> I move between work and home it won't reconnect automatically and >> >I >> >> >>> have >> >> >>> to do wlan0 scan manually for it to pick up the different >> >network. >> >> >> >> >> >> I suffer from the dreaded "reason=0" when I move inside my house: >> >> >> >> >> >> > scan >> >> >> OK >> >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 >> >(SSID='Palombia' >> >> >> freq=2452 MHz) >> >> >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0 >> >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> >> <3>Trying to associate with 6c:3b:6b:ab:ce:d4 >> >(SSID='Palombia' >> >> >> freq=2412 MHz) >> >> >> <3>Associated with 6c:3b:6b:ab:ce:d4 >> >> >> >> >> >> a2:e9 is the loudest AP here in my office, but my I have been in >> >the >> >> >> other end of the house iwn consistently fails to associate with it >> >> >> and >> >> >> and keeps picking the weaker AP in the far end. >> >> >> >> >> >> Eventually (hours!) it disconnects from the weaker ap, also with >> >> >> "reason=0" and gets it right: >> >> >> >> >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 >> >[GTK=CCMP] >> >> >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0 >> >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 >> >(SSID='Palombia' >> >> >> freq=2452 MHz) >> >> >> <3>Associated with 6c:3b:6b:3d:a2:e9 >> >> >> <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 >> >[PTK=CCMP >> >> >> GTK=CCMP] >> >> >> <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 >> >> completed >> >> >> [id=3 id_str=] >> >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 >> >[GTK=CCMP] >> >> >> >> >> >> And yes, working roaming would be nice too... >> >> > >> >> > I have the problem that when roaming networks become disabled >> >> > >> >> > $ wpa_cli >> >> > Selected interface 'wlan0' >> >> > >> >> > Interactive mode >> >> > >> >> > > list_networks >> >> > network id / ssid / bssid / flags >> >> > 0 network1 any [CURRENT] >> >> > 1 network2 any [DISABLED] >> >> > 2 network3 any [DISABLED] >> >> > 3 network4 any [DISABLED] >> >> > 4 network5 any [DISABLED] >> >> > Selected interface 'wlan0' >> >> > >> >> > >> >> > I address this by doing network_enable x in wpa_cli and it all >> >comes >> >> > back. I asked Adrian about this in the past, but it needs some >> >> > debugging >> >> > to pin down. >> >> >> >> >> >> Is this iwm(4) as well in your case or another card? >> >> >> >> /bz >> >> _______________________________________________ >> >> freebsd-wireless_at_freebsd.org mailing list >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> >> To unsubscribe, send any mail to >> >"freebsd-wireless-unsubscribe_at_freebsd.org >> >> " >> >> >> >_______________________________________________ >> >freebsd-current_at_freebsd.org mailing list >> >https://lists.freebsd.org/mailman/listinfo/freebsd-current >> >To unsubscribe, send any mail to >> >"freebsd-current-unsubscribe_at_freebsd.org" >> >> With wpa_supplicant running roaming is set to manual. Bgscan should be >> enabled. >> >> At home we have two n (and 2 g) wifi networks. When powering off one ap >> it connects to the other (in addition to using lagg to failover from >> ethernet to wifi and back). >> >> Your wpa_supplicant should contain each ssid you intend to use. A >> wildcard can be used for open networks. >> >> It's a while since I've tested this functionality but I can test again >> when I get home tonight. >> >> >> -- >> Pardon the typos and autocorrect, small keyboard in use. >> Cheers, >> Cy Schubert <Cy.Schubert_at_cschubert.com> >> FreeBSD UNIX: <cy_at_FreeBSD.org> <cy_at_FreeBSD.org> Web: >> http://www.FreeBSD.org >> >> The need of the many outweighs the greed of the few. >> > > Hmm so in other words, you have to set bgscan for each network entry you > want roaming? What are some good values for this? > > >Received on Thu Sep 19 2019 - 20:30:39 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:21 UTC