On top of that, if you are going to two different providers, but the links go over the same pipe anywhere in the route, you are still vulnerable. I know there are some towns where there is only one provider...that's where wireless can come in...unless you are REALLY remote.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom DeReggi Sent: Saturday, January 20, 2007 6:51 PM To: WISPA General List Subject: Re: [WISPA] Dual-WAN routers And Using two links to one provider does nothing for true redundancy, diversity, and failover.. Tom DeReggi RapidDSL & Wireless, Inc IntAirNet- Fixed Wireless Broadband ----- Original Message ----- From: "RickG" <[EMAIL PROTECTED]> To: "WISPA General List" <firstname.lastname@example.org> Sent: Friday, January 19, 2007 8:33 PM Subject: Re: [WISPA] Dual-WAN routers > Juat catching up on the list after a busy couple of weeks. So, are we > saying that all the products that claim load balancing dont work? I > can testify that the auto-failover works but the load sharing seems to > make things slower not faster. Keep in mind I have not tested > everything. > > -RickG > > On 1/8/07, Jeff Broadwick <[EMAIL PROTECTED]> wrote: >> Great points Butch! >> >> There are products out there that claim "load balancing" and "failover", >> but >> there is only one way to do both, and that is through bonding. Bonding >> requires that the circuits be terminated in one router on your end and >> one >> router on the provider end. >> >> The only true failover with multiple providers is BGP, although there are >> companies claiming otherwise on that also. BGP does nothing for load >> balancing. >> >> Jeff >> >> >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >> Behalf Of Butch Evans >> Sent: Sunday, January 07, 2007 1:49 AM >> To: WISPA General List >> Subject: Re: [WISPA] Dual-WAN routers >> >> On Sat, 6 Jan 2007, David E. Smith wrote: >> >> >> This is for the end user cpe side. I'd like to see both fail-over and >> >> load balancing but fail-over is priority. No need for wireless. I'll >> >> look into the microtik. Thanks! -RickG >> >> Rick, keeping in mind that "load balancing" where you don't control both >> ends of both links is not truly possible, there is a way to SORT OF get >> this >> effect. The problem is that some things have to be treated in a special >> way >> when you are using NAT (actually, masquerade, but we won't go there). >> VoIP, >> P2P, VPN and a few others come to mind. Either way, there are some >> things >> you can do to make this work with MT, and it's not that hard, but it IS a >> bit time consuming to get it right. >> >> As for failover, there are several ways to do this, and some of them are >> pretty simple. A bit of scripting knowledge is required, but other than >> that, it is not that bad to do. There are some examples in the manual >> (as >> David pointed out) >> >> >Mikrotik RouterOS manual. In a pinch, I know we've got one or two >> >Mikrotik trainers on the list; you could get them to show you how to do >> >it. You only have to pay for it once, then you can just copy-and-paste >> >the configuration from there on out. :D >> >> Well, copy/paste for policy routing is not really that cut and dried. It >> is >> best to understand what the policy states, then moving it to a new system >> is >> not that hard. As I said, it is somewhat time consuming to get it >> working, >> however. >> >> >Fair warning, I haven't used the RouterBoard 150 hardware I mentioned, >> >but most of their other hardware has treated me well, so I wouldn't >> >expect that board to be any different. >> >> I like the 150...it is a very inexpensive solution for a low end router >> (just $70 plus a case and powersupply). The 153 is only $120 and you can >> add radio cards. >> >> -- >> Butch Evans >> Network Engineering and Security Consulting >> 573-276-2879 >> http://www.butchevans.com/ >> My calendar: http://tinyurl.com/y24ad6 >> Training Partners: http://tinyurl.com/smfkf Mikrotik Certified Consultant >> http://www.mikrotik.com/consultants.html >> -- >> 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/ >> > -- > 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/ -- WISPA Wireless List: email@example.com Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/