Hi,

I like to open this thread because the lack of DFS support in OpenWRT.

For people in US, and similar regulatory domains, the lack of DFS can't be a problem. You can use channels 48-64 and 149-165 for indoors and outdoors. Nevertheless, for people in EUROPE and similar domains, only channels 100-140 are acceptable for outdoors (channels over 140 are forbidden!). But, as all of you know, these channels (100-140) requires DFS in ALL DOMAINS.

After that, I suggest to developers of OpenWRT to start to support the DFS functionality.

From my research, the Linux Wireless community has initial support for a limited set of hardware: ar9280 and other Atheros chips in the family 9K.

The "ath9k-devel" mailing list is the best place to recopile useful patches. See: http://www.mail-archive.com/ath9k-devel … /info.html and search for "dfs".

I hope to see first snapshots with limited support of DFS in the next months!

Just because you found some code with "radar" or "dfs" in it doesn't mean that there is a working implementation.

Hi Jow,

Ok. But why OpenWRT don't support channels 100-140 in CLIENT MODE without DFS support? All wifi cards that works as "client device" don't have DFS support enabled, but can comunicate with AP with DFS.

Please, read: http://www.nts.com/pdf/whitepapers/6_Dy … 20Band.pdf

I hope that in a short period of time we can use our OpenWRT devices as a CLIENTS of a VERY EXPENSIVE APs that use channels 100-140 (no one has opensource support for DFS).

THIS IS MANDATORY IN EUROPE FOR OUTDOORS USE!!!!!!!!!!!!!!!!!!!

(Last edited by onrollo on 25 Oct 2012, 11:44)

Hi,

After some tests with the last snapshots I can confirm that the Atheros driver supports scaning in channels 100-140 without DFS. I'll check if the CLIENT MODE works in these channels.

Anyone has more info about DFS in OpenWRT?