From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing
Date: Tue, 25 Dec 2001 12:16:48 +0000 [thread overview]
Message-ID: <marc-lartc-100928267119992@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416816@msgid-missing>
On Mon, Dec 24, 2001 at 10:58:14PM -0600, Daniel Wittenberg wrote:
> So I can change the out-going route by using:
> echo "100 link1" >> /etc/iproute2/rt_tables
> ip rule add from 172.16.1.0/24 table link1
> ip rule add from 172.16.2.0/24 table link1
> ip route add default via 1.1.1.1 dev $EXTERNAL_INTERFACE table link1
>
> echo "200 link2" >> /etc/iproute2/rt_tables
> ip rule add from 172.16.3.0/24 table link2
> ip rule add from 172.16.4.0/24 table link2
> ip rule add from 172.16.5.0/24 table link2
> ip route add default via 2.2.2.2 dev $EXTERNAL_INTERFACE table link2
Looks good.
> and if I understand this correctly, this doesn't change anything in
> iptables, so I can still this at the end of my firewall script. I'll
> also want to use SNAT and change the out-going IP's so they come back on
> the correct link. Look good? I can't test this in production very
> often, so before I do I thought I'd run it by everyone since I'm very
> much a newbie on tc...
We use a combination of SNAT/DNAT, MASQ, CBQ, iptables AND Policy routing in
production, and it all works fine.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-25 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 11:13 [LARTC] routing Spyros
2001-01-03 12:37 ` David
2001-01-05 12:25 ` Junus
2001-01-05 12:33 ` Junus
2001-07-06 14:03 ` [LARTC] Routing Dave Miller
2001-07-06 15:01 ` Arthur van Leeuwen
2001-07-06 15:18 ` Dave Miller
2001-07-07 6:33 ` Deepak singhal
2001-07-07 18:24 ` Arthur van Leeuwen
2001-07-07 18:33 ` Dave Miller
2001-07-07 18:37 ` Arthur van Leeuwen
2001-12-25 4:58 ` [LARTC] routing Daniel Wittenberg
2001-12-25 12:16 ` bert hubert [this message]
2002-10-30 12:57 ` [LARTC] Routing Jose Sebastiao Martins
2002-10-30 15:57 ` Martin A. Brown
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-100928267119992@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox