All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Liao <maillist@Gallantry.com>
To: netfilter@lists.netfilter.org
Cc: delaunois@info.ucl.ac.be
Subject: How to change a packet's arriving interface? -j ROUTE?
Date: Fri, 06 Dec 2002 08:41:28 -0800	[thread overview]
Message-ID: <3DF0D338.C2F4E50@Gallantry.com> (raw)

Hi,

I have a firewall running iptables with 3 interfaces: LAN, WAN and DMZ. 
The LAN IP address is 10.0.0.1/24, WAN 66.134.34.157/28, and DMZ
66.134.34.249/28.  The WAN interface connects to the Internet and the
DMZ interface connects to a stub network.

When someone sends a packet to the IP address of the DMZ interface from
the Internet, the packet x.x.x.x->66.134.34.249 arrives at the WAN
interface.  I want to know if there is a way using iptables (maybe with
other tools such as iproute2) to make this packet to appear as if it
arrives at the DMZ interface.  The packet itself should not be
modified.  I need this to work because I am running an IPSec VPN with
FreeS/WAN on the DMZ interface.  When the ESP packets arrives on the WAN
interface, they cannot be properly processed by IPSec because the ipsec0
interface is tied to the DMZ interface directly.  

I looked at the mangle table but could not figure out if it is the right
direction.  I read about the ROUTE target but do not know if this target
is for diverting packets to be sent OUT on another interface, or can it
be used to change a packet's arriving interface.

Thanks in advance.

Jason Liao


             reply	other threads:[~2002-12-06 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 16:41 Jason Liao [this message]
2002-12-06 17:27 ` How to change a packet's arriving interface? -j ROUTE? Cédric de Launois
2002-12-09  5:32 ` Raymond Leach
2002-12-10  1:32   ` Jason Liao
2002-12-10  5:23     ` Raymond Leach

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=3DF0D338.C2F4E50@Gallantry.com \
    --to=maillist@gallantry.com \
    --cc=delaunois@info.ucl.ac.be \
    --cc=netfilter@lists.netfilter.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.