From: "Jee J.Z." <jz105@york.ac.uk>
To: netfilter@lists.netfilter.org
Subject: Re: icmp echo reply && FORWARD chain
Date: Sun, 2 May 2004 16:29:05 +0100 [thread overview]
Message-ID: <007b01c4305a$34258300$68892090@grouse> (raw)
In-Reply-To: 200405021546.51594.Antony@Soft-Solutions.co.uk
Hi Antony,
Sorry for the confusion.
> On Sunday 02 May 2004 3:24 pm, Jee J.Z. wrote:
>
> > Hi all,
> >
> > My rules on a gateway linux box (PC2) are set as follows:
> >
> > Internet(PC1 and so
on)-----------(eth0:global_ip)-PC2-(eth1:192.168.0.1)-------------Internal
> > networks(PC3(192.168.0.2) and so on...)
> >
> > 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 eth1 -j DNAT --to 192.168.0.2
>
> That is a weird-looking rule. Where does IP 192.168.0.2 exist on the
above
> diagram?
It's the internal IP of PC3. I modified the diagram a little bit. Thank you.
Jee
> > ICMP echo request packets from PC1 or PC3 to PC2 can be caught by the
> > FORWARD chain queuing to userspace, however, ICMP echo reply (in
response
> > to ping request from PC2) packets from PC1 or PC3 to PC2 will be ignored
by
> > the FORWARD chain. Is this a reasonable phenomenon? Could anyone tell me
> > the reasons? Thanks a lot in advance!
> >
> > Cheers,
> > Jee
>
> --
> Ramdisk is not an installation procedure.
>
> Please reply to the
list;
> please don't CC
me.
>
>
>
next prev parent reply other threads:[~2004-05-02 15:29 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. [this message]
2004-05-02 15:42 ` Antony Stone
2004-05-02 22:43 ` Jee J.Z.
2004-05-02 23:03 ` Antony Stone
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='007b01c4305a$34258300$68892090@grouse' \
--to=jz105@york.ac.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