Re: zyd fails to associate with a network

[Dmitrij D. Czarkoff]

Maybe anyone knows how can I get any debugging information about my device?
I could try to solve it on my own if I understood where the error is...

Dmitrij D. Czarkoff  wrote:

> Hello!
>
> I'm trying to connect a wireless network on my ASUS R2Hv. Both the built-in
> and usb dongle wireless adapters are zyd-based:
>
> Asus WL-159g (built-in):
>  $ usbdevs -vdf /dev/usb0 -a 3
>  Controller /dev/usb0:
>  addr 3: high speed, power 500 mA, config 1, USB2.0 WLAN(0x171b), 
> ASUS(0x0b05),
>  rev 48.02
>zyd0
>
> 3COM 3CRUSB10075 (usb dongle):
>  $ usbdevs -vdf /dev/usb0 -a 7 
>  Controller /dev/usb0:
>  addr 7: high speed, power 500 mA, config 1, USB2.0 WLAN(0x1215),
>  ZyDAS(0x0ace), rev 48.10
>zyd1
>
> zyd(4) mensions both as supported. They both attach as zyd0 and zyd1
> respectively. Scanning on them succeeds with my network being found, but
> connecting to it gives troubles:
>
> $ sudo ifconfig zyd0 scan  
> zyd0: flags=8802 mtu 1500
> lladdr 00:1d:60:62:59:ef
> priority: 4
> groups: wlan
> media: IEEE802.11 autoselect (DS1 mode 11g)
> status: no network
> ieee80211: nwid "" 100dBm
> nwid bedova chan 11 bssid 00:23:54:71:50:71 26dB 54M
> short_preamble,short_slottime 
> $ sudo ifconfig zyd0 nwid bedova 
> $ sudo ifconfig zyd0 
> zyd0: flags=8802 mtu 1500
> lladdr 00:1d:60:62:59:ef
> priority: 4
> groups: wlan
> media: IEEE802.11 autoselect (DS1 mode 11g)
> status: no network
> ieee80211: nwid bedova 100dBm
> inet6 fe80::21d:60ff:fe62:59ef%zyd0 prefixlen 64 scopeid 0x4
> $ sudo dhclient zyd0
> zyd0: no link . sleeping
>
> What can I do to further investigate the problem?

Re: zyd fails to associate with a network

[damien . bergamini]

| Maybe anyone knows how can I get any debugging information about my device?
| I could try to solve it on my own if I understood where the error is...

"ifconfig zyd0 debug" is usually a good start.

Damien

Re: zyd fails to associate with a network

[Dmitrij D. Czarkoff]

damien.bergam...@free.fr wrote:
> "ifconfig zyd0 debug" is usually a good start.

Thanks.

Actually, I didn't get anything I believe to be helpful.

So, my steps were:

# ifconfig zyd0 debug
# ifconfig zyd0 up
# ifconfig zyd0 scan
zyd0: flags=8847 mtu 1500
lladdr 00:18:6e:35:fd:7f
priority: 4
groups: wlan
media: IEEE802.11 autoselect
status: no network
ieee80211: nwid "" 100dBm
nwid STREAM-15 chan 6 bssid 00:13:33:8a:03:bf 142dB 54M 
privacy,short_slottime 
nwid TheTail chan 6 bssid 00:14:d1:59:16:d3 143dB 54M 
privacy,short_preamble,short_slottime 
nwid TP-LINK chan 6 bssid 00:1d:0f:f3:1e:5b 156dB 54M 
privacy,short_preamble,short_slottime 
nwid kusso chan 6 bssid 00:1e:58:b8:99:2b 20dB 54M 
privacy,short_preamble,short_slottime 
nwid bedova chan 11 bssid 00:23:54:71:50:71 24dB 54M 
short_preamble,short_slottime 
# ifconfig zyd0 nwid bedova
# dhclient zyd0
zyd0: no link . sleeping
# ifconfig zyd0 down

The corresponding dmesg says:

