* 80211s with DFS
@ 2013-08-11 21:03 Volker von Hoesslin @ SKBX Systems
2013-08-12 9:11 ` Simon Wunderlich
2013-08-13 1:33 ` Wright, Brett
0 siblings, 2 replies; 5+ messages in thread
From: Volker von Hoesslin @ SKBX Systems @ 2013-08-11 21:03 UTC (permalink / raw)
To: linux-wireless
hi mailinglist!
i have a real big problem! i'm trying to implement a wireless-mesh
(80211s) with openWRT (current trunk) over 11a (5GHz) with "authSAE" for
outdoor. all works fine, mesh is runnning and all fine. but now, i'm at
germany and for the outdoor use, i have to use the channel 100-140 with
DFS & TPC. so the mesh implementation dont work in this channel? with
this error:
authSAE config:
#######################################################
authsae:
{
sae:
{
debug = 480;
password = "foobar";
group = [19, 26, 21, 25, 20];
blacklist = 5;
thresh = 5;
lifetime = 3600;
};
meshd:
{
meshid = "foobar";
interface = "mesh0";
band = "11a";
channel = 104;
htmode = "ht20";
mcast-rate = 6;
debug = 1;
};
};
#######################################################
starting mesh with "authSAE":
#######################################################
# meshd-nl80211 -c /etc/authsae.cfg
----------
nlcfg rates hexdump
00 3c 00 5a 00 78 00 b4 00 f0 01 68 01 e0 02 1c
----------
----------
mgtk: hexdump
ce 5a b3 fc 8b 76 db 62 11 c9 58 33 fa 0c 26 88
----------
----------
Fixed Information Elements in this STA hexdump
01 08 8c 12 98 24 b0 48 60 6c
----------
meshd: Starting mesh with mesh id = foobar
----------
basic rates: hexdump
8c 98 b0
----------
joining mesh foobar on freq 3443784, mode 0
nlerror, cmd 68, seq 1376254403: Invalid argument
#######################################################
and this is without "authSAE":
#######################################################
# iw mesh0 set channel 104
# iw mesh0 mesh join foobar
command failed: Invalid argument (-22)
#######################################################
but this is working with a non-DFS channel 44:
#######################################################
# iw mesh0 set channel 44
# iw mesh0 mesh join hackewrt
[21044.240000] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
[21044.240000] mesh-br: port 1(vlan11) entered forwarding state
[21044.250000] mesh-br: port 1(vlan11) entered forwarding state
[21044.260000] IPv6: ADDRCONF(NETDEV_CHANGE): vlan11: link becomes ready
[21044.260000] coova-br: port 1(vlan12) entered forwarding state
[21044.270000] coova-br: port 1(vlan12) entered forwarding state
[21044.280000] IPv6: ADDRCONF(NETDEV_CHANGE): vlan12: link becomes ready
root@6470028F55A2:~#
#######################################################
i think this error is from the "netlink lib(libnl genl)"...
if i use a channel without DFS, it works fine (in germany channel like
36-48)... so how it is possible to use mesh (80211s) with DFS ?
big thx for answer,
volker...
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 80211s with DFS
2013-08-11 21:03 80211s with DFS Volker von Hoesslin @ SKBX Systems
@ 2013-08-12 9:11 ` Simon Wunderlich
2013-08-12 9:27 ` Volker von Hoesslin @ SKBX Systems
2013-08-13 1:33 ` Wright, Brett
1 sibling, 1 reply; 5+ messages in thread
From: Simon Wunderlich @ 2013-08-12 9:11 UTC (permalink / raw)
To: Volker von Hoesslin @ SKBX Systems; +Cc: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
On Sun, Aug 11, 2013 at 11:03:38PM +0200, Volker von Hoesslin @ SKBX Systems wrote:
> i think this error is from the "netlink lib(libnl genl)"...
>
> if i use a channel without DFS, it works fine (in germany channel
> like 36-48)... so how it is possible to use mesh (80211s) with DFS ?
mac80211 does not support DFS in mesh mode so far, the only DFS
support implemented is AP mode (and only with ath9k compatible chips).
I'm currently working on IBSS, I don't if/who will work on
802.11s DFS ...
Cheers,
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 80211s with DFS
2013-08-12 9:11 ` Simon Wunderlich
@ 2013-08-12 9:27 ` Volker von Hoesslin @ SKBX Systems
0 siblings, 0 replies; 5+ messages in thread
From: Volker von Hoesslin @ SKBX Systems @ 2013-08-12 9:27 UTC (permalink / raw)
To: Simon Wunderlich; +Cc: linux-wireless
> I'm currently working on IBSS, I don't if/who will work on
> 802.11s DFS ...
>
it is possible to speed up this work? maybe pay for it!
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: 80211s with DFS
2013-08-11 21:03 80211s with DFS Volker von Hoesslin @ SKBX Systems
2013-08-12 9:11 ` Simon Wunderlich
@ 2013-08-13 1:33 ` Wright, Brett
2013-08-13 9:21 ` Volker von Hoesslin @ SKBX Systems
1 sibling, 1 reply; 5+ messages in thread
From: Wright, Brett @ 2013-08-13 1:33 UTC (permalink / raw)
To: Volker von Hoesslin @ SKBX Systems, linux-wireless
> -----Original Message-----
> From: linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-
> owner@vger.kernel.org] On Behalf Of Volker von Hoesslin @ SKBX Systems
> i have a real big problem! i'm trying to implement a wireless-mesh
> (80211s) with openWRT (current trunk) over 11a (5GHz) with "authSAE"
for
> outdoor. all works fine, mesh is runnning and all fine. but now, i'm
at
> germany and for the outdoor use, i have to use the channel 100-140
with DFS
> & TPC. so the mesh implementation dont work in this channel? with this
> error:
>
Hi
The real difficulty with DFS and 802.11s is what happens when a radar is
detected? All mesh nodes need to be on the same channel, so there needs
to be some consistent way of propagating a channel switch announcement
to all wireless nodes.
Brett
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 80211s with DFS
2013-08-13 1:33 ` Wright, Brett
@ 2013-08-13 9:21 ` Volker von Hoesslin @ SKBX Systems
0 siblings, 0 replies; 5+ messages in thread
From: Volker von Hoesslin @ SKBX Systems @ 2013-08-13 9:21 UTC (permalink / raw)
To: Wright, Brett; +Cc: linux-wireless
> The real difficulty with DFS and 802.11s is what happens when a radar is
> detected? All mesh nodes need to be on the same channel, so there needs
> to be some consistent way of propagating a channel switch announcement
> to all wireless nodes.
>
indeed, thats a hard question. my first hint is looking at cisco
(http://www.cisco.com/en/US/docs/wireless/technology/mesh/7.0/design/guide/MeshAP_70.pdf
-> page 169), but 80211s has't a RAP so maybe there are only some tips
for a workflow.
i think there are diffrent possibilities:
1. the MAP that has a radar detection go sleep and wait till the channel
is clear to come back -> mesh will down :/
2. the mesh has to negotiate a new free channel via bacon-frames, maybe
generating preventively a list of channel for switching?
3. some other ideas ?
is there someone at work for a DFS implementation?
volker...
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-08-13 9:22 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-11 21:03 80211s with DFS Volker von Hoesslin @ SKBX Systems
2013-08-12 9:11 ` Simon Wunderlich
2013-08-12 9:27 ` Volker von Hoesslin @ SKBX Systems
2013-08-13 1:33 ` Wright, Brett
2013-08-13 9:21 ` Volker von Hoesslin @ SKBX Systems
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).