Re: wlan can't discover known networks after relocating

2019-09-19 Thread Johannes Lundberg 


On 9/19/19 7:30 PM, Cy Schubert wrote:
> In message  om>
> , Johannes Lundberg writes:
>> --0875960592f275a3
>> Content-Type: text/plain; charset="UTF-8"
>> Content-Transfer-Encoding: quoted-printable
>>
>> Tested today with bgscan added. Didn=E2=80=99t connect to home network unti=
>> l I
>> manually run ifconfig wlan0 scan.
>> Again, this is with failover lagg.
> I use failover lagg too. I'm still at $JOB so no ethernet for my personal 
> FreeBSD laptop here, but that works as well, at home.
>
>> It did however realize I wasn't at the office anymore and the ssid =
>> field
>> was empty in ifconfig output. Sometimes it stays the same long after I
>> leave the network.
> Do you suspend/resume your laptop?
Not the last few months because iichid doesn't support it yet. I just
leave it on while going between work/home.
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Cy Schubert 
In message 
, Johannes Lundberg writes:
> --0875960592f275a3
> Content-Type: text/plain; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
>
> Tested today with bgscan added. Didn=E2=80=99t connect to home network unti=
> l I
> manually run ifconfig wlan0 scan.
> Again, this is with failover lagg.

I use failover lagg too. I'm still at $JOB so no ethernet for my personal 
FreeBSD laptop here, but that works as well, at home.

>
> It did however realize I wasn't at the office anymore and the ssid =
> field
> was empty in ifconfig output. Sometimes it stays the same long after I
> leave the network.

Do you suspend/resume your laptop?


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


