September 24 at 5:56pm
The antennas arrived today! 2 x 9dBi and 2 x 5dBi outdoor dual-band antenna (2.4/5.. Now I just need to score some RP-TNC to N adapters. I have enough 5' LMR-400 jumpers with RP-TNC connectors to get all four hooked up. I need to find some nema enclosures to pole mount the APs.
So the question becomes, do I eschew diversity and go with one antenna per AP, or do I hook up two APs with two antenna each. I'm leaning towards one antenna per AP since I'm not going to be serving mobile clients. What does everyone else think?
September 24 at 6:14pm
Today's arrival brings me to the following inventory:
HSMM Mesh "Go-Package":
Site 1:
Cisco/Linksys WRT54G v2 running v1.0 firmware
Cisco 7961G-GE IP Phones running 8.5.4 SIP firmware
Cisco 7914 Extension Module (14 extension sidecar)
Cisco 2940 8-port Managed Swich
Cisco ATA 187 two line ATA
Grandstream HT-286 ATA
Raspberry Pi running Asterisk and Prosody
9dBi outdoor collinear antenna
Rubbermaid Roughneck 18gl Container
Site 2:
Cisco/Linksys WRT54GL v1.1 running v1.0 firmware
Cisco 7961G IP Phones running 8.5.4 SIP firmware
APC NetBotz 420 IP Camera and Environment Sensor
9dBi outdoor collinear antenna
Rubbermaid Roughneck 3gl Container
Site 3:
Cisco/Linksys WRT54GL v1.1 running v1.0 firmware
Cisco 7961G IP Phones running 8.5.4 SIP firmware
APC NetBotz 420 IP Camera and Environment Sensor
5dBi outdoor collinear antenna
Rubbermaid Roughneck 3gl Container
Site 4:
Cisco/Linksys WRT54GS running v1.0 firmware
Cisco 7961G IP Phones running 8.5.4 SIP firmware
5dBi outdoor collinear antenna
Rubbermaid Roughneck 3gl Container
eBay, here I come. I still need to find:
One more 2-line ATA
Two more NetBotz cameras
Three more PoE injectors to power the APs
Three more data switches
Four nema boxes to pole mount the APs
Four phone patches of some description
Four sturdy collapsible poles
Four power strips
Once that these are found I will have a deployable mesh solution for Field Day or EmComm duties that will support Voice, Video, and Data at four locations (assuming line of site between the antennas or additional mesh hops).
I will keep looking for more WRT54G routers and antennas for mesh infrastructure duties. Although I would suggest something like the Cisoc 1552e APs for actual mesh backhaul. I worry about having a WRT54G atop a tower.
Showing posts with label hsmm. Show all posts
Showing posts with label hsmm. Show all posts
Tuesday, October 1, 2013
Sunday, September 15, 2013
More mesh cross-posts
I am a visual person, so I built a quick diagram of how I visualize a mesh deployment. I have most of these parts already, with the notable exception of the two additional routers, three additional cameras, and additional ATAs.
What does everyone think of this with specific regards to EmComm?
One of the goals of this layout is to allow Incident Commanders, etc, to be able to communicate with disparate agencies via multiple radio systems on multiple frequencies on multiple bands all from any corded or cordless phone. Additionally the option exists to listen to the police/fire/etc scanner from anywhere as well.
Scalability is an core design goal with this architecture with the only limiting factor in theory being the ability of the mesh to scale to lots of node. In theory it will scale to >2000 nodes, but in practice I would be happy to see 500 supported (not that there will ever be a full mesh that size). In the current deployment another limiting factor is the Raspberry Pi that I am using for the voice server. If this were to grow much beyond the size above a larger voice server would be needed.
73,
Richard, KK4JDO
What does everyone think of this with specific regards to EmComm?
One of the goals of this layout is to allow Incident Commanders, etc, to be able to communicate with disparate agencies via multiple radio systems on multiple frequencies on multiple bands all from any corded or cordless phone. Additionally the option exists to listen to the police/fire/etc scanner from anywhere as well.
Scalability is an core design goal with this architecture with the only limiting factor in theory being the ability of the mesh to scale to lots of node. In theory it will scale to >2000 nodes, but in practice I would be happy to see 500 supported (not that there will ever be a full mesh that size). In the current deployment another limiting factor is the Raspberry Pi that I am using for the voice server. If this were to grow much beyond the size above a larger voice server would be needed.
73,
Richard, KK4JDO
Saturday, September 14, 2013
HSMM-MESH a.k.a. "Broadband-Hamnet"
Sorry that I haven't posted in a while. Life has been very busy with shake-ups both personally and professionally. Things are kind of in flux just now but hopefully I can get back to a semi-regular posting schedule. For now though, here is a compilation of some posts that I've made to our local hsmm-mesh Facebook group. For those wondering, you can learn more about hsmm-mesh here.
September 7 at 12:59pm
Got one of my additional routers in. A WRT54GL, got it flashed and a mini mesh created. Also got in touch with a rep from TerraWave/Tessco, a company that manufactures outdoor WiFI antennas and got them to commit to sending us some free antennas. Getting four or five omnis from them hopefully coming this week.
September 3 at 6:51pm
Just found these on eBay. Would really come in handy to powering a WRT54G that is co-located with the antenna!
http://www.ebay.com/itm/Power-Over-Ethernet-Kit-PoE-Linksys-WRT54G-WRT54GL-WRT54GS-WRTU54G-TM-WRT54G-TM-/260973967927
September 10 at 8:27pm
So I still haven't seen the other two routers yet, but I've managed to find some time to work with the two that I have. I've gotten Asterisk running on the R-Pi correctly again (the flash card got corrupted by not shutting down properly) and have two extensions running using Cisco 7961 VoIP phones with a SIP image on them, running one phone per mesh node. I also have a Grandstream HT-286 ATA that I will throw into the mix as soon as another router gets here.
The process is fairly simple as far as the hsmm router configuration is concerned. All that is needed is to edit the /etc/dnsmasq.conf to make DSNMasq hand out the proper DHCP options. Simply add the following to that file:
dhcp-option=150,x.x.x.x
dhcp-option=120,x.x.x.x
dhcp-option=42,x.x.x.x
Replace x.x.x.x with the proper IP addresses of course. Option 150 specifies the TFTP server that the phones will use to download their images and config files. Option 120 points out the SIP server itself, and option 42 points to an NTP server.
If using an R-Pi, keep in mind that it does not have an onboard RTC, so you will need to point to something that can provide the proper time (or use a script as a work-around to set the time on boot, but there are obvious drawbacks to doing that).
One thing that I did notice is that we will want to plan out our subnetting scheme. The method employed by the hsmm image is neat, but not extensible in a large mesh.
Now to find the time to look into how QoS is handled, as well as multicast traffic. Those two things are important on any WiFi network and especially so on a mesh where you lose half of your bandwidth with each RF hop.
I've included a picture showing the two mesh nodes on top of my workbench with the two phones under their respective node. Audio quality was excellent, which I would expect with the two routers less than two feet apart.
Hopefully Terrawave/Tessco will ship those antennas soon. I should have at least one to spare and will throw it and any additional up for grabs when it gets here.
September 11 at 11:10pm
I'm *still* waiting on the two additional routers and five antennas to arrive, but I've been able to get a little done while I'm waiting. It is frustrating only have an hour or so per night to work on this after the kids go to bed.
I've managed to get an additional two phones and a sidecar for the main phone. They are all set up to call each other, as well as some outside agencies. I even added a little personal touch to the phones.
The speed-dials listed as "RF TAC x" will be for extensions that connect to phonepatches via an ATA. This would enable incident commanders to be able to talk via a phone to multiple groups on different radio systems or frequencies. This is a homebrew version of the Cisco IPICS solution that is used by Cisco TACOPS on deployment. Obviously intended to be used only by licensed individuals unless during an actual life-safety emergency.
Currently it is receive only via the internet for the 147.120 stream as I don't have the phone patches built yet, and would need radios for them to connect to as well. But once the proof of concept is done the rest is just "wash-rinse-repeat", right?
I also have an IP camera with environmental sensors running via the mesh as well. This would enable remote observation of triage areas or supply distribution points. It isn't weatherproof, but is fairly sturdy.
My goal is to have deployable go-kits each with a mesh AP, phone, camera, and switch for data connectivity built and ready for the October installfest.
There are other posts, I will have to go back through it and grab some more. I also have non-hsmm stuff to share. I got the Rockmite-40 built, as well as a Pixie II (that I recently gave to a ham that lost his gear in a divorce), with build pictures of both. I also built a go-kit for mt FT-840 that my son and I took to the WMA a while back that I would like to share pictures of. And I just acquired an FT-817 that will be fodder for some future posts. Hopefully I'll have time and inclination to get the posts up.
73,
Richard, KK4JDO
September 7 at 12:59pm
Got one of my additional routers in. A WRT54GL, got it flashed and a mini mesh created. Also got in touch with a rep from TerraWave/Tessco, a company that manufactures outdoor WiFI antennas and got them to commit to sending us some free antennas. Getting four or five omnis from them hopefully coming this week.
September 3 at 6:51pm
Just found these on eBay. Would really come in handy to powering a WRT54G that is co-located with the antenna!
http://www.ebay.com/itm/Power-Over-Ethernet-Kit-PoE-Linksys-WRT54G-WRT54GL-WRT54GS-WRTU54G-TM-WRT54G-TM-/260973967927
September 10 at 8:27pm
So I still haven't seen the other two routers yet, but I've managed to find some time to work with the two that I have. I've gotten Asterisk running on the R-Pi correctly again (the flash card got corrupted by not shutting down properly) and have two extensions running using Cisco 7961 VoIP phones with a SIP image on them, running one phone per mesh node. I also have a Grandstream HT-286 ATA that I will throw into the mix as soon as another router gets here.
The process is fairly simple as far as the hsmm router configuration is concerned. All that is needed is to edit the /etc/dnsmasq.conf to make DSNMasq hand out the proper DHCP options. Simply add the following to that file:
dhcp-option=150,x.x.x.x
dhcp-option=120,x.x.x.x
dhcp-option=42,x.x.x.x
Replace x.x.x.x with the proper IP addresses of course. Option 150 specifies the TFTP server that the phones will use to download their images and config files. Option 120 points out the SIP server itself, and option 42 points to an NTP server.
If using an R-Pi, keep in mind that it does not have an onboard RTC, so you will need to point to something that can provide the proper time (or use a script as a work-around to set the time on boot, but there are obvious drawbacks to doing that).
One thing that I did notice is that we will want to plan out our subnetting scheme. The method employed by the hsmm image is neat, but not extensible in a large mesh.
Now to find the time to look into how QoS is handled, as well as multicast traffic. Those two things are important on any WiFi network and especially so on a mesh where you lose half of your bandwidth with each RF hop.
I've included a picture showing the two mesh nodes on top of my workbench with the two phones under their respective node. Audio quality was excellent, which I would expect with the two routers less than two feet apart.
Hopefully Terrawave/Tessco will ship those antennas soon. I should have at least one to spare and will throw it and any additional up for grabs when it gets here.
September 11 at 11:10pm
I'm *still* waiting on the two additional routers and five antennas to arrive, but I've been able to get a little done while I'm waiting. It is frustrating only have an hour or so per night to work on this after the kids go to bed.
I've managed to get an additional two phones and a sidecar for the main phone. They are all set up to call each other, as well as some outside agencies. I even added a little personal touch to the phones.
The speed-dials listed as "RF TAC x" will be for extensions that connect to phonepatches via an ATA. This would enable incident commanders to be able to talk via a phone to multiple groups on different radio systems or frequencies. This is a homebrew version of the Cisco IPICS solution that is used by Cisco TACOPS on deployment. Obviously intended to be used only by licensed individuals unless during an actual life-safety emergency.
Currently it is receive only via the internet for the 147.120 stream as I don't have the phone patches built yet, and would need radios for them to connect to as well. But once the proof of concept is done the rest is just "wash-rinse-repeat", right?
I also have an IP camera with environmental sensors running via the mesh as well. This would enable remote observation of triage areas or supply distribution points. It isn't weatherproof, but is fairly sturdy.
My goal is to have deployable go-kits each with a mesh AP, phone, camera, and switch for data connectivity built and ready for the October installfest.
There are other posts, I will have to go back through it and grab some more. I also have non-hsmm stuff to share. I got the Rockmite-40 built, as well as a Pixie II (that I recently gave to a ham that lost his gear in a divorce), with build pictures of both. I also built a go-kit for mt FT-840 that my son and I took to the WMA a while back that I would like to share pictures of. And I just acquired an FT-817 that will be fodder for some future posts. Hopefully I'll have time and inclination to get the posts up.
73,
Richard, KK4JDO
Subscribe to:
Posts (Atom)
