On Fri, Oct 18, 2013 at 5:53 PM, Lorenzo Bianconi <lorenzo.bianconi83@xxxxxxxxx> wrote: > Hi all, > > According to regdb.txt, DFS channels are not marked with passive scan flag: > > country US: DFS-FCC > (2402 - 2472 @ 40), (3, 27) > (5170 - 5250 @ 80), (3, 17) > (5250 - 5330 @ 80), (3, 20), DFS > (5490 - 5600 @ 80), (3, 20), DFS > (5650 - 5710 @ 40), (3, 20), DFS > (5735 - 5835 @ 80), (3, 30) > > Therefore STA device will perform active scanning on DFS channels even > if the channel is not CAC checked and available yet. This is certainly an issue, at least for the atheros drivers the ath module ensures to alway set the passive-scan and no-ibss flags for DFS frequencies, but we should at this point just standardize on this. > Should we perform > passive scan on radar channel setting new state to SCAN_DECISION and > not to SCAN_SEND_PROBE in ieee80211_scan_state_set_channel()? There's a few thing we need to do and I'm working on it. 1) no-ibss and passive-scan flags should be merged to a no-ir flag 2) beaconing should not be allowed if you have no-ir flag or radar flag set but your device doesn't support DFS. If your wiphy supports DFS and if CAC was cleared you can use that channel. If you had an AP and a STA on the same wiphy and if the AP had DFS support and cleared a CAC on a channel, the STA can resuse that information to do an active scan, but it doesn't make sense to share CAC information across different radios on the same system as we technically have no guarantee they are on the same location, you never know. I'm working on 1) right now. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
