All of lore.kernel.org
 help / color / mirror / Atom feed
* Question regarding packet src/dst rewriting
@ 2004-08-20 16:32 Russell Handorf
  2004-08-21 15:10 ` Samuel Jean
  0 siblings, 1 reply; 2+ messages in thread
From: Russell Handorf @ 2004-08-20 16:32 UTC (permalink / raw)
  To: netfilter

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Question regarding packet src/dst rewriting
  2004-08-20 16:32 Question regarding packet src/dst rewriting Russell Handorf
@ 2004-08-21 15:10 ` Samuel Jean
  0 siblings, 0 replies; 2+ messages in thread
From: Samuel Jean @ 2004-08-21 15:10 UTC (permalink / raw)
  To: Russell Handorf; +Cc: netfilter

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.




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-08-21 15:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-20 16:32 Question regarding packet src/dst rewriting Russell Handorf
2004-08-21 15:10 ` Samuel Jean

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.