At 6/18/2010 05:52 PM, you wrote: >Hi Fred, >In my opinion there is bit of an oxymoron in your original question / >thought...... > >On-one hand you are looking for a "Mesh" product, which implies a self >configuring / self healing product... but you are also pointing out that >this is not going to work as a whole and you will have to "Engineer" the >links because of the Terrain etc... > >Typically most folks think of a deployment as one (Mesh... turn on, let >it self connect / self configure etc) or the other .. Engineered Link & >Engineered Routing Protocol.... > >Are you sure this is what you are needing ? You can very easily do a >hybrid approach.. where you have an "Engineered Back Bone" Links (these >could be fully meshed, using OSPF or OSLR..etc) and you can do local >distribution using a Mesh protocol if it want to make it easy for the >EndUsers connection.... With this you can mix and match protocol >/equipment / radios etc.....
It's a question of semantics. I use "mesh" to refer to the topology, and to having more radios than injection points. Yes, it needs to be self-healing, and to some extent may be self-configuring, but that's software. The radio links are all engineered; it's too difficult a location to do otherwise. -- Fred Goldstein k1io fgoldstein "at" ionary.com ionary Consulting http://www.ionary.com/ +1 617 795 2701 -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
