|From: "Paul Robert Marino"
|Re: [NYLXS - HANGOUT] More on the Network Question
|Have you looked at the possibility of using iproute2 rules for example prioritized routes.
An other option I can think of is using openha or keepalived or other monitoring tool to monitor the route
and automaticaly switch the default route priority. Again this would also involve iproure2 but would have less latency on failover.
Man the "ip" command its realy cool what you can do with it. If your system does not have it look for a package called iproute2.
you would have to write some custom scripts to mannage it but it shouldn't be too difficult. Also a dynamic dns provider could be helpfull to you and for your website if you could find a hosting provider that could give you a deticated vm where you could configure a squid 3 revers proxy that might also be usefull very but be carefull about bandwidth charges.
From: "Spencer Guiley"
Subj: [NYLXS - HANGOUT] More on the Network Question
Date: Fri Nov 14, 2008 8:43 pm
Size: 841 bytes
I'm the guy that Ruben forwarded the note about the Networking question with
the Cable line and DSL both for a web server.
I've been working on this with the other people in our team and this idea
came up. It hasn't gotten passed on to where tech support checks it all out
so this may be something that can't be done.
Can we set up both lines so they come into one router, and then to ONE
server. So we have Server A with both lines going to it. When one line goes
down the next one picks up? This would be almost like a 100% uptime.
We aren't a large hosting company but still strive for the best service
possible without going into debt. We are getting some quotes on T1 lines,
but I don't think they will be able to beat the prices I'm seeing now with
this Business DSL line.
Thanks for any help or ideas!