From: "Michael Gerner Andreasen" <kawaki@hotmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Howto deal with more than one isp.
Date: Wed, 24 Sep 2003 07:35:08 +0000 [thread overview]
Message-ID: <marc-lartc-106438904019138@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106432713617783@msgid-missing>
> If i understand correctly, what you want, is the one PC doing the routing,
> firewalling and traffic shaping. It has one interface (perhaps with
multiple
> addresses) that everyone uses as their default gateway.
> It then has one or more another interface/s that it directs load balanced
traffic out
> across the links to the 3 ISPs.
>
> You should be able to do this fairly easily with an equalized default
route and
> source based routing (for the return traffic).
> Then just plug in the firewall and QoS on the interfaces in between.
>
> Was that the answer you wanted? or did you want some specific examples?
>
> For the DNS problem, you may want to run something like dnsmasq
> (http://thekelleys.org.uk/dnsmasq/doc.html) on your router PC, and then
add all the
> dns servers to your resolve.conf and add appropriate host routes on the
correct gateways.
>
> regards
>
Well it was close, 1 interface to talk to the 3 routers, the routers simply
forwards all trafik to em to the linux box doing all the funny stuff, and
another interface in the box, that sends the stuff to the proxy server
dirrectly, then the proxy sends out stuff on its second interface to the
same switch but just to the lan.
R=Router
S=Switch
C=Clints
A=Airlink equipment
G=Gateway
P=Proxy
R1 <-> S1 <-> A & C
R2 <-> S2 <-> A & C
R3 <-> S3 <-> A & C & G & P
Gateways external link to the switch.
Gateways internal link to proxys external link
Proxys internal link to S3
S3 <==> G <==> to P
S3 <==> P <==> to G
R1 connects to the switch in building 1, and that switch is connected to 4
clients and a bridge.
R2 connects to the switch in building 2, and that switch is connected to 4
clients and a bridge.
R3 connects to the switch in building 3, and that switch is connected to 4
clients, 4 servers and a Accesspoint that the bridge connects to.
Accesstimes across network smallere than 1ms except from airlink 1-3ms and
11Mbit but it aint bad at all.
hope it helps alittle.
btw. Gateway proberly will have 192.168.0.1 as ip but i dont know if i
should make virtuals on it or, i could live with just one, could i do
balancing on routes only? instead of interfaces? as you normaly have 3 nics
till 3 different isp's and then 1 or 2 to your lan or dmz, this is almost
the otherway around 3 isp's on 1 nic, then 1 nic to a proxy server and from
there to the switch and back to clients or the servers.
forgot to say that it does need to work for 3+ connections >=) as we plan on
adding 3 more with in a year if we ever get to solv this problem.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-09-24 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 14:18 [LARTC] Howto deal with more than one isp Michael Gerner Andreasen
2003-09-23 22:58 ` Damion de Soto
2003-09-24 7:35 ` Michael Gerner Andreasen [this message]
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=marc-lartc-106438904019138@msgid-missing \
--to=kawaki@hotmail.com \
--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.