Ask Slashdot: Ad-Hoc Wireless Mesh Network For Emergency Vehicles?
First time accepted submitter Texaskilt writes "I am looking to put together a mobile mesh network for my volunteer fire department and would like some recommendations from the Slashdot crowd. Ideally, the network would consist of cheap wireless routers (Linksys WRT-type) mounted on each vehicle. From there, tablets or other wireless devices could connect to the router. When the vehicles are in the station, the routers would auto-connect to the WiFi network to receive calls for service and other updates. When out on a call, the router would form an ad-hoc network with other vehicles on the scene. If a vehicle came into range of an Internet 'hotspot,' it would notify other vehicles and become a gateway for the rest of the 'ad-hoc' networked vehicles. I've looked at Freifunk for this, but would like some other options. Recommendations please?"
Of course at least 1/3 of the posts will try to knock you down with the blather "if you have to ask, you're not the right person for the job".
If you want news from today, you have to come back tomorrow.
http://project-byzantium.org/
I have to wonder though, what's wrong with good old fashioned radios.
Why not just use a cellular hotspot?
While ambitious, this is the wrong path to go down. Great for hobbyists, but is NOT what emergency services needs. Emergency services needs reliability. If your department can't afford a few mobile broadband units, you should seriously look into throwing a couple more raffles or asking for more money from the city/county/township/state.
Not sure, but have you checked out this open source initiative? http://project-byzantium.org/faqs/
Be careful about liability. What if something doesn't work right and a loss is blamed on the network?
Tp-link 1043 + openwrt.
Having Emergency vehicles depend on an ad-hoc network seems risky at best and a potential disaster at worst. Might be best to just stick to the telephone (or whatever you currently use) and leave the flaky network to the non-life-critical tasks.
"Maybe this world is another planet's hell"
Aldous Huxley
A lesson i have learned over the years; when spending other peoples money always ask the question, "is it better, or just different?". I dont know the size of your operation, or what state you are in, but analogue, trunking, IP (opensky...) radios are normally more reliable, which is the name of the game. Other services like LTE may be the best bet (location location location), and if you can find the right people to talk to at the state you would be surprised the kind of things the state will spend money on.
Even the most basic of smartphones have good tethering capabilities. Why not simply go with normal phones? Wi-fi on the station, and mobile data when not? Generally, the simpler an idea is, the better.
What is it for?
No really......
You have told us how you *think* you want to communicate, but not what information you are communicating.
The first step of any IT problem is to adapt your ideas to fit users needs........... not adapt users needs to fit your ideas.
Anyone quoted by a reporter knows how little they understand
Don't believe what you read is the truth.
"Wireless Mesh Network" sure sounds sexy, doesn't it. And what Fire Department wouldn't want more sexy shit than, say, the Police Department?
for a Emergency Vehicles i would propose that you take a look at APRS http://en.wikipedia.org/wiki/Automatic_Packet_Reporting_System used by HAM guys. this is the robustest wireless protocoll i am aware of, also the range is better than WLAN.
This is essentially being done by the Emergency Medical Service in Virginia Beach, Virginia, where every ambulance is a hot-spot -- but only for the sake of conveying electronically collected medical reports and transmitting them (via VPN) to "the cloud" where they can rapidly be seen by receiving hospitals and by other units on the same incident. (Yes, we've addressed all HIPAA concerns.) It is *not* being done as a means to communicate calls for service. In Virginia Beach, calls for service are transmitted via a VPN on the commercial cellphone service, with a municipal trunked radio system as a backup.
My advice: Field test the heck out of the routers. Make sure they can survive the weird electric power supply anamolies that occur during standard vehicular operations.
http://www.mikrotik.com/ devices might have what you want. They are inexpensive, very flexible and have interesting mesh modes I have yet to try out and will run directly off your fire engines battery system with some power filtering and clamping. Whatever you do in general you should have a play, write a clear specification with all sorts of test cases and run a small trial for a while. Make the devices/solution meet your requirements, not the other way around or you will be sorry.
Get a budget. Go with a commercial solution. Homebrew is for people hacking and tinkering with stuff. You need something designed to be rugged and meet your requirements.
Astro radios, tetra radios, other systems designed for emergency services are all good options. Go talk to the IT staff at your local cop shop to see what they're doing and if you can nail down their vendor contacts. It will go a long way. Don't have your volunteers trying to reboot the routers when it's more important for them to be saving lives.
Talk to your Motorola dealer. You're using trunking Motorola radios, and they have IP built right in. You don't have enough bandwidth allocated to be able to do broadband stuff, but, given that you don't have a real objective stated, that's okay. You'll get one additional radio per vehicle, plus a godawful expensive adapter, and plug it into your laptops in your vehicles.
Seriously - ad hoc crap is worse than nothing to emergency workers. Get the right equipment or learn to do without. Don't cause mayhem trying to introduce a homebrew system that *might* work half the time.
A recent article over at arstechnica about an interesting piece of wireless mesh hardware: http://arstechnica.com/business/2012/08/how-one-man-is-bringing-voip-net-access-where-telecoms-fear-to-tread/
It works well, it won't give you much throughput but if all you need is some text and voice-based systems this should be plenty (it's about 300-9600 baud for IP so a slow serial link).
The issue I see with your approach is that when the vehicles are within range of each other they will also be within range of the same hotspot. So mesh is simply overkill. Mesh is intended for lots and lots of nodes in dense areas to connect to each other to a single (large?) uplink for either anonymizing or places where you cannot place (either due to economic or ecologic reasons) multiple antenna's. This works well for the GSM range because they are intended to cover literally miles (2W) at a frequency that is licensed to cooperate with each other and able to penetrate a lot of structures so two cell phones can technically talk to each other and extend the range of the original tower another mile or so (given the battery usage to do so is acceptable).
The 100 mW you get out of a WiFi router close to the hydrogen resonance frequency is simply not enough to cover a mile of random area which may have other compatible and incompatible broadband sources (microwaves, garage door openers, bluetooth ...) that could overpower the signal.
You're better off using the professional systems for this. WiMax base stations can be had for $1500 and a receiver is ~$200 and it will cover about 50km. Otherwise get a free cell phone plan for your volunteer fire department (I mean, some local corporate overlord MUST be benevolent enough) or set up your own transmitter (HAM or otherwise).
Custom electronics and digital signage for your business: www.evcircuits.com
Here's the article from less than 2 weeks ago about the same thing. They had a few interesting ideas.
While I applaud your willingness to use technology where you see a need for it, the consumer grade routers just aren't up to the task. I've seen routers die simply being moved from one side of the desk to the other. All it takes is a cold solder or a flaky chip and *poof* that router is history. You'll be troubleshooting weird problems constantly and will be replacing routers just as often. If your solution depends solely on these routers, then I think its not much of a solution at all.
Nobodies Prefect
Tidbits for Techs Technology Blog
What about using some level of 3G wireless access that can be low bandwidth attached to other hardware?
Yeah, this definitely feels like a case of "When the only tool you have is a hammer, every problem looks like a nail".
WiFi meshes like crap. Your first responders will spend valuable time just trying to get their devices to work. While your volunteer situation is well understood, and your budget is probably pretty low, don't ask people to depend on consumer stuff for this sort of thing. A trunk radio system (and one that is not too highly loaded) or something similar is highly recommended.
So you want to set up a VANET (Vehicular Ad-Hoc Network)...a subset of the MANET (mobile ad-hoc network). There's even a proposal for a secure fire truck communication protocol via VANET. Perhaps you can find more information by reaching out to some of the agencies working on this protocol.
"A person is smart. People are dumb, panicky dangerous animals and you know it." - K
Keven Whipp of the Montgomery [County Maryland] Amateur Radio Club gave a presentation last April on a very similar topic to the Columbia Area Linux User's Group (CALUG). The radio club has been working with Montgomery County to test various setups of MESH networks on Linksys WRT54GL routers running custom firmware to be used in emergency situations. They have been testing distances and reliability using different frequencies using high gain antennas (which require a license). As I recall the deployments they tested faced a lot of technical and regulatory obstacles. And they were looking at simple static deployments, not mobile. If, say the infrastructure went down after a flood, their objective was to provide basic internet services to Emergency Response Teams working in the area.
Anyway, here is a link to a PDF summary of the presentation. My take away was that even after pretty extensive testing the system was not ready for prime time, but was very promising. To be useful in the situations to which they aspired the Mesh had to be reliable and robust. It was not. I am sure they would be happy to share their experience with you. And I bet they made progress over the summer.
"No fear. No envy. No meanness." Liam Clancy
What exactly do you need this system for? Seriously, if you are needing internet access to save people, there is something wrong. Sure, there may be a situation where an Incident Commander may need to look up something like an MSDS on a hazardous material, but in that situation a tablet with 3G access is all you need.
If you're wanting this for comms, then you really need to think again. For Emergency Services, any comms system need to be robust (ie. not built on cheap consumer grade hardware), reliable (ie. able to work when parts of the system fail, and it must be easy to fix or replace) but most importantly it need to be able to work with the systems of other Emergency Services. If you go ahead and do your own thing, it could potentially cripple your response capability. If your Fire Department was first to attend a Mass Casualy Incident, would you be absolutely sure that your system, built on 'cheap wireless routers', would be 100% effective? Would you be prepared to stake your life, the lives of other firefighters, and the lives of multiple casualties on this system working? If the answer is not an absolute yes, then walk away now.
Don't get me wrong, it is a cool idea, but it is not something that you or your Volunteer Fire Department should be looking into as a deployed solution. You cannot go from "hey, this sounds cool" to putting it into operational situations without doing some serious research and development as well as thorough testing. This may seem over the top, but this is for an Emergency Service: people's lives will depend on this.
You are likely looking for an inexpensive service router ideally with a number of different ports, ideally supplied by 12 VDC (negative ground.) Ideally the service router will have a number of comm interfaces including two wire, antenna, USB, etc.. There are a number out products on the market. Your challenge is to validate the product, accept the risks, or adjust your specs/reqs.
UMTS service router wan
meshed 5 GHz wifi service router wan
meshed 2 GHz wifi service router wan
Tetra service router wan
APCO P25/P35 service router wan
MPT 1327 service router wan
MPT IP service router wan
Iridium service router wan
I've been doing wifi mesh networks for over ten years. As much as people try, these just aren't reliable or secure enough to be used for such things as military and emergency services networks. Emergency services have more radio spectrum than they know what to do with, and access to lots of other resources. Use technology which is appropriate to these advantages, taking into account the demand for very high reliability.
It's not standardized across the US, but many states have standards for emergency radios. Find out what's standard and go with it.
One of the more useful projects of Homeland Security is to get all the agencies that have first responders connected in emergencies. It's hard, because each agency has their own system and they don't interoperate. Here's the Texas plan. And the Florida plan.
Most of the hard problems have to do with too many people on the air in urban areas. If you're a volunteer department, you're probably not in an urban area and don't have that problem. If you want something that will Just Work, get high-powered 700MHz public safety band capable VHF FM handhelds and vehicle radios for your own people and get them fitted into your state plan. A few Iridium satellite radios for command personnel and those who really need to talk to the outside world during an incident are helpful. Here's one suitable for fire truck installation. Iridium airtime costs are high, about $1.29 per minute, but in an emergency that's the least of your problems.)
This would be pretty simple to do with a cisco router.
One SSID for the 'WAN', all devices in same subnet.
Each device also has an SSID to talk to your tablets etc, turn on DHCP on each individual router.
Advertise both subnets into OSPF. Central site can advertise out a default route.
Job done.
If you have a need for long-distance, broadband communications, you should build yourself either cantennas or cantennas+parabolic dishes. Even very primitive cantennas which are just cans with a hole inside work wonders to boost distance. Some guys on youtube made 70km links with parabolic antennas ! Make sure there is no line-of-sight obstruction, as this will strongly attenuate the signal. That in turn means you need long, portable masts. German THW has dedicated communications gear and units for that. SATCOM is also an option, as you will almost by definition have line of sight to a geo-stationary sat.
Of course, always ask yourself "what is the scenaio we will need it ?" "how would that communication technology be integrated into actual operations in a meaningful way ?"
If your connventional HF communications gear does the job, WLAN would be just a hindrance. I assume WLAN or SATCOM only makes sense in a major disaster such as a vast flood or whenever senior leaders and politicians need to perform confidential video conferences. Always remember, Rommel lead whole armies via hand-typed morse code and rather primitive HF radios.
Also, have you thought about text messaging via HF by some kind of automated acoustic signalling ? Makes a lot of sense because HF works quite well over serious distances and without line-of-sight. Text should be encrypted, of course; just use GnuPG.
The Serval Project on the Android Market.
Our focus is on providing useful services without any reliance on fixed infrastructure. Phone calls and text messaging via adhoc mesh, and even file distribution in the field.
Though you might find our next release more suitable than the version on the market. It's still in heavy development, but would also allow phone calls to be relayed to the PSTN via an asterisk PBX. We'd be happy to provide an alpha version and help you to get the most use out of it.
We're also working on a separate application that uses open street map data for situational awareness and collaborative mapping.
09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
I can see several applications that would make this type of network incredibly useful. Having the ability to distribute situational awareness video in real time would be awesome. This could be useful independently from internet connectivity and a tablet with a decent amount of storage could keep the video for later review. If it were within the budget, wouldn't a head's up display in the firefighters helmet of something built into the brim of a law enforcement officer's hat be pretty slick? The ability to Wifi locate any of your team could also be quite useful. Perhaps more to the point are disasters like Katrina or 9/11, where the telecommunications network may be down for extended periods of time. This kind of backup network could very well be the difference between life and death. If enough of these radios could be dropped in place with solar and battery backup as entire area could be brought back online in a very short period of time. Year's ago there was mention of a completely independent group of license exempt wireless pros forming an instant adhoc network on the the upcoming anniversary of September 11th to drive this exact point home. As a suggestion, you might want to look if the 4.9GHz band in available in your location. Among others, Motorola's Motomesh uses this band. It's clean, licensed for this use, and some Wifi adapters can be switched to work in that band, lowering the cost for equipment. Certainly, challenges exist and need to be worked through but if the opportunity to experiment is presented, why not go for it?
Our local club is playing with HSMM-MESH to supplement our existing ham radio set-ups (two repeaters and an "assigned" ARES/RACES-type simplex frequency (in the last regional drill, hams in the next county were demanding that we get off "their" frequency, which is why "assigned" is in quotes)). Some times it would be helpful in an emergency situation to be able to transfer files or stream video and Wifi speeds are better than TNC speeds.
A bunch of us have purchased a bunch of WRT54Gs and reprogrammed them, but we haven't yet tried to get them to mesh.
First of all, let's imagine the technical stuff isn't an issue. Imagine all the trucks have cellular modems and can just communicate over the Internet as usual. What are they using it for? I do volunteer EMS (not fire, admittedly, though I work with fire agencies a fair bit) but I can't figure out what it'd be used for, aside from CAD (computer-aided dispatch) which is outside the scope of our volunteer agency, and likely outside the scope of yours. Large-scale incidents (MCIs) do require a lot of information sharing that might be well-served by a data network of some sort, but interop is already a huge problem just with bog-standard FM radios. What sorts of computer data are they going to share without the internet? Keep in mind, this has to be data that's either already available digitally (in which case, why the network?) or created on-scene and then digitized. I can't think of any, honestly, except for perhaps pictures? And they're not really necessary.
So assuming there's a use for wireless data sharing, what justifies not dropping a few hundred a month (which is nothing for even a volunteer FD) on cellular broadband? It's a mature technology, reliability is high, and it doesn't require any customization - just logging into a VPN or something, if even.
Finally, your solution can't be finicky or unreliable at all. If it doesn't work once, it'll become a liability and nobody will rely on it. People don't screw around with stuff like this, since it can literally get people killed. Public safety has been doing fine on voice radios for a long time, and even if it could be done better, there's no hesitation about giving up your enhancements permanently the first time there's a problem with it.
I'm an amateur radio operator. I get the attraction to playing with this kind of stuff. But I'd never use it in my EMS agency, since "playing" isn't acceptable. That's why we buy $1k-a-pop Motorola radios that do less than my $100 Chinese HT - because there's no fidgeting, and no question about whether it's going to work when you need it. Even if you've dropped it in a puddle, or it's gotten dropped from 6 feet onto pavement, or used it to clobber a drug addict away from you (yes, it happens).
I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
If reliability is what you seek it's probably best not to rely on ad-hoc wifi networking but pay that $5/mo and get a mobile (cell) card to connect to a router ($50-100). It's incredibly cheap and we use to do it for any employees that carpooled.
Exactly. In such situations, an unreliable mwireless mesh has been used many times, proving it's worth. It was called ham. That experience shows that an ad hoc mesh is sometimes far better than no communication, or in addition to whatever other communication is available.
It's funny to me that MOST people consistently debate how well things MIGHT work without considering how similar things have worked. Ie, most public policy debates concern ideas already tried in California or elsewhere, yet everyone argues whether X would work, ignoring the fact that California already tried X and it failed miserably (or succeeded, as the case may be.)
There is an Android app developed by a mob of Australians which allows cell phones to talk directly to each other in emergency situations without using any cell service at all. Sorry I have no name either for the app or the developers. It was developed last year, released this year, and is intended for bushfire teams and search and rescue operators. I'm guessing it won't be in the app store and I know it works by dialling the number you want and if both phones have the app and are within range then they connect. I'm sorry I can't provide you with more information but it's just something I read about in the Sydney Morning Herald (www.smh.com.au) some months ago and it stuck in my mind because the main developer spoke at length about the incredible problems of getting the protocols to work.
I said - don't look Ethel!..., but it was too late..., she'd already looked.
Your thinking of putting 'emergency' services together using band aids, twine, and consumer crap products and expect it to work reliably enough so that you don't get sued for when it fails?
If you have a need for internet access, get a MiFi/wireless hotspot. If you only want internet access if one of the houses/businesses has a free/unsecured hot spot you can "jump on to" what is the point? Either you need it or you don't.
Do you rummage through people's medicine cabinets for bandaids/medicine or do you bring them with you? Do you look for garden hose when you respond to a fire or do you have a tanker with a pump and hoses you bring with you?
If there is an open, unsecured, wifi hotspot the mesh network can find in the neighborhood, why can't the netbooks, laptops, and tablets you bring with you find them?
Wasn't there a post not two-four weeks ago about an effort to make mesh networks areas without service? Did the original poster even see that posting?
Ken
Disclaimer: I work for a paid fire department but started as a volunteer. I understand the financial challenges for both m
Our metropolitan area uses InMotion OMG1000 or OMG1050 mobile routers. The cost just over $2000 each, but they create a man network for emergency equipment, have up to four different WAN connections, are remotely configurable and upgradable, and provide GPS services. They're almost bulletproof.
Wiring up WRT54Gs isn't the answer. You'll spend more time than your time is worth creating a solution than finding funding to implement one. Apply for a FIRE grant or cooperate with multiple agencies to access a larger program. Check with your county or state.
Realisitcally, an air card is all you need otherwise. If enough agencies want in on the project, see if the wireless provider will put you on your own APN.
Good luck.
I have to wonder why you need the local networking?
I know I didn't address the question of the best way to set up an EMS/Fire network, but that's what I got. Good luck.
They come in the dark, only in the darkest.
... of cheap MiFi 3G routers from sw-box or brando, or use cheap but reliable brands like TP-Link or Huawei. I don't know where you are but these can be had for as little as $15 in Indonesia. You don't need fancy firmware and in-depth features, just connectivity over a short range.
Just use this network for an informative "Oh that's nice" role - nothing mission critical, but everything mission 'helpful'. Don't use it for live comms; but using it for advanced notification (before they get there and ask) in order to negate the need for live comms should be okay. Don't use it for anything at the scene, conditions will most likely be WiFi-unfriendly anyway.
With 2 on vehicles and 1 on each person (dump the casing and put the contents in more convenient/robust containers on a belt or something), with select 3G capability on each vehicle, you should be able to make a sweet logistics net.
Oh, make sure the enclosures for all your toys are fully waterproof. Things could get embarassing otherwise.
Look, no SIG!
If it's available, just go with Nextel. Every phone can act as a dispatcher. Hey, if it works for ENG*, why not this?
* There are times when the news crews arrive first.
“He’s not deformed, he’s just drunk!”
seriously critical comms is not an area to reduce costs on - try a commercial wireless mesh - cobham as an example
Don't let your decisions become technology oriented, instead make your decisions more goal oriented. I don't know what you are trying to accomplish with the mesh network, but a simpler solution that a wifi mesh net is more likely to operate in bad conditions.
If in the US, there is dedicated and exclusive spectrum available for WLAN type communications, at 4.9GHz. Contact your regional spectrum coordinator through APCO. The equipment you select should operate in that spectrum as to avoid the exposure to unlicensed ISM bands (i.e. 2.4 and 5 GHz) where every dohickey operate their wireless routers.
Next, vehicle installation needs to be properly planned. Is there enough electrical capacity left to hook up additional gear? Where do you locate the antennas? If you happen to find a spot on the roof and it is fiberglass, you need to install a metal base plate. Also, you need to offset the antennas at least 1ft from other antennae as not to have your gear fried by high powered public safety comms gear already installed on board. There might be regulation re: the types of cable you are required to use to hook everything up, e.g. all plenum. Most importantly: Are you indemnified to perform any work on the vehicles? If something goes wrong down the road you might be on the hook for damages. And don't think you wouldn't get sued. If something goes wrong "they" sell everybody under the sun. How about maintenance in the long run? It's cool to hook stuff up and such, perhaps make it to the local newspaper, but somebody needs to maintain the whole sheebang.
So.... still interested?
Look at Motorola's Airmobile solutions.
They have a system for emergency communications in Italy, so that a wifi mesh network carries cellular in case of network failures, basically it works like the Serval project in Australia but is much more advanced. I recall it has a voip converter between gsm and wifi . With all the quakes they have it makes sense to have a backup.
Home networking equipment will probably not be suitable for installation on any emergency response vehicle due to local codes, standards and rules. Start with cabling, then check EMC, EMR, shock, vibration, temperature, etc.
Mobile broadband will realistically be used for sharing IP surveillance streams with a Operations and Control Centre.
Kit suppliers include Fortress Technologies, Firetide, Aruba / Alcatel Lucent, Moxa, and start at low thousand $.
I had a consulting friend ask me the same question about ten years ago. Of course the fire department in question realised they didn't really need it and moved on as a business case couldn't be made.
The dormant project has come to the top of my list ... building a fancy battery-powered 3G router is simple :o) Configuring it to do mesh networking isn't a priority right now, media serving is though :D
One of the UK Fire Brigades is currently using an Aerohive Wireless solution to allow the multiple Fire Tenders to be in communication with the Lead Fire Officer. As I understand the Firemen are also kept in Radio communication via Wifi, and the APs in each of the Fire Tenders can be used to triangulate the Firemen's position.
I would suggest you contact Aerohive via aerohive.com
I worked for a company that developed this technology in 2003. Mesh Networks. In 2004, Motorola bought the company.
http://www.motorola.com/Business/US-EN/Business+Product+and+Services/Wireless+Broadband+Networks/Mesh+Networks
The difference between WiFi and Cellular Radio (GSM) is that the latter allows handover of a moving vehicle from one transmitter to the next, whereas WiFi only allows you to walk from one access point to the next.
A patent application on this general type of application with very broad claims is being compiled. Might want to hurry up and develop this idea.
http://www.batswireless.com/
You guys who are trying to figure out what an EMT in the middle of administering CPR could use this for are thinking too immediate. Consider places like Christchurch in the days (and weeks) after the earthquake. The infrastructure is hosed: the cell system is broken or overloaded, power is out to most of the city (but there are generators), half the roads are impassable. The thing I keep hearing over and over from people who lived through that is that they needed comms. Even half-assed taped-together comms.
You are looking for 802.11S, a wireless ad-hoc mesh network. The standards committee has moved very slowly on this. The government doesn't really want it because once activated it would basically be out of their control. There is no central office where they can snoop on everyone. Terrorists bedamned, they want to control what content people are sending to other people. This is why 802.11s has occasionally been described as a 'backhaul network' or a 'dark net'. In rural areas, you could have an internet-like connection spanning dozens or even hundreds of miles, connecting thousands of people. Google 802.11s and see the current status for yourself.
I would think the focus of the people on the vehicle would be to save the patient, not find a way to have network access.
I think our society has become addicted to networking everything for the sake of doing it. I was at HH Gregg today and they had a freakin' toaster oven that could be controlled over the Internet.
Yes - and if you had a GPS then the mapping would be almost automated - say if you could use an open map such as openstreetmap then it would be a neat application of a mesh network + the data that the people on the ground are providing - to me this could be quicker than hand drawing maps.
I work at http://www.rajant.com/ so I may be a bit biased but our BreadCrumb line will work great for rugged meshing. We support 4.9 GHz radios that are reserved for emergency responders. We are in use by the military and large mining operations that require 24/7/365 networks with 100s of nodes and lives on the line.
-- soldack
I'd like to thank everybody for their comments, good and bad, polite and well...not so polite. Some of y'all "got" what I was asking for, some didn't, and some went WAY overboard in assuming what such a network would be used for. It was quite interesting to see how far off the beaten path some of the posts got. I gained some interesting leads and direction from the posts that I'll be looking into. Thanks to my brothers and sisters in the Fire Service and EMS and thanks to my fellow amateur radio operators. Thanks to everyone else as well. I'd love to meet you and have either a beer or a coffee, but I'd rather not hat to meet you professionally! Stay safe all...
This seems like a very interesting area, and one well worth investigating-- don't get discouraged by the negative commentators here. And I disagree strongly with those who say mesh can't be sufficiently reliable for the military; to the contrary, the military has been using mesh for years, and the barrier to wider option is the fact that military deployments tend to be proprietary and closed, not the fact that they are unreliable... to my mind, using mesh as a supplement to (not a substitute for) traditional public safety networks is a really interesting concept.
I'm not well equipped to provide specific hardware reqs (pun not intended), but do have some general recommendations re: leads to pursue in in this space:
As some folks have mentioned, might be worth connecting with the Serval Project. LifeNet down at GA Tech might also have some ideas, as might Funkfeuer in Austria (http://www.funkfeuer.at/index.php?id=42&L=1). Also, Robin Chase and others involved with the DoT's ITSPAC (http://www.its.dot.gov/itspac/index.htm) issued some reports involving VANETs that could be informative. Finally, Ushahidi (http://ushahidi.com/about-us) has done some really innovative post-disaster work, especially after Haiti, that might inform the development of your project.
Finally, I encourage you to reach out to local HAM radio operators, many of whom are quite interested in innovative solutions to communications during emergencies.