>
>
> On Thu, Sep 19, 2019 at 18:25 Cy Schubert  wrote=
> :
>
> > In message <7938e5fa-67da-35fa-10d0-ee3004438...@freebsd.org>, Johannes
> > Lundber
> > g writes:
> > >
> > > 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 th=
> e
> > > > roaming and network preferences when wpa_supplicant is running is don=
> e
> > > > in wpa_supplicant. That's where you have to look. Ideally
> > > > wpa_supplicant would be triggering bgscan too periodically rather tha=
> n
> > > > only when the RSSI is low.
> > > >
> > > >
> > > >
> > > > -adrian
> > > >
> > > >
> > > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert  > > > > wrote:
> > > >
> > > > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> > > > mailto:adrian.ch...@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
> > > > > > > > >
> > > > >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 +, Poul-Henning Kamp
> > > > wrote:
> > > > >> >> 
> > > > >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.or=
> g
> > >,
> > > > >> >> 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=3D0" when I move inside m=
> y
> > > > house:
> > > > >> >>
> > > > >> >>  > scan
> > > > >> >>  OK
> > > > >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> > > > >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> > > > >(SSID=3D'Palombia'
> > > > >> >> freq=3D2452 MHz)
> > > > >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:3d:a2:e9
> > reason
> > > =3D0
> > > > >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> > > > >> >>  <3>Trying to associate with 6c:3b:6b:ab:ce:d4
> > > > >(SSID=3D'Palombia'
> > > > >> >> freq=3D2412 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=3D0" and gets it right:
> > > > >> >>
> > > > >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d=
> 4
> > > > >[GTK=3DCCMP]
> > > > >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:ab:ce:d4
> > reason
> > > =3D0
> > > > >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> > > > >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> > > > >(SSID=3D'Palombia'
> > > > >> >> freq=3D2452 MHz)
> > > > >> >>  <3>Associated with 6c:3b:6b:3d:a2:e9
> > > > >> >>  <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:=
> e9
> > > > >[PTK=3DCCMP
> > > > >> >> GTK=3DCCMP]
> > > > >> >>  <3>CTRL-EVENT-CONNECTED - Connection to
> > 6c:3b:6b:3d:a2:e9
> > > > >> completed
> > > > >> >> [id=3D3 id_str=3D]
> > > > >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e=
> 9
> > > >

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Johannes Lundberg 
Tested today with bgscan added. Didn’t connect to home network until I
manually run ifconfig wlan0 scan.
Again, this is with failover lagg.

It did however realize I wasn’t at the office anymore and the ssid field
was empty in ifconfig output. Sometimes it stays the same long after I
leave the network.


On Thu, Sep 19, 2019 at 18:25 Cy Schubert  wrote:

> In message <7938e5fa-67da-35fa-10d0-ee3004438...@freebsd.org>, Johannes
> Lundber
> g writes:
> >
> > 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  > > > wrote:
> > >
> > > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> > > mailto:adrian.ch...@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
> > > > > > >
> > > >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 +, Poul-Henning Kamp
> > > wrote:
> > > >> >> 
> > > >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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   network1any [CURRENT]
> > > >> >   1   network2 any[DISABLED]
> > > >> >   2   network3 any[DISABLED]
> > > >> >   3   network4 any[DISABLED]
> > > >> >   4   network5 any[DISABLED]
> > > >> >   Selected interface 'wlan0'
> > > >> >
> > > >> >
> > >

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Cy Schubert 
In message <7938e5fa-67da-35fa-10d0-ee3004438...@freebsd.org>, Johannes 
Lundber
g writes:
> 
> 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  > > wrote:
> >
> > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> > mailto:adrian.ch...@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
> > > > >
> > >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 +, Poul-Henning Kamp
> > wrote:
> > >> >> 
> > >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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-wirel...@freebsd.org
> >  mailing list
> > >>

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Adrian Chadd 
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  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  wrote:
>
>> On September 19, 2019 8:20:07 AM PDT, Adrian Chadd <
>> adrian.ch...@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
>> >
>> >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 +, Poul-Henning Kamp wrote:
>> >> >> 
>> >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.org>
>> <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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   network1any [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-wirel...@freebsd.org mailing list
>> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>> >> To unsubscribe, send any mail to
>> >"freebsd-wireless-unsubscr...@freebsd.org
>> >> "
>> >>
>> >___
>> >freebsd-current@freebsd.org mailing list
>> >https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> >To unsubscribe, send any mail to
>> >"freebsd-current-unsubscr...@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

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Johannes Lundberg 

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  > wrote:
>
> On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> mailto:adrian.ch...@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
> > >
> >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 +, Poul-Henning Kamp
> wrote:
> >> >> 
> >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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-wirel...@freebsd.org
>  mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> To unsubscribe, send any mail to
> >"freebsd-wireless-unsubscr...@freebsd.org
> 
> >> "
> >>
> >___
> >freebsd-current@freebsd.org 
> mailing list
> >https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >To unsubscribe, send any mail to
>

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Adrian Chadd 
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  wrote:

> On September 19, 2019 8:20:07 AM PDT, Adrian Chadd 
> 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
> >
> >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 +, Poul-Henning Kamp wrote:
> >> >> 
> >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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   network1any [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-wirel...@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> To unsubscribe, send any mail to
> >"freebsd-wireless-unsubscr...@freebsd.org
> >> "
> >>
> >___
> >freebsd-current@freebsd.org mailing list
> >https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >To unsubscribe, send any mail to
> >"freebsd-current-unsubscr...@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 
> FreeBSD UNIX:  Web: http://www.FreeBSD.org
>
> The need of the many outweighs the greed of the few.
>
___
freebsd-current@freebsd.org mailing list

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Cy Schubert 
On September 19, 2019 8:20:07 AM PDT, Adrian Chadd  
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
>
>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 +, Poul-Henning Kamp wrote:
>> >> 
>> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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   network1any [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-wirel...@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>> To unsubscribe, send any mail to
>"freebsd-wireless-unsubscr...@freebsd.org
>> "
>>
>___
>freebsd-current@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to
>"freebsd-current-unsubscr...@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 
FreeBSD UNIX:  Web: http://www.FreeBSD.org

The need of the many outweighs the greed of the few.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Adrian Chadd 
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 
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 +, Poul-Henning Kamp wrote:
> >> 
> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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   network1any [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-wirel...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org
> "
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Bjoern A. Zeeb 

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 +, Poul-Henning Kamp wrote:


In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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   network1any [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-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

2019-09-19 Thread Tom Jones 
On Tue, Sep 17, 2019 at 04:36:28PM +, Poul-Henning Kamp wrote:
> 
> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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   network1any [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.

- [tj]
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

2019-09-17 Thread Poul-Henning Kamp 

In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@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...

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"