Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Fwd: Re: Help with ICMP Ruls
Date: Thu, 15 Jul 2004 21:13:55 +0100	[thread overview]
Message-ID: <200407152113.55450.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <20040715195526.1368.qmail@web40709.mail.yahoo.com>

On Thursday 15 July 2004 8:55 pm, Real Cucumber wrote:

> I do have a state rule already for allowing any
> established,related connections.

In that case you are already allowing ICMP :)

> So should I add another one such as:
>
> iptables -A FORWARD -p icmp -m state --state RELATED
> -j ACCEPT

No.   ICMP messages which are RELATED to the existing SSH connections will get 
matched by the final rule in this section of your rules:

# Allow previously initiated and accepted connections
# to bypass firewall tests (state matching)
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT

Just out of interest, why do you have the first two of these rules, if you 
have no INPUT or OUTPUT traffic?

Regards,

Antony.

-- 
Microsoft may sell more software than any other company, but McDonald's sell 
more burgers than any other company, and I think the other similarities are 
obvious...

                                                     Please reply to the list;
                                                           please don't CC me.



  parent reply	other threads:[~2004-07-15 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15 19:55 Fwd: Re: Help with ICMP Ruls Real Cucumber
2004-07-15 20:04 ` Aleksandar Milivojevic
2004-07-15 20:13 ` Antony Stone [this message]
2004-07-15 20:18   ` Real Cucumber

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=200407152113.55450.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