Ask Slashdot: Best Connect Scheme For a 2-ISP Household?
c_petras writes "I just had DSL installed (a 19,000 ft run — Woo Hoo!) to act as a backup to my regional WiFi connection. How should I configure my home network so I don't have to swap the cable from one ISP's router to the other to maintain a good connection? Is it as simple as getting another router and plugging the two ISPs in? Is there a more elegant solution that would not require the use of three separate boxes and associated wall warts?"
This is the job of a good router/firewall, but without knowing what you're running there's no way to answer the question.
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
I did this a couple of years ago with DSL and cable. My choice was to use OpenBSD's Equal-Cost Multipath Routing. I've seen other hardware devices that accept two broadband connections but the OpenBSD option was much more elegant and allowed some good granularity in traffic control (ie.: traffic to my cable ISP's billing page may as well go through the cable connection)
I had a couple of lines in pf.conf as so:
then would force the network ranges/IPs contained through the appropriate interface.
I dumped the DSL about a year ago but this worked very well for me. YMMV. Mail me if you'd like more info/tips.
Trolling is a art,
It's the Slashdot-approved solution.
1. Setup a pfSense router/firewall
2. Configure Failover
3. ??
4. PROFIT!
http://www.juniper.net/us/en/products-services/security/ssg-series/ssg5/
Spend a few hundred bucks and get a multi-WAN router that will combine the connections. Peplink is good apparently: http://ma.tt/2011/03/peplink-review/
PFsense (www.pfsense.org) is a great open source multi-wan router. I currently run 3 separate incoming connections to my network with it flawlessly. Combine this with great VPN,load balancing, round robin connection, traffic shaping, and bandwidth monitoring and it is a fantastic easy to use tool.
sure, it's as easy as learning BGP routing..huh huh... Or there might be a router out there with two WAN ports, that you can give metrics to say which is the perferred network. But the only ones i know of are Cradlepoint routers for 4g/wired networks.
Pfsense is a great solution
You can set up an old computer as a home server doing the balancing of the two connections, and you can even add some more functions to it (file server, vpn, etc).
A good distro for it is Zentyal, which is based on ubuntu and will let you config the whole thing over a web browser, just like one of those d-link routers.
My recommendation: pfSense.
Or ClearOS.
pfSense is FreeBSD based. ClearOS is linux-based.
If your router supports dd-wrt, it has this option built in. You may need more than one router for this. I've never tried it, but there's info about it here: http://www.dd-wrt.com/wiki/index.php/Mesh_Networking_with_OLSR
There are companies that make routers with 2 WAN links. Health checks are run periodically (pinging a public DNS server or some other reliable IP through the link), and traffic is routed across your preferred link if it is up, or the backup if the preferred link is down. The one I'm familiar with is made by FortiNet and costs $500+ http://www.fortinet.com/products/fortiwifi/50B.html
Sounds like a job for untangle firewall and router
www.untangle.com
To do fail over or balance your Internet usage over two ISP links you would need a load balancer. ELFIQ is one such balancer that is reasonable priced. To get a Firewall appliance that can do the same you are looking at a much higher cost.
You may be able to set up the same sort of thing using a Linux box, but once you factor in the time to set things up you're better off with a load balancer appliance.
What you might consider is a dual-wan router. It can replace your regular router and provide more connectivity options.
Unfortunately, for the low-end ones that I looked at, the options were limited:
1) fail-over mode. Normally use WAN-A until it dies, then use WAN-B.
2) dual-WAN mode. Client 1 goes to WAN-A, client 2 goes to WAN-B, client 3 goes to WAN-A, etc.
What you probably really want is a truly load-balanced mode, which requires either going higher-end, or rolling something yourself with a PC.
There are some hacks for dd-wrt and such to make a router dual-WAN, but that looked to be more bother than I wanted to go in for.
Ultimately, for me, I made one WAN connection pretty solid such that I didn't have to bother with all this.
The "Cisco" RV042 (http://www.newegg.com/Product/Product.aspx?Item=N82E16833124160&Tpk=RV042) supports this, by having two WAN Ethernet ports. Plug them both in and go. Relatively inexpensive at $180, sometimes you can find deals online for them. I say "Cisco" because I think the hardware is just rebranded "Linksys" gear from before the merger.
Now it's Slashdot - news for noobs, and even more noobish questions.
Setup a three+ NIC box and install ZeroShell. It supports Multi-WAN uplinks with QoS, failover, and load balancing.
Buy a Draytek dual-WAN router. In Canada they are available via here : go-draytek.ca.
They ship to the US.
2 NATs in one rig. Typically this means 1 $5 PCI Etherent card. You really should be more descriptive of your needs, otherwise you're going to get vague useless information.
It is an older router, should be cheap on ebay. I've been using one for 8 years now with very few problems.
I do this for clients frequently, generally cable/fios or cable/dsl depending on what's available. Sonicwalls do a great job as far as load balancing/failover and ease of setup (initial setup wizard allows you to configure dual wan ports). On the pricey side but they work.
When I google 'multi wan router' (I assume you didn't get that far), Peplink is the first result. They seem pretty legit, but I don't have any of their products. They even have one that can connect to wifi networks and ethernet for internet connectivity, which seems right up your alley.
As far as I know, just linking to routers together will not work. Your computer can only have 1 gateway (where it looks for the real internet). Maybe there's custom firmware that allows load-balancing with another router, but I doubt it.
Help I'm a rock.
Comment removed based on user account deletion
This will do the trick...
http://shorewall.net/MultiISP.html
I used a Netgear Dual-WAN for years. It allows you to specify (via the web-interface) which traffic goes over which network.
http://www.google.com/profiles/malachid
Some inexpensive small office firewall appliances support multiple external network connections, and can automatically move traffic to the secondary connection if the primary goes bye-bye. I believe one such device was a Multi-Tech SOHO firewall. There are like a lot of them out there.
I use irony whenever I can, but my shirts are still wrinkled...
If you can spare/build/whatever a machcine (and really it could probably be anything from the last decade), download pfsense, the installer pretty much works, the how-to's are very detailed. It's a mature stable product. It'll let you load balance your outbound connections as well as do everything a modern firewall does (you might, for instance, find being able to setup VPN on the box highly useful).
If you don't know anything about networking it might be a bit daunting, but probably still within the realm of possibility given it's all gui based and the docs are detailed.
While there are products that do this (dual WAN firewalls, etc) none of them are particularly great. If it were me, I'd repurpose an old PC, or a dedicated board such as a Soekris 4501 (http://soekris.com/net4501.html) and roll your own. It should be pretty simple to do it with iptables and a few bash scripts. Off the top of my head, I'd do something like ping a device a few hops upstream on each providers network every 60 seconds or so, if the device isn't responding, then failover and use another script to failback when the device is reachable again.
Using linux would allow.you to incorporate traffic monitoring, QoS, etc and even a file/web/dns server if you want to. In short, the linux route keeps you from getting locked in to a proprietary system that may not meet all your needs. There's load of documentation on doing stuff like this available online, so you don't even really need any prior linux experience as long as you have a will to learn.
I am doing this myself right now using a SYSWAN Duolinks SW24 router. (The other solution I looked at (but was unfortunately out of my price range) was the Peplink Balance.) It works well, with two potential gotchas.
First, it doesn't provide link-bonding (or whatever the appropriate term is). That is, it cannot *combine* the bandwidth of the two links, but if you start downloading one file, then start a second download, (most of the time) the first download will use one connection and the second will use the other. I have two equal-bandwidth/equal-ping connections so it doesn't matter which is used. It won't download *one* file twice as fast. (It could possibly bond the two links together if you used a fancy bonding VPN endpoint somewhere, but I doubt that is what you're looking to do.)
The second gotcha has to do with dynamic DNS providers. I can control the inbound port mapping of only one of my Internet connections (WAN 1). I have port 80 (for example) on my DSL pointed at my home server. I'm using dyndns.com to keep a hostname mapped to my ever changing IP address. The Duolinks will update dyndns whenever any connection change occurs, instead of only when the IP changes on WAN 1. When it changed my dynamic hostname to my second (un-portmapped) internet connection, I couldn't get to my home machine via the hostname anymore when at the office.
Works well, pretty rock solid.
Check out Vyatta.. they have an appliance or it can be run on a computer/VM. They have a commercial version and a community version.
Buy a little router from Mikrotik. Fat Swiss army knife of packet slicing and dicing, easy to use.
It seems like what you are looking for is HSRP. You have routing set up to where if the primary service goes down, the route dies and fails over to a secondary connection. I used to set this up all the time at the NSP I worked for and it was very simple. VRRP is even easier but it is Cisco proprietary and probably wouldn't fit your needs.
Use what the grown-ups use.
Go buy yourself a Juniper SSG 20 with the optional xDSL module, and let the firewall take care of the failover for you.
~dlb
Untangle (http://www.untangle.com) may be a good option. It is relatively inexpensive and has WAN failover and load balancing capabilities with an easy to use UI if you don't want to go the 'roll your own' route.
A Mikrotik RB750 can be configured to do this with no problem. $40
Since you are asking on slashdot, I am going to assume that you are geeky, but not a network person.
If you were a network person, as I am, then building a little box to route would be easy. That is what I would do. If you have more time than money, then I heartily recommend that option. There is plenty of software that will work.
Assuming that you are not a BSD/linux routing jockey, then you should look at a SonicWall or similar firewall. There are TZ100s used on eBay for less than $150. The configuration is through a simple web interface and has wizards. There are other brands, and SonicWall is quite mediocre, but I have the most familiarity with them.
Basically, you need a router with 2 WAN ports and the ability to configure failover. I don't have a good recommendation, because it's a feature that generally isn't available in consumer-grade gear. Expect to spend a couple hundred dollars.
And that's just for failover. Load balancing is more complicated and often doesn't work out as well as people hope.
VRRP was created for exactly this.
But clearly you have something better to say...
Pardon my ignorance, but you have WiFi (as in IEEE 802.11XX?, a.k.a. WLAN?) available, but for DSL you needed 6 km of cable?
WHERE on this planet do you live?? (or am I prejudiced when assuming you are on this planet?)
http://www.dualwanguide.com/ddwrt_dual_wan.html
I found myself in this same position a number of years ago, I've settled on using ubuntu linux, iproute2, and iptables, it's not easy to get working right, especially when you have DSL instead of a nice normal IP based connection (I will forever hate PPPoE)
The mental gymnastics of tracking ip connections across two separate routing tables in the same box will give you a few headaches, especially when a packet which comes in through the DSL heads back out the WiFi interface for no apparent reason... it's definitely not easy to get working. PPPoE imposed by our new DSL vendor added a new level of hell once we moved.
If you can find a piece of hardware which works well for less than a weeks worth of your time and effort, that has good reviews, and supports PPPoE, buy it, and don't look back.
By why is this an 'Ask Slashdot'. This seems like a very straight-forward question that doesn't require opinion to answer. I am not even sure if there are multiple answers. This is one that truly can be answered with a simple Google search. Am I missing something?
See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
Try a draytek vigor
I use a Soekris Net 5501 running pfSense to do this. The thing is bulletproof.
You can configure pfSense to use both WAN connections in a round robin arrangement. Alternatively you can set up a failover configuration where pfSense uses only the faster, higher-bandwidth connection; if that connection fails, traffic is diverted to the "backup" ISP.
Comment removed based on user account deletion
Buy this. http://www.balticnetworks.com/mikrotik-routerboard-750.html?___store=default
Game, Set, Match.
Netgear FVX538 and Netgear SRX5308.
Multiple WAN ports with load balancing and auto-failover.
I have a Linksys (now called Cisco) RV042 that has a dual WAN option and even offers load balancing with the newest firmware. Great product! I believe you can even install dd-wrt on it and make it do more than it was intended for. ;)
Dual WAN Load Balancer from SYSWAN. This thing is great. Tech support out of Oregon. $175 at newegg.
You might want to look into load-balanced routing. I had a linux box with 3 NIC's, one NIC per ISP and one NIC to the rest of the house. I set it up for load-shared routing via the LARTC HOWTO, and for web traffic it worked ok.
I didn't stay with it because it wasn't stable for VPN connections. The decision about which upstream link to use was somehow governed by the local/remote host pairing, plus some unknown-to-me modifier. So I could establish a VPN connection, but it wouldn't keep the connection through 1 of the two links consistently. As soon as it tried to switch the VPN connection to route through the other uplink, pow, there went my VPN session. I don't recall the exact time before failure but it was less than 2 hours in most cases. made it basically unusable for me, at that time, for working from home. Perhaps that's solved(or can be configured around) by now.
I don't know/remember how it works for p2p either, though, since it was so long ago and the decision about which upstream path for any outbound traffic to take is controlled by the kernel on that routing box.
here's the relevant section of the LARTC HOWTO, in case you want to read more or try it out:
http://lartc.org/howto/lartc.rpdb.multiple-links.html#AEN298
I see people trying this all the time, and there's one unavoidable bump in that road: connecting from two totally different public IP's in two totally different IP blocks that are native to two totally different DNS domains. DNS can be worked around to some extent by going to a common DNS server that's outside, and visible from, both domains, like Google or OpenDNS, but that runs into issues resolving in-network hostnames because a lot of ISP's provide different IP's for in-network vs out-of-network services, which can impact email and some streaming services to third party set-top devices pretty heavily. And the in-network services you're connecting to may not know how to handle you if you connect to an externally resolved IP from an in-network address block.
It's *possible* you could hack a home server/router combo to provide split DNS that will resolve properly to in-network services on both connections properly, but that configuration (and routing appropriately to separate WAN's on separate networks) is *very* non-trivial and will be squirrelly as hell if it's not tuned just right, and possibly just squirrelly as hell, period.
Honestly, I'd set up your local router/WAP for a network that's separate from your neighborhood wifi's SSID and just switch networks as needed..
At home, I have both cable and DSL. I use a Vigor2930N from DrayTek.
Works like a charm.
There have been other mentions of a Cisco/Linksys product (the 104, I believe) but I went with the Draytek because I wanted integrated wireless, too.
Aren't you just the very model of a courteous, considerate and empathetic piece of human excrement?
I did a blog post on this very topic last year.
http://johnsokol.blogspot.com/2010/11/increasing-internet-reliablity-dual-wan.html
Use a cable modem and DSL at the same time.
Xincom XC-DPG502
TP-Link TL-R480T+
I am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso
http://store.netgate.com/Netgate-m1n1wall-2D2-Black-P220C83.aspx
I had the Cisco/Linksys and experienced endless frustration. I wound up replacing it with a Draytek Vigor 2930N. The 2930 works great and provides integrated wireless, to boot. Love it.
More info.
Out of curiosity why does anyone need ISP redundancy in a home setting? I'm guessing everyone that needs this is a remote tech contractor/employee of some sort, but I am curious if there are other reasons.
Here is something that may help you. Note that this will get you the public IPs directly to the WAN interfaces and requires bridged mode on the CPE: http://blog.angulosolido.pt/2008/03/intelligent-linux-gateway-multihoming_04.html There is also a (warning) very bad video about it: http://blog.angulosolido.pt/2008/03/intelligent-linux-gateway-bad-video.html
Comment removed based on user account deletion
We used to use shorewall traffic shaping at $company. http://www.shorewall.net/simple_traffic_shaping.html
If you can manage Linux, it's doable. Otherwise, I would try and get a higher-end dual wan router or such. I guess it depends on your budget, motivation and time.
Those Linux-based routers do very well. I have an Asus RT-N16 and this should be able to route both WiFi and up to 5 Ethernet links (each port is separately addressable). There are also specific dual-wan routers but the hardware and software is identical, the configuration changes. There is an example on the DD-WRT wiki on how to set up iptables so any Linux distro would work just as well. If you run out of resources on those ARM devices (Linksys hardware is particularly underpowered for anything beyond 10Mbps) you can get a cheap VIA system with a couple of decent PCI wireless and wired cards.
Custom electronics and digital signage for your business: www.evcircuits.com
http://routerboard.com/RB750
Small, cheap, highly configurable.
It has 5 ports that you can configure as wans or link them together as lans. There is also a gigabit version available.
You can do everything on this as you would on a homebrewed freebsd solution, but with a nice gui or an optimized cli.
I did a website for a client who sells and configure devices like this for schools and libraries under the federal e-rate program. I don't have personal experience with the device, but he says it works quite well. Here's a link (disclaimer: like I mentioned, I developed the web site for this, but I'm not affiliated with the product) http://e-rateforschools.com/services/e-rate-internet-availability-link-balancers/
-Clay
Drinking habits can be dangerous. You can choke on the cloth and the nuns will wonder where their clothes are.
If what you're looking for is A) Fail-over, so if one ISP or line is down you use the other or B) The ability to reach selected IP addresses via one ISP or the other, a dual WAN setup will work for you using one of the dual WAN setups people have mentioned. They're basically hacks that masquerade your desktop behind a public IP address from whichever provider you happen to be using at any moment. They don't allow asymmetric traffic (can't send packets out one ISP and receive via the other ISP) and they'll possibly screw up any security protocol or site that expects to see packets coming from a single IP and port address. This is handy, but only slightly more convenient than moving the cable yourself and re-issuing a DHCP request. Forget about aggregating bandwidth, you won't get that.
If you're thinking that hooking up both ISPs to a router will let you use whichever one is faster for any site when you click on it, you can't do that without a ton of work (and for the most part without being an ISP). The problem is that although a routing protocol exists on the global internet that would let your router figure out which path is best to each network prefix, to use it you have to have your own routing block (an aggregate of multiple network addresses) to announce to the world (which you can't get) and you have to have a router capable of holding and processing the global BGP table in real time... you don't have this.
If only all our home routers could speak a multi path routing protocol with low overhead, every single packet we sent would take the best path to its destination, all our computers would automatically fail over to other connections, we could add bandwidth by plugging in another wire, we could add and remove bandwidth in real time as needed, and we could migrate between internet providers without re-numbering our IP addresses. Things like mobile apps would be much easier to write.. no need to use a central server to pass data to a mobile, just send the packets to its IP and the routing protocol would send them on to wherever it's connected in the net.
I look forward to the day when the Internets evolve to permit multiple pathing for data in real time. Too bad technological development of Internet protocols seems to have slowed and become heavily political.
Erik
I have Comcast, which is expensive at over $60 / month, but I get 10-20M downstream (10M nominal).
AT&T is offering DSL for less than $20, but I'm 13,000 feet from the modem (by wire. By car it's only 1300 feet) Last year their website said they provide service in my area, but when the technician came out and measured it, he said the signal was too weak. This year I checked again, and their website has been updated to show what kind of service they offer to my address, and it said 700K nominal. No way was I going to downgrade to less than 10% of my current throughput.
I guess if you only have wireless internet, DSL could be an alternative. But DSL at 19,000 feet? It must be like 256K. That's slower than dialup, isn't it?
On the other hand, with wireless and DSL, maybe you could configure your router to send some packets to one ISP and some to the other, like a reverse loaed balancer.
Comment removed based on user account deletion
I run several of these. They are both VM machines and loaded from a cd with persistant storage.
http://www.zeroshell.net/eng/
Look at the net balancer option, you can split traffic using any iptables rules and it has an excellect web ui. Full shell to linux if you want to get dirty too.
Maybe follow a guide like this?
http://parkersamp.com/2010/03/howto-using-linux-as-a-simple-load-balancer-nat-router-firewall/
Comment removed based on user account deletion
If it is in your price range, you could look at the Juniper SSG5. Runs about $500. It supports eBGP, OSPF, RIP, ECMP, VPN tunnels, etc... You can have as many WAN connection as ports on the router. I use them pretty much everywhere for my small business clients - you cannot beat them for the flexibility and feature set at that price.
http://www.juniper.net/us/en/products-services/security/ssg-series/ssg5/#literature
No I'm the real thing, not a model.
I've been using a Syswan Octolinks for years with no problems, because at one point I had 3 connections to manage.
I also have a Barracuda Link Balancer that I'm rather underwhelmed with. The DHCP server on the unit seems to crash every few months, and Barracuda support was no help, so the solution was simply to use something else to provide DHCP services.
Some suggestions for you:
Watchguard firewalls are all multi-wan capable and are nice units.
If cash is an issue and you have an old box lying around, run PFSense
I once saw a presentation about the products from Mushroom Networks. As I recall, they basically are running a small Linux box and are aggregating bandwidth at the link level of the OSI model. Based on the product, you can plug in multiple (5 to 6) Ethernet connections or even USB connections to wireless cellular data cards. This is probably more of a small to mid-sized office product.
I'm not sure on the pricing. Here's a blurb from their site on one of their products:
"The Porcini BBNA (Broadband Bonding Network Appliance), is a one-sided Internet bonding appliance that provides aggregated Internet connectivity to home offices who wish to aggregate multiple Internet access lines for increased performance and reliability in a cost-effective way. With the Porcini BBNA, multiple DSL, cable modem or T1 services can be combined to provide higher speed and more reliable Internet access.
"The Porcini BBNA combines multiple Internet access lines, each on a 10/100baseT Ethernet interface, into a single aggregated Internet access line for HTTP downlink traffic, again on a 10/100baseT Ethernet interface. The aggregation over the Internet access lines is done even for a single download session, providing the full aggregate speed. Additionally, session based intelligent load-balancing is provided for both non-http downlink and uplink traffic as well as inbound load-balancing. The Porcini BBNA4422 supports aggregation of up to 4 Internet access lines plus one USB based cellular data card as the 5th WAN. Each Internet access line may be through a DSL modem, cable modem, T1, satellite modem, fractional DS3, DS3, fiber, cellular or any other broadband connection. For uplink bonding capabilities, please see our TRUFFLE product line."
There are routers that specifically support multiple WAN connections for redundancy or load sharing. They take care of the job of modifying routing tables so that bad things don't happen. The biggest users of this stuff are businesses, so expect higher prices (and, hopefully, better quality).
http://www.peplink.com/balance/
I've had good results with peplink's WiFi gateways, but have tried the multi-WAN stuff myself.
-Dan
I was looking up how to do a backup/failover link via Cisco ASAs yesterday after a friend mentioned getting a second link. Hardware is pricier than your normal at home router, but it's a thought.
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtml
It's probably cost prohibitive for some SOHO setup, but I think some of the mid-tier firewall and link balancer products will support sticky connections and/or policy routing specific IPs and URLs.
I've installed a half-dozen or so Ecessa PowerLinks and have not had any problems with users being unable to get to or work with specific sites, even though it works as you generally suggest (although they use a dummy LAN between the PowerLink and your internal firewall).
The same is true for Watchguard Firebox firewalls with the Fireware Pro software level and multi-wan.
IMHO, the bigger issue is failover that doesn't leave something to be desired. Most products I've worked with tend to want to use ping or, slightly better, TCP connects to static IPs on a per-interface basis to test to see if there's a network there. It's all well and good, but false positives/negatives are tough to avoid.
A big chunk of the problem is that you want to test something on the internet and not served, co-hosted or part of your ISPs network -- you want to make sure you can get past the ISP.
Ping is nearly useless across the public internet as a rule, unless you have a host you can ping and expect a packet back. TCP connect is a lot smarter, but the whole static IP thing is a huge problem unless you frequently check and validate IPs regularly or are using known statics. It'd be far more helpful to use DNS names that were cached and refreshed periodically, but I haven't seen any devices designed for this.
Check out this product called OASIS.
http://onlight.com/oasis.php
It is described as follows:
"Our engineers have perfected a line of devices that intelligently manage two or more Internet connections to keep businesses connected. We call these devices OASIS."
Sweet
I am in a similar situation except I am using the Cable Company Internet connection to connect my server(s) to the Internet while the Wireless Company Internet connection is intended for my desktop/notebook computer. I have the Wireless Company connection via an Ethernet cable and the Cable Company connection via WiFi to another router; these connections are to my desktop/notebook computer. When I need to switch between the two networks I use Network Manager / Network Configuration utility in PCLinuxOS and it works smoothly to the point that I can rejoin a previous ssh connection, for example, to the servers after having been connected to the other router. My cable ISP is unlimited data whereas my wireless carrier ISP is tiered pricing with a 3GB minimum and 10GB maximum before overages kick in to the billing.
I setup a dual homed network system in about 5 minutes with arno iptables in ubuntu. Super simple and very reliable and easy to setup.
--- It is not the things we do which we regret the most, but the things which we don't do.
I'm pretty sure you can do this with a Cisco ASA - although they're meant more for offices, they should work in the home just as well. The ASA 5505 is reasonably priced.
Sustworks IPNRX (IP Network Router X) will also do this on a Mac, even over multiple USB NICs on a Mini: http://www.sustworks.com/site/prod_ipnrx_help/html/AlternateRouteHelp.html
Luke, help me take this mask off
Buy a router and put DDWRT on it (lots of advantages, certain routers well supported) then use one of the LAN ports as your WAN port
http://www.dd-wrt.com/wiki/index.php/Dual_WAN
http://webcache.googleusercontent.com/search?q=cache:gIv7HeSGSCcJ:www.sbhacker.net/forum/index.php/topic/5903-dual-wan-guide-for-dd-wrt-routers/+tomato+dual+lan&cd=7&hl=en&ct=clnk&client=firefox-a&source=www.google.com
These posts express my own personal views, not those of my employer
Try a suitable router loaded with DD-WRT.
http://www.roadrunnerguide.com/dualwan.html
Many decent motherboards these days have dual network chips. But you can take any old computer and shove three network cards into it. I presume your favourite operating system can share it's internet access.
So that's what I'd do -- in part because I'm not a networking kind of guy, and in part because I know it'll work. One computer, in the basement, with both ISPs going into the computer, running windows -- vista or 7. One network cable out of that computer to my home router. That's it.
It's also really easy to debug. That computer either has internet access or it doesn't; and you've got all of windows to help you ensure that it always does. Everything else can just feed off of it.
And if you're anything like me, you undoubtedly have an old computer lying around, and at least five old network cards. So you can prototype it in an hour. Then just get some good quality network cards.
We use a Sonicwall TZ-170 (no doubt replaced by something else now). It offered three network ports -- internal LAN, WAN and 'OPT'. WAN and OPT are assigned to our two ISPs -- a local WiFi vendor (fast but unreliable) and satellite (slow but very reliable). We have played around with a couple of failover and load balancing strategies and they all have their flaws. The least disfunctional for us has been to route traffic through the faster port with failover to the surviving service. We tried rounrobin, balancing traffic between them, etc -- all the possibilities available had their own quirks. And some services have to go through specific paths, so those connections will just be blocked when the link is AWOL. Failover is established by probing resources on the vendor network every couple of minutes -- because these are unreliable, the Sonicwall considers it a success if any of the probes succeed (there are a number of choices). With the WiFi, the remote end of the wireless link is always there but the ISPs DNS servers are up and down. It is a different combination for the satellite -- one just has to experiment to see what works. It is never seamless, but waiting a few minutes while the system reconfigures itself is a lot better than swapping cables. And besides, there will be those days when both of them are down.
I recently a dual wan router (Cisco RV042 Dual WAN VPN Router) to connect two DSL lines and it works great. I purchased mine at Microcenter.
I use a three interface linux box with Shorewall http://www.shorewall.net/MultiISP.html
as the firewall software. Shorewall allows you to do Multi-ISP routing but does not do dynamic routing so you have to restart the software to change the routing. Dynamic routing based on link quality of very hard to do properly.
CM www.cometenergysystems.com Blog: http://caribbeanrenewable.blogspot.com/
http://lmgtfy.com/?q=how+do+I+make+links+on+slashdot+comments%3F&l=1
Look at this site for using dual WAN connections: http://chris.olstrom.com/howto/setup-dual-wan/
It allows you to use the speed of both internet connections. You just have to use multiple connections to a site (load 2 pages, etc). I have not tested how it will react if one of the connections is pulled, but it should recognize that it has no connection and move to the other table. I used this at a friend's apartment where they gave him "free" internet, but capped his speed per nic. We setup a VM with 10 vnics and were able to use the speed of all of them at once.
Mpath-tools is a set of programs for linux 2.6+ that aim to facilitate load balancing and failover over multiple and heterogeneous ISP connections.
Simple, build a routing computer, use it to switch when wireless connectivity isn't meeting your demands.
Anyone else suggesting anything else is just shilling for some company or another.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
While you can have traffic that follows different paths in the network - you can't expect to have one connection shared across two public WAN connections that have different public IP addresses. The best you will do with the Internet is to send one connection one way and the next the other way. You get load balancing and HA/reliability but you don't get combined bandwidth.
That will only ever work when the user is directly publicly addressable using the same IP address on both of the router. I am a network engineer and once I erroneously tried to do this.
Sounds like you are in what used to be Northern Ohio Telephone Co territory. NOTC was bought by GTE in 1968, the phone portion of GTE merged with Bell Atlantic to form Verizon in 1999, then Verizon spinning off a bunch of their business the last few years.
A Shadeless room is a brighter room.
We've found Sonicwalls to be the only small-business grade router to be able to effectively load-balance two connections without breaking the bank. It's actually surprising how hard it is to find a router that will load-balance correctly. I've worked with a variety of soft-routers, cisco and cisco smb equipment and fund that bang for buck, the sonicwalls are the only ones that produce real results. This opinion comes from many real-life dual-wan setups, and I've found time and time again that the homebrew solution didn't stack up.
.
1) My major uploads/downloads would not slow down her business and vice versa.
2) My investigation of NSFW websites would never be traced back to her business (although I know there a better ways around that).
3) If her network was down, I could run a cat-5 to her switch from mine and change her gateway machine setting temporarily and she was back up, and vice-versa.
4) If (slim chance) either of the firewall machines were to be hacked, presumably the other would remain un-hacked, and available.
Anyway, it worked for us.
Hi ,this is shenzhenelectronic.
Our website is http:/// www.shenzhenwholesale.com
we have some electronics ,for example Microsoft Xbox360 Live card 10000 US PointsMoster beats by Dr.Dre solo hdMoster beats Dr.Dre pro and so on.
Welcome to visit our website
Moster beats by Dr.Dre solo hd
http://www.shenzhenwholesale.com/monster-beats-by-dr-dre-solo-hd-headphones-black-red-white-hot-sell_p53915.html
Moster beats Dr.Dre pro
http://www.shenzhenwholesale.com/brand-new-monster-beats-by-dre-pro-headphones-in-white-black-5pcslot-hot-selling_p53932.html
Look at Sharedband: http://www.sharedband.com/.
Time to put that nice collection of data into Openstreetmap. Volunteers?
may be cheap atom box + ASG(Astaro Security Gateway,www.astaro.com(forums at astaro.org)) with free Home Edition license Potential Issues: - it probable will use more power than regular router after all - max 50 IPs behind it(but it's for home after all) - if want to you use ASG's extended funcionality(web filtering, advanced IPS(snort-based),etc) you will need to choose CPU carefully - you will have root password from ASG(it's really very specilized Linux) but it is assumed that you will use web-based control tools I use old athlon machine with 1.5 Gb RAM and some old hdd(and 3 network cards) as my ASG router
Do yourself a favor and choose openWRT instead, which is truly open source. www.openwrt.org
Set up a Vyatta Router/Firewall. It does a great job of load balancing and fail over. You just need three NICs to set it up. We use Vyatta everywhere and have had no problems. It just works!
Look at the Mikrotik SOHO routers, they're very capable, very reasonably priced (under $75 for the RB750G), and commonly used for just this kind of application. They're less well known in the US than the usual consumer brands because mostly aimed at commercial users, for setting up kiosks, access points, hot spots, and the like. They also need a bit more networking savvy to configure than the average consumer device, but that's just the price of more capabilities.