[OpenWrt-Devel] why only hostapd?
smilebef at gmail.com
smilebef at gmail.com
Tue Jul 8 09:22:48 EDT 2014
Only hostap work with dfs in AP-Mode?
This is the last development step here?
Than is this not rewarding for me.
Wy this limitation?
Is this necessary?
I think no.
1. I think the Hardware has only to disable the channel if Radar is
detectet. Right? It works.
2. The Software in Userspace has to choice a (ald and new) channel.
Right? It works only with hostapd!
3. We are not bound to honour a standard, that not explicit writen for
4. We are only engaged to fulfil the laws of the countries.
But why only hostapd?
If the Hardware disables the channel because radardetect, i do not need
any instance, that tell me wich aplication rules my channels, because i
can not overide disabled channels by hardware with the software tools.
I think the choice of the channel can also be done by a shell-script
using iw or iwconfig located in chrontab.
The current situation is in my opinion not nessesary and not
consistent to ours situation.
Am Thu, 03 Jul 2014 18:14:10 +0200
schrieb Martin Garbe <monomartin at opennet-initiative.de>:
> On 7/3/14, 7:28 AM, Jacek Kikiewicz wrote:
> > Hi,
> > I sure selected this option, as I said command 'iw phy phy1 info'
> > does in fact show DFS channels, but I just cannot set them for
> > usage...
> The command "iw phy ..." only shows hardware capabilities. For DFS
> hardware AND software support is needed. In OpenWRT you need hostapd
> to support DFS too. The config parameter CONFIG_PACKAGE_ATH_DFS
> explicitely activates DFS in hostapd. This parameter is not set by
> default. For more information see also the patch with comment in git:
> > Jacek
> > On 07/02/14 22:50, Martin Garbe wrote:
> >> On 7/1/14, 10:04 AM, Jacek Kikiewicz wrote:
> >>> Hello,
> >>> I have few APs that are using ath9k driver, I've read that now
> >>> DFS is supported on that driver,
> >>> so I compiled latest revision (yesterday: 41415), and started
> >>> playing, basically when as per
> >>> manual / howto I run 'iw phy phy1 info' I can see DFS channels,
> >>> exactly like in howto on a wiki, problem is however
> >>> that I cannot make it work on those channels (I've tried
> >>> 52,56,100, 104), after changing config and restarting wifi
> >>> I saw in dmesg 'interface wlan1 entered disabled mode) - I tried
> >>> with HT20 for the beginning.
> >>> So, question here is, should this work in current state or is
> >>> there still some support missing?
> >>> I can pull any logs / settings that are of interest.
> >> Have you elected
> >> CONFIG_PACKAGE_ATH_DFS=y
> >> when compiling the driver? This way you agree to the fact that your
> >> hardware supports DFS. After that DFS channels can be selected.
> >> Martin
> >>> Thanks!
> >>> Jacek
> >>> _______________________________________________
> >>> openwrt-devel mailing list
> >>> openwrt-devel at lists.openwrt.org
> >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> >> _______________________________________________
> >> openwrt-devel mailing list
> >> openwrt-devel at lists.openwrt.org
> >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> > _______________________________________________
> > openwrt-devel mailing list
> > openwrt-devel at lists.openwrt.org
> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel