Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Samuel Jean" <sj-netfilter@cookinglinux.org>
To: Russell Handorf <rhandorf@closednetworks.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Question regarding packet src/dst rewriting
Date: Sat, 21 Aug 2004 11:10:35 -0400 (EDT)	[thread overview]
Message-ID: <32820.207.236.167.130.1093101035.squirrel@207.236.167.130> (raw)
In-Reply-To: <4126279F.7040109@closednetworks.com>

On Fri, August 20, 2004 12:32 pm, Russell Handorf said:
> The weird behavior I am having is that whenever a packet from the
> Internet comes in interface eth0, and gets forwarded to a server on
> eth1, the server which resides on the eth1 side of the network sees the
> source IP as coming from the router and not the real host on the
> Internet. Vice versa applies as well (a node behind eth1 sends a packet
> out to, say, google.com. Google.com sees the data as coming from the
> router, and not the node which is behind eth1).
>

My assumption is that you are using a MASQUERADE rule regardless of the
outgoing device.

> I dont understand why the packet headers are being re-written. I also
> dont understand if this is a specific problem with iptables, or the
> linux kernel itself.
>
> eth2 and eth3 are masquerading, but eth1 is not.
>

Okay, so you are using 2 MASQUERADE rules with specific outgoing device ?
Please post your ruleset. PREROUTING and POSTROUTING chains should be enough.




      reply	other threads:[~2004-08-21 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 16:32 Question regarding packet src/dst rewriting Russell Handorf
2004-08-21 15:10 ` Samuel Jean [this message]

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=32820.207.236.167.130.1093101035.squirrel@207.236.167.130 \
    --to=sj-netfilter@cookinglinux.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=rhandorf@closednetworks.com \
    /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