From: Russell Handorf <rhandorf@closednetworks.com>
To: netfilter@lists.netfilter.org
Subject: Question regarding packet src/dst rewriting
Date: Fri, 20 Aug 2004 12:32:31 -0400 [thread overview]
Message-ID: <4126279F.7040109@closednetworks.com> (raw)
Hello all,
I have a linux router over here with 4 ethernet nics running on 2.6.4
kernel. The respective IP's are as follows:
eth0 : peering point to ISP
eth1: public routable IP block (/23)
eth2 : 172.16.0.1
eth3 : 192.168.0.1
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).
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.
Any help would be greatly appreciated.
Thanks again,
Russ
next reply other threads:[~2004-08-20 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 16:32 Russell Handorf [this message]
2004-08-21 15:10 ` Question regarding packet src/dst rewriting Samuel Jean
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=4126279F.7040109@closednetworks.com \
--to=rhandorf@closednetworks.com \
--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.