From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Subject: Re: icmp forward
Date: Fri, 30 Jan 2009 12:36:59 +0100 [thread overview]
Message-ID: <4982E65B.10509@chello.at> (raw)
In-Reply-To: <4982E363.6070005@cetrtapot.si>
Hinko Kocevar wrote:
> Pascal Hambourg wrote:
>
>> Hello,
>>
>> Hinko Kocevar a écrit :
>>
>>> Christoph Paasch wrote:
>>>
>>>> On Fri January 30 2009, Hinko Kocevar wrote:
>>>>
>>>>> Is it possible to 'port forward' ICMP requests?
>>>>>
>>>> You can match the protocol on ICMP packets with -p icmp and let the
>>>> port-
>>>> specific stuff out of it, as ICMP doesn't uses portnumbers. But the
>>>> problem will be, that your external machine won't be reachable for
>>>> icmp packets. (as every icmp packets will get forwarded) It may be
>>>> ennoying if MTU or ping packets doesn't reach anymore your machine.
>>>> That depends on the usage of your gateway.
>>>>
>>> Yes, that is what I was afraid of. I think that gateway should still
>>> remain
>>> available for ICMP echo-reply from external network.
>>>
>> You must not be afraid of redirecting incoming ICMP replies or error
>> messages originally destined to the gateway to the mobile device. These
>> messages have the state ESTABLISHED or RELATED, while NAT rules see only
>> packets creating a new "connection", which have the state NEW. Even
>> though, you could have your DNAT rule match only the echo-request type
>> with the --icmp-type option. However, if you redirect ICMP echo request
>> to the device, indeed you cannot ping the gateway any more on the same
>> external address. You need a separate address.
>>
>
> Not quite sure what it is all about, but is it doing something like:
> # ifconfig eth0:1 172.31.64.121 netmask 255.255.254.0 up
>
> And later..
> # iptables -A FORWARD -p icmp --icmp-type echo-request -j ACCEPT
> # iptables -t nat -A PREROUTING -i eth0 -p icmp -j DNAT --to-destination 10.1.1.2
>
>
try:
iptables -t nat -A PREROUTING -i eth0 -d 172.31.64.121 -p icmp -j DNAT --to-destination 10.1.1.2
> This is not what I expected - shouldn't the request destined for eth0:1 be
> answered by the gateway device?
>
next prev parent reply other threads:[~2009-01-30 11:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 8:18 icmp forward Hinko Kocevar
2009-01-30 8:33 ` Michele Petrazzo - Unipex srl
2009-01-30 8:53 ` Payam Chychi
2009-01-30 9:19 ` Hinko Kocevar
2009-01-30 8:49 ` Christoph Paasch
2009-01-30 9:12 ` Hinko Kocevar
2009-01-30 10:53 ` Pascal Hambourg
2009-01-30 11:24 ` Hinko Kocevar
2009-01-30 11:35 ` Hinko Kocevar
2009-01-30 11:42 ` Pascal Hambourg
2009-01-30 11:36 ` Mart Frauenlob [this message]
2009-01-30 9:20 ` Mart Frauenlob
2009-01-30 11:36 ` Hinko Kocevar
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=4982E65B.10509@chello.at \
--to=mart.frauenlob@chello.at \
--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