All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: Netfilter User Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: ICMP and connection tracking
Date: Thu, 20 May 2004 11:24:07 -0500	[thread overview]
Message-ID: <40ACDBA7.5010008@pbl.ca> (raw)
In-Reply-To: <200405201637.10513.Antony@Soft-Solutions.co.uk>

Antony Stone wrote:
> On Thursday 20 May 2004 4:06 pm, Aleksandar Milivojevic wrote:
> 
>>Are ICMP packets related to new and established TCP connections and UDP
>>traffic considered to be part of them,
> 
> An ICMP packet which is returned in response to a previously sent TCP or UDP 
> packet is considered to be RELATED.

Thanks.  This preaty much answers my question.

>>or do I need to have explicit rules like
>>
>>    -A INPUT -p icmp -m state --state RELATED -j ACCEPT
>>
>>for things like path MTU discovery, traceroute, ICMP port unreachables,
>>and so on to work properly?
> 
> Nothing wrong with the above rule, however remember that it isn't only ICMP 
> packets which are considered to be RELATED - in an FTP connection, for 
> example, the reverse (data) connection is considered to be RELATED to the 
> original (control) connection, even though it's another TCP link, not ICMP.

Yup, I'm aware of that part.

>>Any downsides of using generic rule like above (if it is needed)?
> 
> Most people use an even *more* generic rule:
> 
> iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

Actually, the orginal question was prompted because I'm avoiding this 
more generic rule :-)

-- 
Aleksandar Milivojevic <amilivojevic@pbl.ca>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7


      reply	other threads:[~2004-05-20 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 15:06 ICMP and connection tracking Aleksandar Milivojevic
2004-05-20 15:37 ` Antony Stone
2004-05-20 16:24   ` 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=40ACDBA7.5010008@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --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.