<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.extremist.software/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=98.156.77.43</id>
	<title>Noisebridge - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.extremist.software/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=98.156.77.43"/>
	<link rel="alternate" type="text/html" href="https://wiki.extremist.software/wiki/Special:Contributions/98.156.77.43"/>
	<updated>2026-04-05T11:49:48Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.13</generator>
	<entry>
		<id>https://wiki.extremist.software/index.php?title=HInternet/TR2&amp;diff=34154</id>
		<title>HInternet/TR2</title>
		<link rel="alternate" type="text/html" href="https://wiki.extremist.software/index.php?title=HInternet/TR2&amp;diff=34154"/>
		<updated>2013-09-25T03:53:42Z</updated>

		<summary type="html">&lt;p&gt;98.156.77.43: /* 802.11s */  Fixed a typo: 8021s --&amp;gt; 80211s&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 802.11 ==&lt;br /&gt;
* [http://en.wikipedia.org/wiki/IEEE_802.11 IEEE 802.11] comprises a set of standards for wireless LAN (WLAN) operation.&lt;br /&gt;
&lt;br /&gt;
== Regulatory Requirements ==&lt;br /&gt;
&lt;br /&gt;
Although it is possible to encode nearly all callsigns in the 6 byte source MAC address field for an 802.11 radio to satisfy the identification requirement for part 97 operation, callsigns can be more than 6 bytes long.  Sending a broadcast UDP packet to port 73 with the station identification information will suffice in this case.&lt;br /&gt;
&lt;br /&gt;
== Commercial Hardware ==&lt;br /&gt;
* [[HInternet/Hardware/MerakiMini|Meraki Mini]]&lt;br /&gt;
&lt;br /&gt;
== 802.11s ==&lt;br /&gt;
&lt;br /&gt;
802.11s is a draft amendment to the existing 802.11 standards documents to support mesh networking between WLAN nodes. It supports unicast and multicast routing, and RF-aware dynamic routing using a new dynamic routing protocol dubbed Hybrid Wireless Mesh Protocol (HWMP).&lt;br /&gt;
&lt;br /&gt;
There is some support in the mac80211 stack in the Linux kernel to support an all-software implementation of 802.11s dubbed [http://open80211s.org/trac open80211s].&lt;br /&gt;
&lt;br /&gt;
It is present in kernel 2.6.32 and above, and is backported through the [http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=summary; wireless-testing] git tree. &amp;lt;sup&amp;gt;[Citation Needed]&amp;lt;/sup&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hardware requirements for open80211s ==&lt;br /&gt;
* A WLAN adapter that has a driver written for the mac80211 framework. Consult the [http://linuxwireless.org/en/users/Drivers Driver Table] to check that it also supports &amp;quot;mesh&amp;quot; as an interface type.&lt;br /&gt;
&lt;br /&gt;
* Recommended computers&lt;br /&gt;
** [http://www.soekris.com/products.htm Soekris computers] with miniPCI slots. These are fairly open, low-power, x86 computers. They&#039;re produced in relatively small production runs so they can be somewhat expensive.&lt;br /&gt;
** [http://www.ubnt.com/routerstation Ubiquiti RouterStation]. A low-power, MIPS computer for WISP applications. Produced at scale, and relatively inexpensive.&lt;br /&gt;
** [http://www.routerboard.com/ RouterBoard] are low-power, mostly Atheros-based MIPS computers made by WISP supplier MicroTik. Produced at scale and relatively inexpensive.&lt;br /&gt;
* Recommended wireless adapters/controllers&lt;br /&gt;
** Ubiquiti Networks Atheros-based miniPCI Adapters&lt;br /&gt;
*** [http://ubnt.com/xr2 XR2]. A high-power 2.4 GHz adapter that supports 5 MHz channels. 28 dBm TXPO.&lt;br /&gt;
*** [http://ubnt.com/sr2 SR2]. A high-power 2.4 GHz adapter that supports 5 MHz channels. 26 dBm TXPO.&lt;br /&gt;
*** [http://ubnt.com/xr5 XR5]. A high-power 5 GHz adapter that supports 5 MHz channels. 28 dBm TXPO.&lt;br /&gt;
*** [http://ubnt.com/xr9 XR9]. A 900 MHz adapter that supports 5 MHz channels inside the 33cm band. 28 dBm.&lt;br /&gt;
*** [http://ubnt.com/sr9 SR9]. A 900 MHz adapter that supports 5 MHz channels inside the 33cm band. 20 dBm.&lt;br /&gt;
*** [http://ubnt.com/xr3 XR3-3.5]. A 3.4 - 3.7 GHz adapter. Might be usable in the 3.3 - 3.5 GHz band.&lt;br /&gt;
*** [http://ubnt.com/xr1 XR1]. A 180-280 MHz VHF adapter that might be able to be modified for use in amateur radio spectrum. Supports 5 MHz channels.&lt;br /&gt;
** Ubiquiti Networks Atheros-based radio systems&lt;br /&gt;
*** [http://ubnt.com/bullet Bullet] are ruggedized radio systems that are powered over PoE and have an integrated N connector. 1 watt TXPO.&lt;br /&gt;
&lt;br /&gt;
== Example: configuring an open80211s network under Linux using mac80211_hwsim ==&lt;br /&gt;
There exists a testing driver in the mac80211 stack in Linux in recent kernels that will create simulated 802.11 devices so that one can test mesh networking even if they don&#039;t have proper adapters yet. It creates a configurable number of adapters (default is 2) that will shuttle frames between adapters that are tuned to the same frequency.&lt;br /&gt;
&lt;br /&gt;
* Before beginning, make sure that you have a recent version of the [http://git.sipsolutions.net/?p=iw.git &amp;quot;iw&amp;quot; utility], as the netlink interface to mac80211 is under constant development.&lt;br /&gt;
* First, load the mac80211_hwsim driver&lt;br /&gt;
 modprobe mac80211_hwsim&lt;br /&gt;
* You should see some lines in your dmesg like:&lt;br /&gt;
 [80477.585860] mac80211_hwsim: Initializing radio 0&lt;br /&gt;
 [80477.586051] phy3: Selected rate control algorithm &#039;minstrel&#039;&lt;br /&gt;
 [80477.587047] phy3: hwaddr 02:00:00:00:00:00 registered&lt;br /&gt;
 [80477.587057] mac80211_hwsim: Initializing radio 1&lt;br /&gt;
 [80477.587326] phy4: Selected rate control algorithm &#039;minstrel&#039;&lt;br /&gt;
 [80477.588596] phy4: hwaddr 02:00:00:00:01:00 registered&lt;br /&gt;
* Pick a 32-byte &amp;quot;mesh ID&amp;quot;. &amp;quot;hinternet&amp;quot; is used here.&lt;br /&gt;
* Create some mesh interfaces from the two phys that were created (called wlan1 and wlan2 here)&lt;br /&gt;
 think:~# iw dev wlan1 interface add mesh1 type mp mesh_id hinternet&lt;br /&gt;
 think:~# iw dev wlan2 interface add mesh2 type mp mesh_id hinternet&lt;br /&gt;
* See the new devices with &amp;quot;iw dev&amp;quot;&lt;br /&gt;
 think:~# iw dev&lt;br /&gt;
 phy#4&lt;br /&gt;
 	Interface mesh2&lt;br /&gt;
 		ifindex 22&lt;br /&gt;
 		type mesh point&lt;br /&gt;
 	Interface wlan2&lt;br /&gt;
 		ifindex 19&lt;br /&gt;
 		type managed&lt;br /&gt;
 phy#3&lt;br /&gt;
 	Interface mesh1&lt;br /&gt;
 		ifindex 21&lt;br /&gt;
 		type mesh point&lt;br /&gt;
 	Interface wlan1&lt;br /&gt;
 		ifindex 18&lt;br /&gt;
 		type managed&lt;br /&gt;
* Bring &amp;quot;UP&amp;quot; the mesh interfaces&lt;br /&gt;
 think:~# ip link set dev mesh1 up&lt;br /&gt;
 think:~# ip link set dev mesh2 up&lt;br /&gt;
* Tune the interfaces to the same channel&lt;br /&gt;
 think:~# iw dev mesh1 set channel 1&lt;br /&gt;
 think:~# iw dev mesh2 set channel 1&lt;br /&gt;
* At this point, the mesh interfaces should be able to &amp;quot;hear&amp;quot; each other and create adjacencies&lt;br /&gt;
 think:~# iw dev mesh1 station dump&lt;br /&gt;
 Station 02:00:00:00:01:00 (on mesh1)&lt;br /&gt;
 	inactive time:	612 ms&lt;br /&gt;
 	rx bytes:	17352&lt;br /&gt;
 	rx packets:	171&lt;br /&gt;
 	tx bytes:	264&lt;br /&gt;
 	tx packets:	3&lt;br /&gt;
 	signal:  	-50 dBm&lt;br /&gt;
 	tx bitrate:	1.0 MBit/s&lt;br /&gt;
 	mesh llid:	46469&lt;br /&gt;
 	mesh plid:	33020&lt;br /&gt;
 	mesh plink:	ESTAB&lt;br /&gt;
 think:~# iw dev mesh2 station dump&lt;br /&gt;
 Station 02:00:00:00:00:00 (on mesh2)&lt;br /&gt;
 	inactive time:	912 ms&lt;br /&gt;
 	rx bytes:	22127&lt;br /&gt;
 	rx packets:	232&lt;br /&gt;
 	tx bytes:	594&lt;br /&gt;
 	tx packets:	8&lt;br /&gt;
 	signal:  	-50 dBm&lt;br /&gt;
 	tx bitrate:	1.0 MBit/s&lt;br /&gt;
 	mesh llid:	33020&lt;br /&gt;
 	mesh plid:	46469&lt;br /&gt;
 	mesh plink:	ESTAB&lt;/div&gt;</summary>
		<author><name>98.156.77.43</name></author>
	</entry>
</feed>