From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: ICMP Connections ...
Date: Tue, 24 Aug 2004 22:05:15 +0100 [thread overview]
Message-ID: <200408242205.16243.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <20040824133610.80037.qmail@web14926.mail.yahoo.com>
On Tuesday 24 August 2004 2:36 pm, Chetan Nagaraja wrote:
> Dear All,
> First of all, let me introduce as a total newbie in filtering and iptables.
>
> To ping a host in a different network, I have configured a dual homed[ two
> network interfaces] linux system to act as NAT router. I have add a rule in
> the NAT table of iptables, to achieve the following. If the Linux system
> recieves a icmp packet from a particular host in NETWORK A addressed to a
> particular HOST in NETWORK B , perform SNAT of the ICMP packet to that of
> the Linux System, so that the icmp replies reaches the Linux system.
I think you probably mean DNAT?
> The above is working very fine. The ICMP requests are reaching the expected
> destination. But I'am unable to understand the fact that the ICMP replies
> are reaching the host in NETWORK A which had generated the requests,
> without adding a DNAT rule for the same. How is this possible, does
> iptables automatically redirect ICMP replies ?
Yes, and not just ICMP. Netfilter automatically applies reverse-nat to reply
packets in accordance with the forward nat rules you specify for the original
packets.
> And How to avoid the same.
What do you mean?
Regards,
Antony.
--
How I want a drink, alcoholic of course, after the heavy chapters involving
quantum mechanics.
- 3.14159265358979
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-08-24 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 13:36 ICMP Connections Chetan Nagaraja
2004-08-24 21:05 ` Antony Stone [this message]
2004-08-24 21:24 ` Aleksandar Milivojevic
2004-08-24 21:56 ` Deepak Seshadri
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=200408242205.16243.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox