From: Mauricio Tavares <raubvogel@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: newbie: forward rule to itself
Date: Wed, 27 Oct 2010 15:47:36 -0400 [thread overview]
Message-ID: <4CC881D8.3060408@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1010272116580.19157@obet.zrqbmnf.qr>
On 10/27/2010 03:17 PM, Jan Engelhardt wrote:
> On Wednesday 2010-10-27 21:02, Mauricio Tavares wrote:
>
>> Let's say I have server1 with two ports, eth0 and eth0, and server2
>> whose eth0 port is connected to server1's eth1. And let's say the subnet
>> between them is 192.168.1.0/24 while the one server1's eth0 is connected to is
>> 192.168.4.0/24.
>>
>> I have the following rules to forward port 6969 coming on eth0 on server1 to
>> port 6969 on server2's eth0:
>>
>> iptables -A PREROUTING -t nat -p tcp --dport 6969 -j DNAT --to
>> 192.168.1.server2:6969
>> iptables -A INPUT -d 192.168.4.server1 -p tcp -m tcp -m state --state NEW
>> --dport 6969 -j ACCEPT
>> iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
>>
>> Any machine in 192.168.4.0/24 seems to be able to get to server2 by using
>> 192.168.1.server1:6969. But, if I try to connect to 192.168.1.server1:6969 on
>> server1 itself, I will not be forwarded to server2. What am I missing here?
>
> That prerouting only applies to packets coming from devices connected to
> the machine.
How would the prerouting that applies to packets coming from the
machine itself look like?
next prev parent reply other threads:[~2010-10-27 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 19:02 newbie: forward rule to itself Mauricio Tavares
2010-10-27 19:17 ` Jan Engelhardt
2010-10-27 19:47 ` Mauricio Tavares [this message]
2010-10-27 20:00 ` Jan Engelhardt
2010-10-27 21:03 ` Mauricio Tavares
2010-10-28 8:01 ` Pascal Hambourg
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=4CC881D8.3060408@gmail.com \
--to=raubvogel@gmail.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox