Friday, January 04, 2019

Re: security/wpa_supplicant: Reassoc on NWID change

On 2019/01/04 23:43, Peter Hessler wrote:
> On 2019 Jan 04 (Fri) at 17:38:56 +0000 (+0000), Raf Czlonka wrote:
> :
> :Absolute silence when I move around - only when I move back near the AP,
> :the laptop associated with first, do I get this:
> :
> : $ route monitor
> : got message of size 192 on Fri Jan 4 17:28:11 2019
> : RTM_GET: Report Metrics: len 192, priority 12, table 0, ifidx 4, pid: 86459, seq -904765000, errno 0
> : flags:<UP,GATEWAY,DONE,STATIC>
> : fmask:
> : use: 42 mtu: 0 expire: 0
> : locks: inits:
> : sockaddrs: <DST,GATEWAY,NETMASK,IFP,IFA>
> : 0.0.0.0 gate.domain.example.com 0.0.0.0 ab:cd:ef:01:23:45 host.domain.example.com
> :
> :Apart from both FQDNs and the MAC address, nothing has been redacted.
> :
> :I'll be back here on Monday. Is there anything else I should try?
> :
> :Cheers,
> :
> :Raf
>
> Yes, can you turn on debug for the interface: ifconfig iwm0 debug
> (replace iwm0 with your actual wifi device if it is different).
>
> That will give a lot more output in the dmesg buffer, but also the
> results of channel scans and when it is looking for a new bssid to
> connect to.
>
> The kernel needs to select a new bssid to connect to, move to it, then
> this patch lets wpa_supplicant listen for those changes and react to
> them.

Probably obvious anyway but just checking... you haven't forced bssid
or chan via hostname.if / ifconfig have you?

No comments:

Post a Comment