From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: Real Cucumber <monkcucumber@yahoo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Help with ICMP Ruls
Date: Thu, 15 Jul 2004 14:57:28 -0500 [thread overview]
Message-ID: <40F6E1A8.6060705@pbl.ca> (raw)
In-Reply-To: <20040715192110.11412.qmail@web40702.mail.yahoo.com>
Real Cucumber wrote:
> That is why I'm not sure if I need ICMP supported on
> it or not, and not sure where do add the ICMP support
> (input, output, forward).
You need it in FORWARD, that's obvious. You also need it in OUTPUT
because ICMP packets can be generated on your forwarding machine too.
For example, if it fails to pass the packet to the next hop, it will
generate "no route to host/network" message back to originating host
(this ICMP packet will have source address of forwarding machine, so it
goes to OUTPUT chain). More examples of ICMP packets generated on your
forwarding machine (as result of receiving a packet that should be
forwarded) would be traceroute (which works by exploiting TTL exceeded)
and path MTU discovery (which works by exploiting don't fragment bit).
Note that removing match for RELATED from INPUT chain does not gain you
much (other than one line less in rules). If your machine only forwards
packets, no ICMP that ends up in INPUT chain will ever be in RELATED
state (it will be in either NEW or INVALID states).
--
Aleksandar Milivojevic <amilivojevic@pbl.ca> Pollard Banknote Limited
Systems Administrator 1499 Buffalo Place
Tel: (204) 474-2323 ext 276 Winnipeg, MB R3T 1L7
prev parent reply other threads:[~2004-07-15 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 17:03 Help with ICMP Ruls Real Cucumber
2004-07-15 18:43 ` Antony Stone
2004-07-15 19:21 ` Real Cucumber
2004-07-15 19:32 ` Antony Stone
2004-07-15 19:57 ` Aleksandar Milivojevic [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=40F6E1A8.6060705@pbl.ca \
--to=amilivojevic@pbl.ca \
--cc=monkcucumber@yahoo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.