From: <russ@essentialmix.ca>
To: lartc@vger.kernel.org
Subject: [LARTC] Policy Routing Help
Date: Mon, 01 Apr 2002 17:45:59 +0000 [thread overview]
Message-ID: <marc-lartc-101768403719512@msgid-missing> (raw)
Hey guys, can anyone comment on this if it is possible?
My setup:
Linux Box Cable
_____ E0 _____
| |_______|___|____
| |
| | DSL
| | E1 _____
| |_______|___|____
|___|
Hopefully everyone can interperet my diagram. Anyhow, I have an FTP
server running off the Linux Box. The DNS resolves to Eth0 which is the
NIC attached to the Cable modem provider and the default route is set to
the Cable next-hop. Eth1 is attached to My Network. What I would like to
happen is that all incoming FTP traffic to Eth0 will always return out
Eth0 through the Cable ISP. Any other traffic will take the DSL provider
via a default route to the DSL next-hop
I can think of 2 ways to do this:
1) Mark FTP traffic and create a rule to set the next-hop to the Cable
default route
2) Configure policy routing such that if traffic is destined to Eth0 IP
address, the next-hop is set to the Cable provider.
Because there is a default route configured on the linux box to the Cable
ISP, all return traffic regardless of the interface it was received on
will always take the Cable ISP. I would prefer option #2. Can anyone
shed some light on the config necessary to do this? This is pretty quick
and dirty with policy routing on IOS, but I am struggling a little bit on
the linux config. Thanks all!
--
-Russ
essentialmix.ca
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-04-01 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-01 17:45 russ [this message]
2002-04-02 8:31 ` [LARTC] Policy Routing Help Arthur van Leeuwen
2002-04-03 16:40 ` Patrick McHardy
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-101768403719512@msgid-missing \
--to=russ@essentialmix.ca \
--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.