zyd0 at uhub0 port 2 configuration 1 interface 0 "ZyDAS USB2.0 WLAN" rev 
2.00/48.10 addr 3
zyd0: HMAC ZD1211B, FW 47.25, RF AL2230, PA 0, address 00:18:6e:35:fd:7f
zyd0: begin active scan
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 2 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 3 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 4 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 5 mode 11g
zyd0: received beacon from 00:1e:58:b8:99:2b rssi 20 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 6 mode 11g
zyd0: received beacon from 00:14:d1:59:16:d3 rssi 143 mode 11g
zyd0: received beacon from 00:13:33:8a:03:bf rssi 140 mode 11g
zyd0: received beacon from 00:13:33:8a:03:bf rssi 142 mode 11g
zyd0: received beacon from 00:1d:0f:f3:1e:5b rssi 156 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 7 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 8 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 9 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 10 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 172 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 11 mode 11g
zyd0: received probe_resp from 00:23:54:71:50:71 rssi 161 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 24 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 24 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 12 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 156 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 162 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 161 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 13 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 14 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 1 mode 11g
zyd0: end active scan
zyd0: begin active scan
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 2 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 3 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 4 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 5 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 6 mode 11g
zyd0: received beacon from 00:13:33:8a:03:bf rssi 138 mode 11g
zyd0: received beacon from 00:14:d1:59:16:d3 rssi 119 mode 11g
zyd0: received beacon from 00:13:33:8a:03:bf rssi 137 mode 11g
zyd0: received beacon from 00:14:d1:59:16:d3 rssi 137 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 7 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 8 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 9 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 10 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 56 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 159 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 11 mode 11g
zyd0: received probe_resp from 00:23:54:71:50:71 rssi 160 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 30 mode 11g
zyd0: received beacon from 00:16:e3:f3:a3:ce rssi 147 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 147 mode 11g
zyd0: received beacon from 00:16:e3:f3:a3:ce rssi 25 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 20 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 12 mode 11g
zyd0: received beacon from 00:23:54:71:50:71 rssi 165 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 13 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 14 mode 11g
zyd0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 1 mode 11g
zyd0: end active scan
zyd0: sending auth to 00:23:54:71:50:71 on channel 11 mode 11g
zyd0: received auth from 00:23:54:71:50:71 rssi 27 mode 11g
zyd0: sending assoc_req to 00:23:54:71:50:71 on channel 11 mode 11g
z

Re: zyd fails to associate with a network

[damien . bergamini]

| So now I know that that:
| 
| 1. the association fails with status 25;
| 2. the drivers actively sends free-roaming requests during
| asssociation
| process while is requested to connect an exact network.
| 
| Where can I read what is "association failed (status 25)" and
| "deauthenticate (reason 3)"? Does anyone know what the problem is?

Status 25 is IEEE80211_STATUS_SHORTSLOT_REQUIRED.
It means that the access point refuses association from
clients that do not support short slot time.
zyd(4) does not have the IEEE80211_C_SHSLOT capability.
I'll try to see what is required to support that functionnality.
I suggest you submit a PR with sendbug so it does not get lost.

Damien

Re: zyd fails to associate with a network

[Dmitrij D. Czarkoff]

damien.bergam...@free.fr wrote:
> Status 25 is IEEE80211_STATUS_SHORTSLOT_REQUIRED.
> It means that the access point refuses association from
> clients that do not support short slot time.

Thanks!

While it's not a valid workaround, I've set my router up to long slot, so my
issue is resolved.

Still, could You please tell me where can I find that info without disturbing
developpers and mailing list memebers?

--
Dmitrij D. Czarkoff

Re: zyd fails to associate with a network

[damien . bergamini]

| Thanks!
| 
| While it's not a valid workaround, I've set my router up to long slot,
| so my issue is resolved.
| 
| Still, could You please tell me where can I find that info without
| disturbing developpers and mailing list memebers?

In the IEEE 802.11 standard or in /usr/src/sys/net80211/ieee80211.h
or /usr/include/net80211/ieee80211.h

Damien