From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: icmp echo reply && FORWARD chain
Date: Mon, 3 May 2004 00:03:48 +0100 [thread overview]
Message-ID: <200405030003.48725.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <009801c43096$e999e0a0$68892090@grouse>
On Sunday 02 May 2004 11:43 pm, Jee J.Z. wrote:
> Hi Antony,
>
> Oh, dear! I am making a lot ot mistakes. The rules are as follows:
>
> iptables -F
> iptables -F -t nat
> iptables -I FORWARD -j QUEUE
> iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to global_ip
> iptables -t nat -A PREROUTING -i eth0 -j DNAT --to 192.168.0.2
>
> The problem is that it seems icmp request destined to PC2 can be caught by
> the FORWARD chain, however, the icmp reply destined to PC2 is ignored by
> the FORWARD chain.
This may seem like a strange suggestion (however, it seems you are trying to
do something quite strange, I think...), but try putting the QUEUE target
into the mangle table instead of the filter table (mangle tables generally
see more packets than filter tables, because nothing 'magic' happens in the
background, causing packets to bypass them, which is the case with filter
tables and nat tables):
iptables -A FORWARD -t mangle -j QUEUE
Regards,
Antony.
--
The idea that Bill Gates appeared like a knight in shining armour to lead all
customers out of a mire of technological chaos neatly ignores the fact that
it was he who, by peddling second-rate technology, led them into it in the
first place.
- Douglas Adams in The Guardian, 25th August 1995
Please reply to the list;
please don't CC me.
prev parent reply other threads:[~2004-05-02 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 14:24 icmp echo reply && FORWARD chain Jee J.Z.
2004-05-02 14:46 ` Antony Stone
2004-05-02 15:29 ` Jee J.Z.
2004-05-02 15:42 ` Antony Stone
2004-05-02 22:43 ` Jee J.Z.
2004-05-02 23:03 ` Antony Stone [this message]
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=200405030003.48725.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