From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2 gateways out
Date: Sun, 23 Sep 2001 14:59:19 +0000 [thread overview]
Message-ID: <marc-lartc-100125720127764@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100119531523323@msgid-missing>
On Sat, Sep 22, 2001 at 05:45:50PM -0400, Largo Hellenz wrote:
> hi,
>
> first, i'd like to say im so happy this list is finally back up!!!!
I'm happy too :-)
> those two connect to a central 2.4.2 machine with 5 nics.
> box C (eth0 10.0.0.1/24, eth1 10.1.1.2/24, eth2 10.2.2.2/24, eth3
> 10.3.3.1/24, eth4 10.4.4.1/24)
Very impressive.
> the most important thing is to load balence between the two cable modems
> and route all traffic out the right way if one of the cable modems goes
> down.
This depends greatly on what's on the other side of the cable modems - are
there two separate ISPs?
This situation is very difficult to resolve properly, the best way is to
experiment a bit. You will most probably need a cronscript to detect which
modems are operating.
> if possible, possibly even send some packets out one way and some out
> aNother (based on payload content and packet tagging?) but this is for my
> next lesson :)
Policy routing does this for you, and may in fact be the best solution.
Route part of your customers to one modem, and others to the other, if both
are functioning. If you detect that stuff is down, route everybody to the
other one.
> [root@io /root]# cat masquerade
> #!/bin/sh
>
> modprobe ip_tables
> modprobe ip_nat_ftp
> modprobe ip_conntrack
> modprobe ip_conntrack_ftp
> modprobe iptable_nat
Having modules autoload themselves is way easier, bt.
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> /sbin/iptables -F
I would advise to change the path, so you can leave out the redundant /sbin
on every line.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-09-23 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-22 21:45 [LARTC] 2 gateways out Largo Hellenz
2001-09-23 14:59 ` bert hubert [this message]
2001-09-23 19:04 ` Largo Hellenz
2001-09-23 20:00 ` bert hubert
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-100125720127764@msgid-missing \
--to=ahu@ds9a.nl \
--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.