From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing to two interfaces
Date: Wed, 20 Nov 2002 23:05:43 +0000 [thread overview]
Message-ID: <marc-lartc-103783366010403@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103783300809624@msgid-missing>
Paco,
IP routing decisions are stateless.
You'll need to define your problem a bit more clearly (for yourself).
Once you understand exactly what you are trying to do (why you are
splitting the traffic this way) you'll be able to answer the question you
pose.
If you wish to look at some simple examples of split access, see my
chapter on advanced routing:
http://plorf.net/linux-ip/html/adv-routing.htm
For outbound split access (or inbound), see these sections in particular.
http://plorf.net/linux-ip/html/adv-routing.htm#ADV-MULTI-INTERNET-OUTBOUND
http://plorf.net/linux-ip/html/adv-routing.htm#ADV-MULTI-INTERNET-INBOUND
It doesn't sound like you wish to use a multipath route, but if you do,
you should probably read the LARTC docs on load sharing split access:
http://lartc.org/howto/lartc.rpdb.multiple-links.html
Good luck,
-Martin
: Hello,
:
: Sorry if this question is very common, but I searched the
: maillist archive and didn't found an answer...
:
: I have a linux box with 3 interfaces, 2 of them have public IPs
: (eth1 and eth2), and the third is a private IP (our LAN). I want to do the
: following: if a packet is coming from eth1, it must be forwarded to eth0,
: and when it comes back, it must be routed to eth1. In case of packet comes
: from eth2, it must be forwarded to eth0, and the respose must be routed to
: eth2. In other words, a packet must leave our network by the interface it
: come.
:
: I tried several combinations of iptables, 'ip rule' and 'ip
: route', but it didn't work...
:
: I appreciate any help, thanks :)
:
:
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-20 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 22:55 [LARTC] routing to two interfaces Paco Brufal
2002-11-20 23:05 ` Martin A. Brown [this message]
2002-11-20 23:26 ` Robert Felber
2002-11-20 23:34 ` Robert Felber
2002-11-20 23:45 ` Martin A. Brown
2002-11-21 0:04 ` Robert Felber
2002-11-21 0:09 ` Robert Felber
2002-11-21 0:27 ` Paco Brufal
2002-11-21 0:38 ` Paco Brufal
2002-11-21 3:37 ` Martin A. Brown
2002-11-21 8:27 ` Arthur van Leeuwen
2002-11-21 18:28 ` Paco Brufal
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-103783366010403@msgid-missing \
--to=mabrown-lartc@securepipe.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.