From: Philip Craig <philipc@snapgear.com>
To: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
Cc: Netfilter users list <netfilter@lists.netfilter.org>
Subject: Re: PMTU-D and conntrack
Date: Mon, 06 Feb 2006 16:43:16 +1000 [thread overview]
Message-ID: <43E6F004.4020404@snapgear.com> (raw)
In-Reply-To: <1139204858.2549.5.camel@localhost>
On 02/06/2006 03:47 PM, John A. Sullivan III wrote:
> Are the ICMP Destination Unreachable-Fragmentation Needed and DF Set
> (type 3, code 4) packets sent in response to a TCP packet doing PMTU
> discovery considered RELATED or does one need to allow NEW connections
> for such packets?
The man page says that ICMP errors are RELATED, but I seem to recall
them showing up as ESTABLISHED instead. In any case, fragmentation
needed errors are treated the same as other ICMP errors, and so an
accept ESTABLISHED/RELATED rule is enough.
> By the way, is there a way to specify code number in the --icmp-type
> match? I think one can do -p 1 --icmp-type fragmentation-needed but I
> usually use the numbers to avoid lookups, e.g., -p 1 --icmp-type 8.
> Thanks - John
The man page doesn't mention this, but if you run iptables -p icmp -h
then it says you can use type/code, eg -p 1 --icmp-type 3/4
prev parent reply other threads:[~2006-02-06 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 5:47 PMTU-D and conntrack John A. Sullivan III
2006-02-06 6:43 ` Philip Craig [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=43E6F004.4020404@snapgear.com \
--to=philipc@snapgear.com \
--cc=jsullivan@opensourcedevel.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.