Re: NM can't see WEP access point
On Fri, 2016-06-10 at 17:30 +0200, Bastien Nocera wrote:
> On Fri, 2016-06-10 at 10:11 -0500, Dan Williams wrote:
> >
> >
>
> >
> > Jouni confirmed that there is a bug in the supplicant. The
> > commit ce8963fc9f197771cd51ba2834fbdf711189641a ('Remove
> > WEP40/WEP104
> > cipher suite support for WPA/WPA2') appears to have broken this
> > functionality (where the AP advertises WEP support in WPA/RSN IEs),
> > but
> > it will still work for WEP-only APs. Not sure what his solution
> > will
> > be, since this behavior (TSN) is technically allowed by the
> > standards
> > for WPA1 (but not necessarily for WPA2/RSN, I believe).
> >
> > We should likely also modify NM to not reject the AP if the RSN IE
> > fails to parse, but to simply ignore WPA2/RSN on that AP and only
> > allow
> > using TKIP, if present. If the RSN IE fails to parse and the AP
> > does
> > not support TKIP, then NM should correctly reject the AP, since
> > RSN+WEP
> > is not really a valid mode.
> The only WEP-equivalent mode on the Airport Express (gen 1) I have is
> labeled as "WEP (Transitional Security Network)".
Does it allow configuring the WEP key separately from the WPA
passphrase? Or does it have just one key/passphrase entry, and if so,
what is it labeled?
Dan
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM can't see WEP access point
On Fri, 2016-06-10 at 10:11 -0500, Dan Williams wrote:
>
> Jouni confirmed that there is a bug in the supplicant. The
> commit ce8963fc9f197771cd51ba2834fbdf711189641a ('Remove WEP40/WEP104
> cipher suite support for WPA/WPA2') appears to have broken this
> functionality (where the AP advertises WEP support in WPA/RSN IEs),
> but
> it will still work for WEP-only APs. Not sure what his solution will
> be, since this behavior (TSN) is technically allowed by the standards
> for WPA1 (but not necessarily for WPA2/RSN, I believe).
>
> We should likely also modify NM to not reject the AP if the RSN IE
> fails to parse, but to simply ignore WPA2/RSN on that AP and only
> allow
> using TKIP, if present. If the RSN IE fails to parse and the AP does
> not support TKIP, then NM should correctly reject the AP, since
> RSN+WEP
> is not really a valid mode.
The only WEP-equivalent mode on the Airport Express (gen 1) I have is
labeled as "WEP (Transitional Security Network)".
I'll have to see how to set up a hotspot with WEP some other way for my
testing I think.
Cheers
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM can't see WEP access point
On Thu, 2016-06-09 at 16:47 -0500, Dan Williams wrote:
> On Thu, 2016-06-09 at 17:28 +0200, Bastien Nocera wrote:
> >
> > On Thu, 2016-06-09 at 10:23 -0500, Dan Williams wrote:
> > >
> > >
> > > On Thu, 2016-06-09 at 17:13 +0200, Bastien Nocera wrote:
> > > >
> > > >
> > > > On Thu, 2016-06-09 at 10:00 -0500, Dan Williams wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > > So I missed it before. But your AP isn't actually set for
> > > > > WEP,
> > > > > it's
> > > > > set for WPA/TKIP. If it's actually using just WEP, you won't
> > > > > see
> > > > > any
> > > > > of the RSN/WPA IEs in the beacon.
> > > > Still isn't right that it's not showing though, is it?
> > > Yeah. Can you 'nmcli g log', then:
> > >
> > > nmcli g log level debug domains > > domains>,WIFI_SCAN
> > >
> > > and then turn on airplane mode, turn it off, and wait for a bit
> > > until
> > > you're sure the AP doesn't get found by NM. Then send me the
> > > logs
> > > and
> > > I'll take a look to see if I can figure out why NM doesn't find
> > > it.
> > > If
> > > the supplicant sees it, but NM does not, then there's an NM bug
> > > somewhere.
> > Well, wpa_supplicant is throwing an error when you try to get the
> > RSN,
> > so I don't really expect NM to be able to process that access
> > point.
> The AP's beacon indicates that it is using TSN (Transition Security
> Network), since it's indicating WEP-104 as the group cipher (00 0f ac
> 05). It looks like wpa_supplicant tries to handle that in some
> places,
> but ultimately the IE parsing in wpa_parse_wpa_ie_rsn() doesn't allow
> that, so the IE won't parse, and the supplicant wouldn't allow
> assocaiting to that network either.
>
> So it's a bug in the supplicant for TSN networks. For other testing,
> try disabling RSN/WPA2? If the AP allows a "WEP-only" mode that's
> what
> I'd use. You want *nothing* in the beacon that indicates RSN or WPA
> capabilities.
Jouni confirmed that there is a bug in the supplicant. The
commit ce8963fc9f197771cd51ba2834fbdf711189641a ('Remove WEP40/WEP104
cipher suite support for WPA/WPA2') appears to have broken this
functionality (where the AP advertises WEP support in WPA/RSN IEs), but
it will still work for WEP-only APs. Not sure what his solution will
be, since this behavior (TSN) is technically allowed by the standards
for WPA1 (but not necessarily for WPA2/RSN, I believe).
We should likely also modify NM to not reject the AP if the RSN IE
fails to parse, but to simply ignore WPA2/RSN on that AP and only allow
using TKIP, if present. If the RSN IE fails to parse and the AP does
not support TKIP, then NM should correctly reject the AP, since RSN+WEP
is not really a valid mode.
Dan
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM can't see WEP access point
On Thu, 2016-06-09 at 17:28 +0200, Bastien Nocera wrote: > On Thu, 2016-06-09 at 10:23 -0500, Dan Williams wrote: > > > > On Thu, 2016-06-09 at 17:13 +0200, Bastien Nocera wrote: > > > > > > On Thu, 2016-06-09 at 10:00 -0500, Dan Williams wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > So I missed it before. But your AP isn't actually set for WEP, > > > > it's > > > > set for WPA/TKIP. If it's actually using just WEP, you won't > > > > see > > > > any > > > > of the RSN/WPA IEs in the beacon. > > > Still isn't right that it's not showing though, is it? > > Yeah. Can you 'nmcli g log', then: > > > > nmcli g log level debug domains > domains>,WIFI_SCAN > > > > and then turn on airplane mode, turn it off, and wait for a bit > > until > > you're sure the AP doesn't get found by NM. Then send me the logs > > and > > I'll take a look to see if I can figure out why NM doesn't find it. > > If > > the supplicant sees it, but NM does not, then there's an NM bug > > somewhere. > Well, wpa_supplicant is throwing an error when you try to get the > RSN, > so I don't really expect NM to be able to process that access point. The AP's beacon indicates that it is using TSN (Transition Security Network), since it's indicating WEP-104 as the group cipher (00 0f ac 05). It looks like wpa_supplicant tries to handle that in some places, but ultimately the IE parsing in wpa_parse_wpa_ie_rsn() doesn't allow that, so the IE won't parse, and the supplicant wouldn't allow assocaiting to that network either. So it's a bug in the supplicant for TSN networks. For other testing, try disabling RSN/WPA2? If the AP allows a "WEP-only" mode that's what I'd use. You want *nothing* in the beacon that indicates RSN or WPA capabilities. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM can't see WEP access point
On Thu, 2016-06-09 at 10:23 -0500, Dan Williams wrote: > On Thu, 2016-06-09 at 17:13 +0200, Bastien Nocera wrote: > > On Thu, 2016-06-09 at 10:00 -0500, Dan Williams wrote: > > > > > > > > > > > > > > So I missed it before. But your AP isn't actually set for WEP, > > > it's > > > set for WPA/TKIP. If it's actually using just WEP, you won't see > > > any > > > of the RSN/WPA IEs in the beacon. > > Still isn't right that it's not showing though, is it? > > Yeah. Can you 'nmcli g log', then: > > nmcli g log level debug domains domains>,WIFI_SCAN > > and then turn on airplane mode, turn it off, and wait for a bit until > you're sure the AP doesn't get found by NM. Then send me the logs > and > I'll take a look to see if I can figure out why NM doesn't find it. > If > the supplicant sees it, but NM does not, then there's an NM bug > somewhere. Well, wpa_supplicant is throwing an error when you try to get the RSN, so I don't really expect NM to be able to process that access point. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM can't see WEP access point
On Thu, 2016-06-09 at 17:13 +0200, Bastien Nocera wrote: > On Thu, 2016-06-09 at 10:00 -0500, Dan Williams wrote: > > > > > > > > > So I missed it before. But your AP isn't actually set for WEP, > > it's > > set for WPA/TKIP. If it's actually using just WEP, you won't see > > any > > of the RSN/WPA IEs in the beacon. > Still isn't right that it's not showing though, is it? Yeah. Can you 'nmcli g log', then: nmcli g log level debug domains ,WIFI_SCAN and then turn on airplane mode, turn it off, and wait for a bit until you're sure the AP doesn't get found by NM. Then send me the logs and I'll take a look to see if I can figure out why NM doesn't find it. If the supplicant sees it, but NM does not, then there's an NM bug somewhere. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM can't see WEP access point
On Thu, 2016-06-09 at 10:00 -0500, Dan Williams wrote: > > So I missed it before. But your AP isn't actually set for WEP, it's > set for WPA/TKIP. If it's actually using just WEP, you won't see any > of the RSN/WPA IEs in the beacon. Still isn't right that it's not showing though, is it? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM can't see WEP access point
On Thu, 2016-06-09 at 15:34 +0200, Bastien Nocera wrote: > On Tue, 2016-06-07 at 19:13 +0200, Bastien Nocera wrote: > > > > On Tue, 2016-06-07 at 09:58 -0500, Dan Williams wrote: > > > > > > 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=0069f3b5fd9a > > > > 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: > > > > 2D1A2C401700 > > > > IE: Unknown: > > > > 3D160B001100 > > > > IE: Unknown: 4605020001 > > > > IE: WPA Version 1 > > > > Group Cipher : WEP-104 > > > > Pairwise Ciphers (1) : TKIP > > > > Authentication Suites (1) : PSK > > > > IE: Unknown: > > > > DD180050F2020101070003A427A442435E0062322F00 > > > > IE: Unknown: DD07000393016B0B20 > > > > IE: Unknown: > > > > DD0E0017F207000101060024369D3B33 > > > > IE: Unknown: DD0B0017F2010001010007 > > > > > > > > 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. > > $ sudo ./wpas-list.py wlp2s0 > > [sudo] password for hadess: > > 54:64:d9:3e:0e:89 :: ssid='Livebox- > > 0E88' wpa=yes wpa2=yes signal=-58% freq=5240 > > 18:1e:78:70:c4:6b :: ssid='Livebox- > > C46A' wpa=yes wpa2=yes signal=-62% freq=5520 > > Traceback (most recent call last): > > File "./wpas-list.py", line 68, in > > main() > > File "./wpas-list.py", line 46, in main > > props = props_iface.GetAll(WPAS_DBUS_BSSID_INTERFACE) > > File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line > > 70, in __call__ > > return self._proxy_method(*args, **keywords) > > File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line > > 145, in __call__ > > **keywords) > > File "/usr/lib64/python2.7/site-packages/dbus/connection.py", > > line 651, in call_blocking > > message, timeout) > > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Failed: > > failed to parse RSN IE > After adding a try/except: > failed for /fi/w1/wpa_supplicant1/Interfaces/3/BSSs/2 > > Which is the "WEP test" AP I used. So I missed it before. But your AP isn't actually set for WEP, it's set for WPA/TKIP. If it's actually using just WEP, you won't see any of the RSN/WPA IEs in the beacon. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM can't see WEP access point
On Tue, 2016-06-07 at 19:13 +0200, Bastien Nocera wrote:
> On Tue, 2016-06-07 at 09:58 -0500, Dan Williams wrote:
> > 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=0069f3b5fd9a
> > > 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:
> > > 2D1A2C401700
> > > IE: Unknown:
> > > 3D160B001100
> > > IE: Unknown: 4605020001
> > > IE: WPA Version 1
> > > Group Cipher : WEP-104
> > > Pairwise Ciphers (1) : TKIP
> > > Authentication Suites (1) : PSK
> > > IE: Unknown:
> > > DD180050F2020101070003A427A442435E0062322F00
> > > IE: Unknown: DD07000393016B0B20
> > > IE: Unknown: DD0E0017F207000101060024369D3B33
> > > IE: Unknown: DD0B0017F2010001010007
> > >
> > > 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.
>
> $ sudo ./wpas-list.py wlp2s0
> [sudo] password for hadess:
> 54:64:d9:3e:0e:89 :: ssid='Livebox-0E88' wpa=yes wpa2=yes signal=-58%
> freq=5240
> 18:1e:78:70:c4:6b :: ssid='Livebox-C46A' wpa=yes wpa2=yes signal=-62%
> freq=5520
> Traceback (most recent call last):
> File "./wpas-list.py", line 68, in
> main()
> File "./wpas-list.py", line 46, in main
> props = props_iface.GetAll(WPAS_DBUS_BSSID_INTERFACE)
> File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in
> __call__
> return self._proxy_method(*args, **keywords)
> File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in
> __call__
> **keywords)
> File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in
> call_blocking
> message, timeout)
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Failed: failed to
> parse RSN IE
After adding a try/except:
failed for /fi/w1/wpa_supplicant1/Interfaces/3/BSSs/2
Which is the "WEP test" AP I used.
$ sudo gdbus introspect --system --dest fi.w1.wpa_supplicant1 --object-path
/fi/w1/wpa_supplicant1/Interfaces/3/BSSs/2
interface fi.w1.wpa_supplicant1.BSS {
methods:
signals:
PropertiesChanged(a{sv} properties);
properties:
readonly ay SSID = [0x57, 0x45, 0x50, 0x20, 0x74, 0x65, 0x73, 0x74];
readonly ay BSSID = [0x00, 0x24, 0x36, 0x9d, 0x3b, 0x33];
readonly b Privacy = true;
readonly s Mode = 'infrastructure';
readonly n Signal = -35;
readonly q Frequency = 2462;
readonly au Rates = [5400, 4800, 3600, 2400, 1800,
1200, 1100, 900, 600, 550, 200, 100];
readonly a{sv} WPA = {'KeyMgmt': <['wpa-psk']>, 'Group': <''>,
'Pairwise': <['tkip']>};
readonly a{sv} RSN;
readonly a{sv} WPS = {};
readonly ay IEs = [0x00, 0x08, 0x57, 0x45, 0x50, 0x20, 0x74,
0x65, 0x73, 0x74, 0x01, 0x08, 0x82, 0x84, 0x8b, 0x96, 0x0c, 0x12, 0x18,
0x24, 0x03, 0x01, 0x0b, 0x07, 0x06, 0x47, 0x42, 0x20, 0x01, 0x0d, 0x1e,
0x2a, 0x01, 0x00, 0x32, 0x04, 0x30, 0x48, 0x60, 0x6c, 0x30, 0x18, 0x01,
0x00, 0x00, 0x0f, 0xac, 0x05, 0x02, 0x00, 0x00, 0x0f, 0xac,
Re: NM can't see WEP access point
On Tue, 2016-06-07 at 09:58 -0500, Dan Williams wrote: > 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=0069f3b5fd9a > > 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: > > 2D1A2C401700 > > IE: Unknown: > > 3D160B001100 > > IE: Unknown: 4605020001 > > IE: WPA Version 1 > > Group Cipher : WEP-104 > > Pairwise Ciphers (1) : TKIP > > Authentication Suites (1) : PSK > > IE: Unknown: > > DD180050F2020101070003A427A442435E0062322F00 > > IE: Unknown: DD07000393016B0B20 > > IE: Unknown: DD0E0017F207000101060024369D3B33 > > IE: Unknown: DD0B0017F2010001010007 > > > > 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. $ sudo ./wpas-list.py wlp2s0 [sudo] password for hadess: 54:64:d9:3e:0e:89 :: ssid='Livebox-0E88' wpa=yes wpa2=yes signal=-58% freq=5240 18:1e:78:70:c4:6b :: ssid='Livebox-C46A' wpa=yes wpa2=yes signal=-62% freq=5520 Traceback (most recent call last): File "./wpas-list.py", line 68, in main() File "./wpas-list.py", line 46, in main props = props_iface.GetAll(WPAS_DBUS_BSSID_INTERFACE) File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Failed: failed to parse RSN IE Ungood. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM can't see WEP access point
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=0069f3b5fd9a > 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: > 2D1A2C401700 > IE: Unknown: > 3D160B001100 > IE: Unknown: 4605020001 > IE: WPA Version 1 > Group Cipher : WEP-104 > Pairwise Ciphers (1) : TKIP > Authentication Suites (1) : PSK > IE: Unknown: > DD180050F2020101070003A427A442435E0062322F00 > IE: Unknown: DD07000393016B0B20 > IE: Unknown: DD0E0017F207000101060024369D3B33 > IE: Unknown: DD0B0017F2010001010007 > > 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 ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
