Difference between revisions of "Mesh/Firmware"

Mesh/Firmware (view source)

739 bytes added , 20:37, 30 April 2015

→‎Compatible devices: Adding bits about target devices

186

edits

@@ Line 276: / Line 276: @@
 = Compatible devices =
-We should have ready-made images for:
+We're going to target ar71xx devices with decent storage + processing speed + memory for "router board" nodes.
-*One really cheap indoor router (with 3G usb stick support?) like [http://wiki.openwrt.org/toh/tp-link/tl-wr703n TP-Link TL-WR703N]
+Right now we're using for "router board" nodes:
-*One nice high-speed indoor router (300 mbps 802.11n)
+WD MyNet N750 and/or TP-Link TL-WDR4300
-*Ubiquiti hardware. Most of the AirMAX stuff.
+The MyNets are no longer in production, but the TL-WDR4300 are the exact same board, just with external antennas.
+Then we can use "extender nodes" which can basically just do wifi and bridging. This would be basically any router which supports openwrt. We'll probably begin by targeting a variety of ubiquiti long-distance high power radios (Nanostation M line, Bullet M line, Picostation M line, Nanobridge/beam/etc).
+Really the extender nodes are just doing dumb bridging. The only reason we want them to run openwrt is so that they can do some fancier address assignment with [https://github.com/sudomesh/notdhcp notdhcp] and have some nice UI features. We could actually setup something like 2 ends of an airfiber and just configure them the way we want (wouldn't need the dynamic features of notdhcp).