[Commotion-discuss] Battlemesh talk about mesh-wide channel hopping (for DFS, etc)

[Grady Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I had some thoughts a while back about using nodes for spectrum
sensing and came across LinSSID, a Linux-based spectrum analyzer:
http://sourceforge.net/projects/linssid/

It uses the Linux Wi-Fi drivers to dynamically sense the spectrum
environment across compatible channels. It's probably too resource
intense to run on the average node, but could be used on higher
resource backbone nodes (or client devices) and could feed the data
into a central server.

Obviously, this would largely tie up the node's radio while it was
sampling the spectrum, but it wouldn't have to do it continuously,
only say every hour or even once a day.

On 05/19/2014 05:23 PM, Ben West wrote:
> Simon Wunderlich gave a talk at this year's Battlemesh about
> progress in implementing DFS (dynamic frequency selection) in mesh
> networks, whether through user-space tools or in kernel space.
> 
> http://www.battlemesh.org/BattleMeshV7/Agenda?action=AttachFile&do=view&target=2014-05-17_wbmv7_DFS.pdf
>
>  The intended application from Simon's perspective is to permit
> automated channel hopping for meshes, as required for operating on
> those 5.8GHz bands shared with radar installations.  Although his
> talk focused on the EU regulatory environment, the incentives for
> using these channel in the US would be similar (avoiding otherwise
> crowded channels).
> 
> My understanding is that the FCC presently requires unlicensed
> 5.8GHz radios operating on these channels to be be able to sense
> the present of radar and hop to another channel, and Ubiquiti stock
> firmware for their AirMAX products (e.g. Nanostation M5) now does
> this.  W/r/t running adhoc networks on DFS channels, I'm not sure
> if the FCC explicitly forbids beaconing, or if radios may sample
> the band for 30secs before sending out beacons.  The FCC regs may
> be vague on this detail right now.
> 
> I'm pointing out this particular talk, however, because the ability
> for a mesh to reliably channel-hop would also be *very useful* for
> 2.4GHz meshes.  That band now sees potentially destructive noise
> from channel-hopping neighbors, i.e. one day your mesh works, the
> next day it doesn't.  Manually keeping up where a clear channel
> happens to be becomes increasingly untenable.
> 
> Any high-level thoughts about mesh-wide noise sensing and channel
> hopping schemes for a platform like Commotion?
> 
> 
> 
> _______________________________________________ Commotion-discuss
> mailing list Commotion-discuss at lists.chambana.net 
> https://lists.chambana.net/mailman/listinfo/commotion-discuss
> 

- -- 
Grady Johnson
Open Technology Institute | New America Foundation
@geekwrights
D6AE 65CE 141B 8DBC 7B5F 99AA 6BCC 0833 8B28 833B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTe1v/AAoJEGvMCDOLKIM7lZ8H/if7cVFYO7wkRczQZDWIKUCD
18GyrwNuN4kgjkPrZLi4SIDJnB1AtL/Caw4CG9ojw4q4AxCB4mc3KISiHbAsw3ft
wljxjMhdrzEJ8d+mNFRD3pmDQuVY9/3LGTyj5kX+X6hE5/PDcau5LkzX2/xQfjbW
t1YYjjWNTzwR1UPJmH0AJkWGjZdQADjMepcbgUE31ul3IMvB0rLr1QrZUdlJIt7V
1p1LSHAYnzqtNQAbYBYi3h6Oyw0LSDVK/kuhKm4iBIcxOCq4KBcyk9s9uSu3kWAH
u3hcmYcgUZDJMq+0mmBgwHMpORWtiy754Ty5P+LuS/egclMZipFng0uj674yx6w=
=mxbF
-----END PGP SIGNATURE-----