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..... Faisal Imtiaz Snappy Internet& Telecom 7266 SW 48 Street Miami, Fl 33155 Tel: 305 663 5518 x 232 Helpdesk: 305 663 5518 option 2 Email: [email protected] On 6/18/2010 5:20 PM, Fred Goldstein wrote: > At 6/18/2010 04:47 PM, L. Aaron Kaplan wrote: > > >> On Jun 18, 2010, at 4:33 PM, Dennis Burgess wrote: >> (I wrote:) >> >>> MicroTik says they have a meshing protocol, HWMPplus, that provides >>> Layer 2 (this is critical; we're not building a Layer 3 network, and >>> with this many hops, latency and loss are critical) dynamic meshing, >>> essentially applying a routing protocol (smarter than bridge STPs) among >>> nodes. I can't find any documentation for it on line, though, and a >>> distributor I've been talking to has never tried or sold it. So does >>> anyone on the list have any experience with the HWMPplus mesh? Or any >>> other suggestions? Thanks! >>> >> >> IMHO it does not scale... is not documented and built on an outdated >> rip-off copy of another protocol which already developed further >> and fixed some major scalability issues. >> > MT says that it's an incompatible extension of an early draft of > HWMP. I don't know where HWMP is now or why they forked it. But > we're looking for an off-the-shelf short term solution, while we, uh, > work on the long-term answer. The nice thing about Routerboards is > that you can run other Linux code on them... > > >> But please, do not get discouraged and in case HWMPplus does indeed >> work with more >> than 100 nodes, let me know and I would be very interested in how >> you managed to do that. >> >> Of course, your mileage or your needs might differ. >> > The site I have in mind would need fewer than 50 nodes. So how many > hops and how many nodes would be reasonable limits for HWMPplus? > > > > -- > 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/ > > -------------------------------------------------------------------------------- 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/
