All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: RE : iptable 1.2.11 and kernel 2.6.11-1 compatibility issue
Date: Wed, 01 Jun 2005 12:45:48 -0500	[thread overview]
Message-ID: <429DF44C.2040706@riverviewtech.net> (raw)
In-Reply-To: <004801c566c9$8134fbc0$7c66e4a0@supelec.fr>

Thibault Le Meur wrote:
> Thanks for your reply,

*nod*  No problem.

> You're right, but in fact I didn't give the whole configuration. The
> iptables script is generated by Fwbuilder and the following lines are
> relevant:
> 
> # Default policy is to DROP everything
> $IPTABLES -P OUTPUT  DROP
> $IPTABLES -P INPUT   DROP
> $IPTABLES -P FORWARD DROP
> 
> # First accept any related, established packets
> $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
> 
> #
> # Then Rule 0 for the loopback interface
> #
> $IPTABLES -A INPUT  -i lo  -m state --state NEW  -j ACCEPT
> $IPTABLES -A OUTPUT  -o lo  -m state --state NEW  -j ACCEPT
> 
> I think the "# First accept any related, established packets" rules should
> do the same as the proposed modification.
> 
> Am I right?

I would think so and agree with you on this one.

I'm taking it that there is more to your script?  If that is the case could we see the entire script or at the very least an output of iptables-save after your script has run?



Grant. . . .


  reply	other threads:[~2005-06-01 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 15:05 iptable 1.2.11 and kernel 2.6.11-1 compatibility issue Thibault Le Meur
2005-06-01 16:21 ` Taylor, Grant
2005-06-01 16:46   ` RE : " Thibault Le Meur
2005-06-01 17:45     ` Taylor, Grant [this message]
2005-06-02  8:54   ` Thibault Le Meur

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=429DF44C.2040706@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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.