From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath Multirouter - Can it be done?
Date: Thu, 11 Oct 2007 14:19:23 +0000 [thread overview]
Message-ID: <470E30EB.80900@riverviewtech.net> (raw)
In-Reply-To: <a11134e1c29db0b6f777ee11ab768d79@coairnet.com>
On 10/10/07 22:44, Tony Hagans wrote:
> Currently I have a setup that involves connections from several
> different providers ranging from 6 mbit DSL's to 10 mbit fractional
> DS3 connections tied together to provide multipath high availability
> internet in our area for schools and businesses. We recently
> extended our coverage to another area which has several other ISP's.
> The box that is doing multiwan right now is the only gateway for the
> entire network and for some sites it is several hops back to that
> gateway. My goal is for us to purchase bandwidth in other locations,
> install a linux box and have multiple gateways available, but I think
> this is easier said than done. I will diagram this as best I can for
> you in current and future setup modes.
...
> My goal is for people in area 1-4 to all be able to use any of the
> connections to ISP 1-z and if one fails it passes the traffic through
> the network to an available route. Area 1-4 don't current have any
> linux hardware but it has been a long standing plan to put some in
> place in those areas as well so if that is required it could be done.
> These areas are all serviced by different small ISP's and would make
> acceptable alternate routes say if a backhual failed for some reason
> so that is the goal.
Like Alex said, I think you need at least an interior routing protocol.
I'd also recommend that you look in to getting your own address space
from your regional provider. Ideally you would get multiple if not all
of the ISPs to BGP advertise your address space out to the world. In
addition to the world knowing the better / best routes in to you
depending on where the traffic is originating from, your network would
know the better / best routes to take out to destinations with relation
to your ingress / egress points.
Additionally as long as you are doing NATing much closer to the
customer, or the customer is doing it them selves, you could have
multiple routes to / from the customer with out worrying about changing
NAT IPs.
> Thanks for any input.
You are welcome.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-10-11 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 3:44 [LARTC] Multipath Multirouter - Can it be done? Tony Hagans
2007-10-11 3:53 ` Alex Samad
2007-10-11 14:19 ` Grant Taylor [this message]
2007-10-11 19:07 ` Tony Hagans
2007-10-11 20:02 ` Grant Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=470E30EB.80900@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.