[Cialug] multi-homed apache ssl

[Dave Hala Jr]

The IP I listed before I made up. A whois on one of my ip addresses
returns the following:

Qwest Communications Company, LLC QWEST-INET-10 (xxx-xxx-xxx-x-x-x)
xxx.xxx.xxx.xxx - xxx.xxx.xxx.xxx
OSIS INC Q0802-xxx-xxx-xxx-xxx (NET-xxx-xxx-xxx-xxx-xxx) xxx.xxx.xxx.xxx
- xxx.xxx.xxx.xxx

I have a commercial grade T-1 circuit from Century Link/Qwest. I was
really happy with the service, until I had a problem. Secondly, I'm not
paying Qwest TWICE for more of the same. It wont solve my problem. 

I think the only safe way to cover my behind is to have a second
connection from a differant provider, using a differant transport and
having "automatic" failover.

I'm just trying to get a little info and wash some of the blood off
before I get back in the deep water with the sharks.

:) Dave


On Thu, 2011-11-10 at 13:38 -0600, L. V. Lammert wrote:
> On Thu, 10 Nov 2011, Dave Hala Jr wrote:
> 
> > I have a /27 now, I could probably get a /24 if I needed too.
> >
> If the IP you provided previously is one of them, *YOU* do not have a /27,
> Quest is allowing you to USE the /27. Normally, BGP is done by advertising
> your block via the ASN that your organization owns. IPv4s are all
> allocated to ISPs, so you would have to obtain a V4 address from an ISP so
> you would be 'subserviant' to their services.
> 
> Your best solution is to use two circuits from Quest, or upgrade to one of
> the commercial-grade circuits like a T1 for better reliability.
> 
> Most folks don't even think about reliability, but we have had a grand
> total of about two hours of downtown time on our T1 circuit over the past
> 10 years (and that was due to a lightening strike), whereas our folks with
> Charter [especially] are typically down for hours a *WEEK* (the
> connection just stop routing traffic)!
> 
> 	Lee
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug