|FROM ||From: "Spencer Guiley"
|SUBJECT ||RE: [NYLXS - HANGOUT] More on the Network Question
|From lest-hangout-at-mrbrklyn.com Sat Nov 15 12:10:09 2008
Received: from www2.mrbrklyn.com (localhost [127.0.0.1])
by www2.mrbrklyn.com (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id mAFHA680007624
for ; Sat, 15 Nov 2008 12:10:08 -0500
Received: (from majordomo-at-localhost)
by www2.mrbrklyn.com (8.13.1/8.13.1/Submit) id mAFHA66Y007623
for hangout-outgoings; Sat, 15 Nov 2008 12:10:06 -0500
X-Authentication-Warning: www2.mrbrklyn.com: majordomo set sender to lest-hangout-at-nylxs.com using -f
Received: from fmailhost03.isp.att.net (fmailhost03.isp.att.net [22.214.171.124])
by www2.mrbrklyn.com (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id mAFH9uxA007620
for ; Sat, 15 Nov 2008 12:10:05 -0500
Received: from guileys1 (host-216-78-81-103.bgk.bellsouth.net[126.96.36.199])
by isp.att.net (frfwmhc03) with SMTP
id <20081115170942H0300pqr4le>; Sat, 15 Nov 2008 17:09:44 +0000
From: "Spencer Guiley"
Subject: RE: [NYLXS - HANGOUT] More on the Network Question
Date: Sat, 15 Nov 2008 12:09:40 -0500
X-Mailer: Microsoft Office Outlook 12.0
I haven't looked into much at all. I pretty much let the tech guy just work
In this case since I know what our goal is, and what we need, I thought
maybe others might know of an easy or fast way to set it up.
I'm forwarding on all of the messages to my tech guy so he can see what
ya'll are talking about and research and find out what one would fit our
Thanks for your thoughts---and keep-em coming
From: lest-hangout-at-mrbrklyn.com [mailto:lest-hangout-at-mrbrklyn.com] On Behalf
Of Paul Robert Marino
Sent: Saturday, November 15, 2008 12:25 AM
To: hangout-at-mrbrklyn.com; hangout-at-mrbrklyn.com
Subject: Re: [NYLXS - HANGOUT] More on the Network Question
Have you looked at the possibility of using iproute2 rules for example
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!
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.175 / Virus Database: 270.9.2/1783 - Release Date: 11/12/2008