Search Linux Wireless

CMD_REMAIN_ON_CHANNEL vs CMD_FRAME (offchannel)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I'm having an issue with CMD_REMAIN_ON_CHANNEL taking a full second to become ready versus CMD_FRAME (offchannel_ok=1) which is quite fast. Under the hood it looks like both commands call ieee80211_start_roc_work() so its curious why one would take so long. I'm running this in UML so I shouldn't be hitting scheduling problems (at least that's how I understand UML).

This happens during the DPP auth exchange, I can include a full log if desired, but this is the sequence:

- Start ROC on 2417mhz
- Wait for ROC event indicating we are offchannel
- Receive DPP presence announcement from enrollee
- Send DPP auth request, request enrollee switches to 2412mhz
- Send Cancel ROC (and wait for confirmation)

- Start ROC on 2412mhz
- Oddly, receive the enrollees auth response before ROC event. So the driver _did_ switch channels.
- ROC event comes about a second later, and enrollee has timed out

So the driver is in fact going offchannel to 2412 and even receiving a frame. But for whatever reason it doesn't send the ROC event for a full second. Any idea why the ROC event is so delayed here?

Thanks,
James



[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Wireless Regulations]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux