Hi Denis, > Just FYI, there's definitely something funny with the scanning code: > > denkenz@iwd-test ~ $ sudo iw dev wlp2s0 scan flush > BSS 10:c3:7b:54:74:d4(on wlp2s0) > last seen: 274.815s [boottime] > freq: 5765 > beacon interval: 100 TUs > signal: -35.00 dBm > last seen: 349 ms ago > Information elements from Probe Response frame: > SSID: \x00\x00\x00\x00\x00\x00\x00\x00\x00 This is already rather strange to start with. Can you provide a sniffer capture of this situation? Thing is - the all-zero-bytes there points to using hidden SSID with a length of 9 characters, BUT * "myssid" is just 6 characters long - or did you edit that? * normally the zeroed-out SSID isn't transmitted in a *probe response* but only in beacons > Then if I try: > denkenz@iwd-test ~ $ sudo iw dev wlp2s0 scan flush ssid myssid > BSS 10:c3:7b:54:74:d4(on wlp2s0) > last seen: 319.667s [boottime] > freq: 5765 > beacon interval: 100 TUs > signal: -42.00 dBm > last seen: 350 ms ago > Information elements from Probe Response frame: > SSID: \x00\x00\x00\x00\x00\x00\x00\x00\x00 > .... > BSS 10:c3:7b:54:74:d4(on wlp2s0) > last seen: 319.662s [boottime] > freq: 5765 > beacon interval: 100 TUs > signal: -37.00 dBm > last seen: 355 ms ago > Information elements from Probe Response frame: > SSID: myssid > > Shouldn't the second scan give a single result from that one BSS? Well, depends what the AP sends you really. The "last seen" doesn't indicate that it's not flushed but rather that you got it again, so without seeing the sniffer I don't think we can really say what's going on. johannes
