Re: cfg80211 connect for at76c50x-usb

[Kalle Valo <kalle.valo@iki.fi>]

Jason Andryuk <jandryuk@gmail.com> writes:

> Kalle,

Hi Jason,

> My logs do not show CMD_JOIN getting sent after executing an "iw
> connect".  dmesg shows the three direct probe attempts being sent to
> the device in at76_mac80211_tx, but a separate monitor interface does
> see them transmitted.  at76_mac80211_tx_callback has urb->status == 0;

Earlier I have noticed that transmission doesn't work at all with
CMD_SCAN. I used it only to enable monitoring.

> So I think the direct probes failure is halting mac80211 before it
> gets any further.  This corresponds to the flows in Johannes's
> mac80211 MLME diagrams.

Yes, that seems to be the case here.

> Hacking in the bssid, by initially setting priv->bssid and re-copying
> on _bss_info_changed, does have CMD_JOIN get sent.  However, it
> returns "at76_wait_completion failed: 7"  CMD_STATUS_TIME_OUT == 0x07.
>
> iw connect is hung too.
>
> It looked like priv->essid wasn't getting set, so I hacked that one in
> too.  With the essid hack, the at76_wait_completion disappears, but
> there is still no connection.

Ok, so CMD_JOIN should work properly then.

I have to admit that the firmware is weird and I have frustrutated
with multiple times. Maybe it's now preventing probe requests and only
allowing authentication and association requuests? If you can hack
mac80211 to skip or ignore probe request phase, that might tell us
more.

> However, there is still nothing seen on the monitor interface and it
> is seeing plenty of other traffic. I am trying to filter with
> wlan.addr == <Mac Address> in wireshark for what it's worth.
>
> Since I am not seeing anything with the CMD_JOIN being sent, I am
> wondering if my device has failed.

Unfortunately I'm busy with other stuff and I can't test it. But if
you can send the patches anyway, and if I find the time at some point,
I can test it with my device.

-- 
Kalle Valo