Tom, what if you could take the Cell/Sector system and add some routing that determined when a path had stopped and chose another one.
You have controlled this by your choice of units to make those cross connections and really all that is happening is that the mesh routing is constantly testing to see if it needs to try another route. We used to do this manually and what a pain it was. This new routing does what I used to do, except it does not sleep, have bathroom breaks or go out for lunch. You can assign weights to connections and force your chosen route to get used, at least until it goes down, which hopefully never happens, but if and when it does you are covered with your alternate path. What is so terrible about that? Lonnie On 2/24/06, Tom DeReggi <[EMAIL PROTECTED]> wrote: > Brad, > > I agree. Our downtown Mesh versus Cell/Sector trials proved exactly that. > Our tests showed that the cities like DC could be better served with > Cell/Sector models more effectively. > As a matter of fact, Alvarion product, appeared to be well equiped for that > task. > I think projects like Phili's will bring a rude awakening. I can't prove > that, but there is no reason for me to. > Thats the point of modelling. So you can pre-dict BEFORE you spend. > Its the Muni's budget to pay for, to find the true answer, not mine. > > Tom DeReggi > RapidDSL & Wireless, Inc > IntAirNet- Fixed Wireless Broadband > > > ----- Original Message ----- > From: "Brad Larson" <[EMAIL PROTECTED]> > To: "'WISPA General List'" <firstname.lastname@example.org> > Sent: Friday, February 24, 2006 2:49 PM > Subject: RE: [WISPA] Mesh Equipment > > > > Tom, IMHO mesh is great for lighting up downtown and city parks etc. but > > it > > has yet to prove itself in a large deployment with 1,000's of customers or > > 1,000's of nodes deployed. I too have first hand experience backhauling > > several mesh projects and the mesh edge so far has not been easy at all. > > Here in Northeast USA 15 mesh nodes per square miles doesn't even come > > close > > to what's needed. I've also found that implementing mesh in major metro > > areas, where there are already 1,000's of wifi access points, shrinks > > coverage models and can turn a well intentioned response to an RFP > > laughable. I believe Philadelphia projects 70k users in 5 years on 3900 > > mesh > > nodes backhauled by Canopy. We'll see. > > > > I'd love to see a comparison of our BreezeAccess VL with one mile centers > > and our high powered DS11 on the edge in Anytown USA vs mesh. I'm working > > on > > a few of my guys to do such a test so stay tuned. > > > > What it comes down to is the fact that Matt may have just the right > > terrain > > and noise floor without the traffic that some of these larger projects > > will > > get hammered with so it works for his company. Mesh is a tool for a > > certain > > job just like other gear. But I don't believe mesh should be construed as > > broadband for the masses in any major metro area. Brad > > > > > > > > > > -----Original Message----- > > From: Tom DeReggi [mailto:[EMAIL PROTECTED] > > Sent: Friday, February 24, 2006 2:28 PM > > To: WISPA General List > > Subject: Re: [WISPA] Mesh Equipment > > > > > > Matt, > > > > I think you are misinterpretting my comments. Don't read more in to them > > than are there. > > I am in no way attacking the validity of your experience or comments. I'm > > simply asking for more detail, so that I can learn from your experience. > > > > -- > > WISPA Wireless List: email@example.com > > > > Subscribe/Unsubscribe: > > http://lists.wispa.org/mailman/listinfo/wireless > > > > Archives: http://lists.wispa.org/pipermail/wireless/ > > -- > WISPA Wireless List: firstname.lastname@example.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > -- Lonnie Nunweiler Valemount Networks Corporation http://www.star-os.com/ -- WISPA Wireless List: email@example.com Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/