Difference between revisions of "Emergent Network Field Day"

From Makers Local 256
Jump to: navigation, search
m (From IRC: Added notes about power solution for wr703n's)
m (Back to being an event page!)
Line 6: Line 6:
  
 
==Overview==
 
==Overview==
Building a wireless mesh network up with DNS, captive portal webpage, and communication infrastructureA tiny "internet" for disaster stricken areas.
+
A field day type event like Ham radio operators do to test out emergency communication only with ethernet and wifi links to build a computer networkBasically, how quickly and to what extent can we create an computer network that operates similar to the Internet.
  
  
Line 32: Line 32:
 
==Progress==
 
==Progress==
  
===General===
 
 
====03/30/2012====
 
* To catch everyone up, as the wiki has been neglected :( :
 
** At last count we have 3 WRT54G devices meshing using [[User:Brimstone|Brimstone]]'s custom slim build.
 
** [[User:strages|strages]] purchased/obtained 8 TP-Link wr710N wireless routers, 3 of which have been flashed with openwrt. 
 
** [[User:strages|strages]] purchased a fair sized clear blue water proof box and an 1800mAh battery pack that might work well for the wr710n's.  Testing will ensue.
 
** [[User:strages|strages]] purchased a 45W solar array with power converter for use with the field day portion of this project.
 
** [[User:strages|strages]] purchased a 5W solar panel for use with the field day portion of this project.
 
 
====07/09/2012====
 
* Stopped by Batteries+ and found 42Ah AGM battery for $76.99 and battery boxes for $12.99.  The battery boxes should provide decent weather proofing so long as they're not submerged.  Might want to paint them white so as to not absorb so much heat (they're black plastic).  Still trying to workout a small footprint solar charging solution.
 
 
====01/21/2013====
 
* Successfully configured an AP and adhoc(mesh) interface on 3 of the 8 routers and they all function properly!  Mesh is mesh and AP let's everyone connect into the network over wireless.  Still some configuration I have to setup for the physical LAN interfaces.  Thanks to [http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config-sophisticated this website] I now have a uci config that involves 2 line changes per device.
 
 
===From Twitter===
 
* [[User:strages|strages]] Huzzah! First mesh node toward @krs and I's emergent network plans. #makerslocal 26 Sep
 
 
* [[User:strages|strages]] Huzzah! Freifunk wiki.freifunk.net/Freifunk_Firmw… flashed to the first mesh node! #makerslocal #opensourcemesh 27 Sep
 
 
* [[User:strages|strages]] Achievement unlocked! [[User:JimShoe|JimShoe]] found a wrt-54gv2 in a box. Yay for having a second node! #makerslocal #opensourcemesh 28 Sep
 
** Later found to be a WAP54G v2
 
 
* [[User:strages|strages]] Ran down some rather nice tutorials for setting up mesh networks using Freifunk. This should help. #makerslocal 29 Sep
 
 
* [[User:strages|strages]] wewt! third mesh node obtained! #makerslocal 3 Oct
 
 
* [[User:brimstone|brimstone]] Debricking one of @strages's APs for his mesh project using only parts found around #makerslocal [http://twitpic.com/6uulda| twitpic.com/6uulda] 3 Oct
 
 
* [[User:strages|strages]] Totally got a WAP54gv2(Yancey) and WRT54gv5(Josh) meshing with OLSR :D #makerslocal 4 Oct
 
 
* [[User:strages|strages]] Alright, unbricked the third node again. Loaded dd-wrt with olsr on it. Might have it talking to the others in the mesh. #makerslocal 6 Oct
 
 
* [[User:strages|strages]] 4th mesh node obtained! Brother-in-law gave me a WRT160N :D #makerslocal 7 Oct
 
 
* [[User:strages|strages]] Fifth wireless mesh node obtained! A WRT54G v2.2 with swappable antennas! I shall call it Lincoln after where I got it. #makerslocal 13 Oct
 
 
* [[User:strages|strages]] Wifi mesh project update: five nodes, three water proof enclosures, one solar panel. Four more nodes in the future. #makerslocal 14 Oct
 
 
* [[User:strages|strages]] Found another water proof box! Bringing the total up to 4 :D #makerslocal #mesh 15 Oct
 
 
* [[User:strages|strages]] Found node six while unpacking boxes at the shop! :D ...and it shall be called Butterscotch #makerslocal 17 Oct
 
 
* [[User:strages|strages]] Pic of my first 6 mesh nodes all freshly labeled http://www.flickr.com/photos/stragesv3/6264767887/in/photostream #makerslocal 20 Oct
 
 
* [[User:strages|strages]] Huzzah the 3 new mesh nodes from Birmingham showed up! Thanks @xhizu :D #makerslocal 02 Dec
 
 
* [[User:strages|strages]] Looking heavily into http://smesh.org for my mesh network project. Working on finding or compiling a newer image to load.  04 Jan
 
 
* [[User:strages|strages]] Settling on kmod-batman-adv for my mesh network. Layer 2 routing for the win. #makerslocal 06 Jan
 
 
* [[User:strages|strages]] Just ordered 3 TP-Link TL-WR703N for my mesh network project.  #makerslocal 13 Jan
 
 
* [[User:strages|strages]] [[User:brimstone|@brimston3]] is working pretty hard on a openwrt backfire image for 2MB devices containing batman-adv #makerslocal 16 Jan
 
* [[User:brimstone|brimstone]] Got #openwrt finally under 2MB for this wrt54gs for @strages' mesh at #makerslocal 20 Jan
 
* [[User:strages|strages]] Huzzah! TP-Link WR703Ns have arrived! Time to get back to work on mesh nodes! #makerslocal 19 March
 
* [[User:strages|strages]] Huzzah! All 8 wr703n APs flashed with openwrt. Now to get them all meshing... #makerslocal 31 March
 
* [[User:strages|strages]] Huzzah! Three wr703n's meshing! #ranoutofusbports #makerslocal http://pic.twitter.com/0vg5cHMb 07 Apr
 
 
===From IRC===
 
====01/13/12====
 
* <brimstone> 03:00:31  +brimstone | !note strages* At this point in our program, brimstone takes a victory lab as Josh is now running a usable openwrt.
 
* <brimstone> 03:01:38  +brimstone | 1708032 works
 
* <brimstone> 03:02:47  +brimstone | 1773568 doesn't
 
* <brimstone> 03:06:18  +brimstone | i could hack it in there like this one
 
* <brimstone> 03:09:01  +brimstone | let's see if i can sneak batman-adv into it now
 
* <brimstone> 03:11:02  +brimstone | !note strages* Now turn to page 2: batman_adv: B.A.T.M.A.N. advanced 2011.2.0 (compatibility version 12) loaded
 
* <brimstone> 03:12:35  +brimstone | !note strages* i apparently have removed wifi drivers, this is a beast for another day, monday perhaps
 
====01/17/12====
 
* [23:16] <+brimstone> !note strages* wifi passes traffic in adhoc mode
 
====01/18/12====
 
* [08:56] <strages_work> how did you get it working?
 
* [08:56] <+brimstone> which part?
 
* [08:56] <strages_work> I guess what I'm asking, what had to be removed to get wifi and batman-adv in there
 
* [08:57] <+brimstone> ssh, firewall support, anything crypto related
 
* [08:57] <+brimstone> usb and network file system support from the kernel
 
* [08:57] <+brimstone> some wireless regulation stuff (crda)
 
* [08:58] <+brimstone> pretty progress bars off wget
 
* [08:58] <+brimstone> a hand full of other things
 
* [08:58] <+brimstone> i don't remember all right now
 
* [09:06] <strages_work> fantastic work
 
* [09:06] <strages_work> thank you
 
* [09:09] <+brimstone> it's not quite done
 
* [09:09] <+brimstone> there's still not a good way to change configurations
 
* [09:11] <strages_work> but one can be set initially?
 
* [09:12] <+brimstone> yes, but i'm not sure if that's a good thing to do
 
====01/19/12====
 
* [14:44] <+brimstone> strages_work: why did i ask you to send me that lsmod and dmesg output?
 
* [14:45] <strages_work> oh, you were going to check what driver they were using to do VAPs
 
* [14:46] <strages_work> you might find some other interesting stuff in there as well
 
* [14:47] <+brimstone> it's interesting that a lot of the hardware's the same
 
* [14:47] <strages_work> right
 
* [14:48] <strages_work> *it's mostly just memory contraints
 
* [14:48] <strages_work> cheaper manufacturing
 
* [14:48] <+brimstone> i think the multiple VAPs are controlled by hostapd, and i don't have space for that graaaaa
 
====01/20/12====
 
* 17:19 <+brimstone> strages_work: i tweaked the lzma settings and saved another k out of the kernel
 
* 17:51 <+brimstone> Kernel: Old: 809812 New: 784844 Size change: -24968
 
* 17:51 <+brimstone> Busybox: Old: 407679 New: 407679 Size change: 0
 
* 17:51 <+brimstone> Squashfs: Old: 846014 New: 845889 Size change: -125
 
* 17:51 <+brimstone> TRX: Old: 1794048 New: 1765376 Size change: -28672
 
* 17:51 <+brimstone> Room: 4096
 
* 17:51 <+brimstone> It's good!
 
* 17:57 < strages_shop> :D
 
* 17:57 <+brimstone> this might be it
 
* 17:57 <+brimstone> but it may still give you problems
 
* 17:57 < strages_shop> oh man oh man oh man
 
* 17:57 <+brimstone> i removed some of the routing stuff
 
* 17:57 <+brimstone> and the qos
 
* 17:57 <+brimstone> and some queuing stuff
 
* 17:57 < strages_shop> hmm
 
* 17:58 <+brimstone> but it's got batman, and wifi firmware, and it's small enough to flash
 
* 17:58 < strages_shop> works on Josh?
 
* 17:58 <+brimstone> yup
 
====01/21/12====
 
* 14:28 <+brimstone> strages_home: you didn't tell me these routers only had 8MB of ram too
 
* 14:35 < strages_home> I didn't know it was an issue :(
 
* 14:35 <+brimstone> yup
 
* 14:36 <+brimstone> i've got butterscotch in a weird state too
 
* 14:36 <+brimstone> boots up fine, then does something to corrupt itself
 
* 14:42 < strages_home> hmm
 
* 14:43 <+brimstone> i'm reflashing butterscotch with stock openwrt
 
* 14:43 <+brimstone> leaves him at least usable
 
* 14:44 < strages_home> kk
 
* 14:44 < strages_home> he's a 2.2 which means that's fine
 
* 14:44 <+brimstone> yeah, but my firmware should have worked
 
* 14:45 <+brimstone> so there's debugging that
 
* 14:45 < strages_home> oh you were testing it for use on all the devices, not just the 2MB ones
 
* 14:45 <+brimstone> yup
 
* 14:46 < strages_home> buterscotch is 4MB
 
* 14:46 <+brimstone> right
 
* 14:46 <+brimstone> why does the 1.7MB firmware fail?
 
* 14:46 < strages_home> not a clue
 
* 14:47 < strages_home> check lsmod and dmesg dumps for differences?
 
* 14:47 <+brimstone> probably the jffs2 stuff getting in the way
 
* 15:06 <+brimstone> yup, the jffs2 stuff
 
* 15:11 <+brimstone> pfft, batctl wants a debugfs
 
* 15:13 < strages_home> don't need it
 
* 15:38 <+brimstone> debugfs is so biiiiiiig
 
* 15:39 <+brimstone> +70k!
 
* 17:54 <+brimstone> Mesh: Built
 
 
====01/23/12====
 
* [09:56] <strages_work> brimstone: is there a config being written somewhere on Josh that contrains all the settings for the mesh?
 
* [09:56] <+brimstone> no, josh doesn't have room to save configs
 
* [09:57] <+brimstone> but /etc/init.d/mesh-setup and /etc/init.d/mesh-finish are the static files i hard coded into the firmware to set it up
 
* [09:57] <strages_work> ok
 
* [09:59] <strages_work> I'm thinking we need to replicate those settings in a config file for the 4MB devices and just run straight openwrt 10.3.1 on them.  This would let us use tools like batctl etc on at least some of the devices.
 
* [10:01] <+brimstone> we could also just pull the batctl binary from the package and replace it on the 4MB ones
 
* [10:01] <+brimstone> the stock firmware has a lot of extra    baggage
 
* [10:01] <+brimstone> ppp, luci, etc
 
* [10:03] <strages_work> can hostap be installed like that as well?
 
* [10:03] <+brimstone> yes
 
* [10:04] <strages_work> ok
 
* [10:06] <strages_work> so right now, we can install your openwrt image on all the devices (at least the ones we've tested thus far), they'll mesh, and we add packages as needed given room on the device?
 
* [10:06] <+brimstone> should be able to
 
* [10:06] <+brimstone> i made sure opkg was still on there
 
* [10:07] <strages_work> alright because I'm shooting for as little setup time as possible given that it's supposed to be an emergency network
 
* [10:08] <strages_work> there are a few spinoff ideas after I finish this one utilizing the same or similar setup
 
* [10:09] <strages_work> like having them in client mode on one of the virtual aps and auto connection to open wireless networks effectively extending the range of existing infrastructure
 
* [10:09] <strages_work> *auto connecting
 
* [10:10] <+brimstone> that'll be gross if you're not careful
 
* [10:10] <strages_work> right, it's just an idea
 
* [10:10] <+brimstone> as long as you're only linking to one network it should be ok
 
* [10:11] <strages_work> or use a decent routing protocol to prevent routing loops
 
* [10:12] <+brimstone> it's more then that
 
* [10:12] <+brimstone> you can't link to 192.168.1.0/24 networks, you'll get conflicting ips
 
* [10:12] <+brimstone> you'll knock valid users off networks, or your own users
 
* [10:13] <strages_work> that seems fixable by using some other network range though by default...
 
* [10:13] <+brimstone> you don't control the open wifis you're connecting to
 
* [10:13] <+brimstone> you might be able to do some double/triple nat weirdness, but that's gross
 
* [10:15] <strages_work> sure I would have difficulty hosting services on the network, but that wasn't really the plan
 
* [10:15] <+brimstone> you also start limited the range as you're adding additional TTLs
 
* [10:15] <+brimstone> or subtracting as the case may be
 
* [10:15] <strages_work> true
 
* [10:17] <strages_work> regardless this is all hypothetical right now.  Getting everything working as an emergency network is the plan then it's building communication services on top of that
 
* [10:17] <+brimstone> yup
 
* [10:17] <strages_work> captive portal, message board, chat, possibly crude voip
 
* [10:18] <strages_work> I wonder if android can do batman-adv
 
 
====02-19-2013====
 
<strages_work> say a wr703n uses 200mA (.2A) peak, I know it doesn't but humor me.
 
<strages_work> that 1W peak power (5V x.2A)
 
<strages_work> *that's
 
<strages_work> .2A x 24hrs = 4.8Ah
 
<strages_work> so we'll round up and say a 6Ah battery ought to suffice
 
<strages_work> now let's day our area gets 6 hours optimal sunlight per day
 
<strages_work> *let's say
 
<strages_work> if I had a 6V panel and a 6V battery, then I would need a 1W panel to keep it topped off?
 
<brimstone> you would need to charge that 6Ah battery in 6 hours
 
<strages_work> yeah
 
<strages_work> does all this sound about right for keeping a mesh node going?
 
<strages_work> ideally you would over engineer with a 1.5 or 2 W panel to account for less than optimal conditions
 
 
===Google+===
 
* [[User:Brimstone|Matt Robinson]]  -  I might finally have it. Will start testing tonight. 04:38PM 17 Jan
 
 
==Nodes==
 
# Linksys WRT54GS v5 (Josh)
 
#* S/N: CGN70F2A6509
 
#* OS: custom OpenWrt Backfire 10.03.1 w/ kmod-batman-adv
 
#* Owner: [[User:Strages|strages]]
 
#* Mesh IP: 192.168.10.102
 
# Linksys WRT54G v2.2 (Lincoln)
 
#* S/N: CDF70DCM4969
 
#* OS: custom OpenWrt Backfire 10.03.1 w/ kmod-batman-adv
 
#* Owner: [[User:Strages|strages]]
 
#* Mesh IP: 192.168.10.100
 
#* Status: locked out because of root password being set and no ssh
 
# Linksys WRT54G v2.2 (Butterscotch)
 
#* S/N: CDF70DCE1873
 
#* OS: custom OpenWrt Backfire 10.03.1 w/ kmod-batman-adv
 
#* Owner: [[User:Strages|strages]]
 
#* Mesh IP: 192.168.10.101
 
# TP-Link wr703n (blue leader)
 
#* S/N: 12116803322
 
#* OS: OpenWRT ATTITUDE ADJUSTMENT (bleeding edge, r30919)
 
#* Owner: [[User:Strages|strages]]
 
#* WLAN IP:
 
#* LAN IP:
 
# TP-Link wr703n (blue1)
 
#* S/N: 12116801066
 
#* OS: OpenWRT BARRIER BREAKER (Bleeding Edge, r35445)
 
#* Owner: [[User:Strages|strages]]
 
#* WLAN IP: 10.100.1.1
 
#* LAN IP:
 
# TP-Link wr703n (blue2)
 
#* S/N: 12116802930
 
#* OS: OpenWRT BARRIER BREAKER (Bleeding Edge, r35445)
 
#* Owner: [[User:Strages|strages]]
 
#* WLAN IP: 10.100.1.2
 
#* LAN IP:
 
# TP-Link wr703n (blue3)
 
#* S/N: 11C35603301
 
#* OS: OpenWRT BARRIER BREAKER (Bleeding Edge, r35445)
 
#* Owner: [[User:Strages|strages]]
 
#* WLAN IP: 10.100.1.3
 
#* LAN IP:
 
# TP-Link wr703n (blue4)
 
#* S/N: 11C35603745
 
#* OS: OpenWRT BARRIER BREAKER (Bleeding Edge, r35445)
 
#* Owner: [[User:Strages|strages]]
 
#* WLAN IP: 10.100.1.4
 
#* LAN IP:
 
# TP-Link wr703n (blue5)
 
#* S/N: 11C35603488
 
#* OS: OpenWRT BARRIER BREAKER (Bleeding Edge, r35445)
 
#* Owner: [[User:Strages|strages]]
 
#* WLAN IP: 10.100.1.5
 
#* LAN IP:
 
# TP-Link wr703n (blue6)
 
#* S/N: 11C35603174
 
#* OS: OpenWRT BARRIER BREAKER (Bleeding Edge, r35445)
 
#* Owner: [[User:Strages|strages]]
 
#* WLAN IP: 10.100.1.6
 
#* LAN IP:
 
# TP-Link wr703n (blue7)
 
#* S/N: 11C35603510
 
#* OS: OpenWRT BARRIER BREAKER (Bleeding Edge, r35445)
 
#* Owner: [[User:Strages|strages]]
 
#* WLAN IP:
 
#* LAN IP:
 
 
==Costs==
 
* $5 for the VW solar panel from Unclaimed Baggage
 
* $75 for 3 [http://www.ebay.com/itm/TP-Link-TL-WR703N-b-g-n-150Mbps-Nano-Mini-Portable-WiFI-Wireless-N-3G-Router-AP-/150786211264?pt=COMP_EN_Routers&hash=item231b8efdc0 TP-Link TL-WR703N]
 
* $150 [http://www.harborfreight.com/45-watt-solar-panel-kit-90599.html 45W solar array and power converter] from Harbor Frieght
 
* $60 [http://www.harborfreight.com/5-watt-solar-battery-charger-41144.html 5W solar panel] from Harbor Frieght
 
 
==Notes==
 
* a 7Ah battery should run a WRT54G for ~29 hours [http://www.skifactz.com/wifi/solar_wrt54g3.htm]
 
* "And as a reference point, it was found that a 55 AH SLA battery with a 45W amorphous solar panel under decidedly sub-optimal conditions can run a WRT54G indefinitely." [http://www.hsmm-mesh.org/section-blog/37-hardware-faqs/56-how-long-will-a-wrt54g-run-from-a-battery.html]
 
* With the custom 2MB openwrt-10.3.1 image that [[User:brimstone|brimstone]] is developing, if there is no mesh IP defined it will assume 192.168.10.2 .
 
* Multiple SSIDs cannot be done with the custom 2MB image, but can on the 4MB devices.
 
** This is due to the limited number of packages available due to memory constraints.
 
* To enter failsafe mode on the wr703n routers, hit the reset switch multiple times immediately upon plugging it in.  The blue light will begin blinking rapidly if done correctly.  You should now be able to set your ethernet IP to 192.168.1.233 and telnet to 192.168.1.1.  Run the command '''mount_root''' to mount the root filesystem and edit files to restore connectivity.
 
** running the command '''firstboot''' restores deafult values
 
 
==Packages needed==
 
* terminfo
 
** libncurses
 
*** nano
 
* kmod-batman-adv
 
 
==UCI config==
 
<pre>
 
#!/bin/sh
 
 
### Main radio0 will broadcast one AP with no encryption
 
### Another VAP in adhoc mode is added to main radio0.
 
 
### Node-specific settings
 
read -p "Hostname: " HOSTNAME
 
read -p "IP: " IP
 
 
### These parameters should be consistent across all nodes
 
export NETMASK="255.255.252.0"
 
export DNS=""
 
export GATEWAY=""
 
export PUBLIC_ESSID="The Mesh"
 
export PUBLIC_BSSID="DE:AD:BE:EF:CA:FE"
 
export ADHOC0_BSSID="CA:CA:CA:CA:CA:00"
 
export ADHOC0_ESSID="meshtrunk"
 
export ADHOC0_CHANNEL="1"
 
 
### Ensure of populating /etc/config/wireless with
 
### autodetected wifi-device entries (radioX)
 
### to get all list_capab and hwmode correct. Otherwise
 
### OpenWRT might fail to configure the radio properly.
 
wifi detect >>/etc/config/wireless
 
 
### Clear preexisting wifi-iface sections to avoid conflicts or dups
 
( for i in `seq 0 9` ; do echo "delete wireless.@wifi-iface[]" ; done ) | uci batch -q
 
 
### Create /etc/config/batman-adv if it's not there yet.
 
uci import -m batman-adv </dev/null
 
 
echo "
 
set system.@system[0].hostname=$HOSTNAME
 
 
set batman-adv.bat0=mesh
 
set batman-adv.bat0.gw_mode=client
 
 
#set network.wan.proto=dhcp
 
set network.lan.ipaddr=$IP
 
set network.lan.netmask=$NETMASK
 
set network.lan.dns='$DNS'
 
set network.lan.gateway=$GATEWAY
 
set network.lan.ifname='bat0'
 
set network.mesh=interface
 
set network.mesh.ifname=adhoc0
 
set network.mesh.proto=batadv
 
set network.mesh.mtu=1528
 
set network.mesh.mesh=bat0
 
 
set wireless.radio0=wifi-device
 
set wireless.radio0.channel=$ADHOC0_CHANNEL
 
set wireless.radio0.disabled=0
 
set wireless.radio0.phy=phy0
 
set wireless.radio0.macaddr=
 
 
add wireless wifi-iface
 
set wireless.@wifi-iface[-1].device=radio0
 
set wireless.@wifi-iface[-1].encryption=none
 
set wireless.@wifi-iface[-1].network=lan
 
set wireless.@wifi-iface[-1].mode=ap
 
set wireless.@wifi-iface[-1].ssid='$PUBLIC_ESSID'
 
set wireless.@wifi-iface[-1].bssid=$PUBLIC_BSSID
 
 
add wireless wifi-iface
 
set wireless.@wifi-iface[-1].device=radio0
 
set wireless.@wifi-iface[-1].ifname=adhoc0
 
set wireless.@wifi-iface[-1].encryption=none
 
set wireless.@wifi-iface[-1].network=mesh
 
set wireless.@wifi-iface[-1].mode=adhoc
 
set wireless.@wifi-iface[-1].bssid=$ADHOC0_BSSID
 
set wireless.@wifi-iface[-1].ssid='$ADHOC0_ESSID'
 
set wireless.@wifi-iface[-1].mcast_rate=11000
 
set wireless.@wifi-iface[-1].hidden=true
 
commit" \
 
| uci batch
 
</pre>
 
 
===What needs to be done===
 
*
 
  
 
==References==
 
==References==
* [http://wirelessafrica.meraka.org.za/wiki/index.php/DIY_Mesh_Guide Building a Rural Wireless Mesh Network]
 
* [http://www.skifactz.com/wifi/solar_wrt54g3.htm Solar WRT54G]
 
* [http://www.hsmm-mesh.org/ HSMM-Mesh]
 
* [http://fabfi.fabfolk.com/distribution/ FabFi firmware and CNC-able reflector designs]
 
* [http://www.i2cchip.com/linksys.html Data logging on a WRT54G through serial port hack]
 
* [http://www.zx80.org/sd-mmc-storage-add-on-for-wrt54g-v2-2.html Adding an SD card slot]
 
* [http://www.dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash Recovering from a bad flash]
 
* [http://www.smesh.org/ SMesh]
 
* [https://openwrt.org/ OpenWRT]
 
* [http://www.open-mesh.org/wiki/batman-adv B.A.T.M.A.N. Advanced]
 
* [http://pizza.hskflashcards.com/index.php?page=B.A.T.M.A.N.+Advanced+on+OpenWrt+How-To Awesome tutorial for installing and configuring batman-adv]
 
* [http://jtagcables.com/jtag-cable Building a JTag cable]
 
* [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=20205 Using the JTag cable you just built]
 
 
* [http://drwho.virtadpt.net/archive/2011/03/15/project-byzantium-sprint-1 The Doctor's Byzantium Sprint #1 notes from March 2011 (wish I had known about this sooner)]
 
* [http://drwho.virtadpt.net/archive/2011/03/15/project-byzantium-sprint-1 The Doctor's Byzantium Sprint #1 notes from March 2011 (wish I had known about this sooner)]
 
* [http://wiki.hacdc.org/index.php/BATMAN-Advanced_Setup HacDC's how-to on setting up batman-adv in Linux]
 
* [http://wiki.hacdc.org/index.php/BATMAN-Advanced_Setup HacDC's how-to on setting up batman-adv in Linux]
Line 419: Line 40:
 
* [http://wiki.openwrt.org/toh/tp-link/tl-wr703n wr703n OpenWRT wiki]
 
* [http://wiki.openwrt.org/toh/tp-link/tl-wr703n wr703n OpenWRT wiki]
 
* [http://www.physorg.com/news/2012-02-emergency-network-natural-disasters.html Similar idea being done in Arkansas and partially funded by the NSF]
 
* [http://www.physorg.com/news/2012-02-emergency-network-natural-disasters.html Similar idea being done in Arkansas and partially funded by the NSF]
* [http://wiki.openwrt.org/toh/tp-link/tl-mr11u TP-Link tl-mr11u]: equivalent to the wr702n but with a 2000mAh battery!
 
 
* [http://astro.unl.edu/classaction/animations/coordsmotion/daylighthoursexplorer.html daylight calculator]
 
* [http://astro.unl.edu/classaction/animations/coordsmotion/daylighthoursexplorer.html daylight calculator]
 
* [http://antipastohw.blogspot.com/2012/08/how-to-build-diy-perpetually-powered.html DIY solar powered wifi] promising resource
 
* [http://antipastohw.blogspot.com/2012/08/how-to-build-diy-perpetually-powered.html DIY solar powered wifi] promising resource
* [http://downloads.openwrt.org/snapshots/trunk/ar71xx/ trunk for the wr703n chipset]
 
  
 
[[Category:Event]]                                                  <!--MAKE AS MANY CATEGORIES AS YOU NEED-->
 
[[Category:Event]]                                                  <!--MAKE AS MANY CATEGORIES AS YOU NEED-->

Revision as of 17:57, 3 March 2013

Creator:
Strages
Status:
Planning
Born On:
21:17, 26 September 2011 (CDT)
Last Updated:
17:57, 03 March 2013 (CDT)

Overview

A field day type event like Ham radio operators do to test out emergency communication only with ethernet and wifi links to build a computer network. Basically, how quickly and to what extent can we create an computer network that operates similar to the Internet.


Goals

  • Portable power
    • batteries, solar, wind turbines, etc
  • Mesh network nodes capable of being run on available power.
    • OpenWRT capable devices
  • Various antenna types
  • DNS server
  • DHCP server
  • Captive portal page containing emergency and general information for people joining the network.
  • Communication options
    • IRC
    • BBS?
    • SMS gateway
    • Jabber server
  • QR code ( http://delivr.com/qr-code-generator ) stickers and/or stencils containing a link or information about the network in a given area. Keep with the nodes and/or on the nodes.
  • Have a file repo available and linked off the captive portal containing mesh network packages, etc. Piratebox ( http://wiki.daviddarts.com/PirateBox ) perhaps.
  • Local copies of Wikipedia or Appropedia for reference use.

Location

?

Progress

References