Re: NM can't see WEP access point

[Dan Williams <dcbw redhat com>]

On Tue, 2016-06-07 at 16:09 +0200, Bastien Nocera wrote:
> Hey,
>
> iwlist scan as root shows:
>           Cell 17 - Address: 00:24:36:9D:3B:33
>                     Channel:11
>                     Frequency:2.462 GHz (Channel 11)
>                     Quality=70/70  Signal level=-32 dBm  
>                     Encryption key:on
>                     ESSID:"WEP test"
>                     Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6
> Mb/s
>                               9 Mb/s; 12 Mb/s; 18 Mb/s
>                     Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
>                     Mode:Master
>                     Extra:tsf=00000069f3b5fd9a
>                     Extra: Last beacon: 27430ms ago
>                     IE: Unknown: 00085745502074657374
>                     IE: Unknown: 010882848B960C121824
>                     IE: Unknown: 03010B
>                     IE: Unknown: 0706474220010D1E
>                     IE: Unknown: 2A0100
>                     IE: Unknown: 32043048606C
>                     IE: IEEE 802.11i/WPA2 Version 1
>                         Group Cipher : WEP-104
>                         Pairwise Ciphers (2) : CCMP TKIP
>                         Authentication Suites (1) : PSK
>                     IE: Unknown:
> 2D1A2C4017FFFF000000000000000000000000000000000000000000
>                     IE: Unknown:
> 3D160B001100000000000000000000000000000000000000
>                     IE: Unknown: 46050200010000
>                     IE: WPA Version 1
>                         Group Cipher : WEP-104
>                         Pairwise Ciphers (1) : TKIP
>                         Authentication Suites (1) : PSK
>                     IE: Unknown:
> DD180050F2020101070003A4000027A4000042435E0062322F00
>                     IE: Unknown: DD07000393016B0B20
>                     IE: Unknown: DD0E0017F207000101060024369D3B33
>                     IE: Unknown: DD0B0017F20100010100000007
>
> Which is a WEP access point created on an Airport Express gen 1
> device.
> "nmcli -f all device wifi | grep 'WEP test'" doesn't show anything
> related to that access point?
>
> Any ideas on how to debug this?

It depends if the supplicant has actually exposed it via D-Bus yet too.

Grab http://people.redhat.com/dcbw/wpas-list.py and sudo-run that with
the interface name of your wifi device, and see if the AP shows up in
that list.  It directly dumps out the supplicant's AP list in a more
readable form.  If the AP shows up there, but doesn't show up in
NetworkManager, then we need to enable NM debug logging including the
WIFI_SCAN log domain to see why it's not showing up in NM.

NM 1.2 and later ditch the internal AP list code and just present the
APs that the supplicant does, and remove them from the NM internal AP
list when the supplicant removes them from its own scan list.  So there
shouldn't be any real difference between NM's list and the supplicants,
unless NM failed to parse the supplicant D-Bus object for some reason.

Dan