From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: iptable 1.2.11 and kernel 2.6.11-1 compatibility issue
Date: Wed, 01 Jun 2005 11:21:51 -0500 [thread overview]
Message-ID: <429DE09F.2060409@riverviewtech.net> (raw)
In-Reply-To: <003801c566bb$62a1de20$7c66e4a0@supelec.fr>
> iptables -A INPUT -i lo -m state --state NEW -j ACCEPT
> iptables -A OUTPUT -o lo -m state --state NEW -j ACCEPT
If your firewall has a policy of DROP for any traffic that is not explicitly allowed then this rule would not work for any thing other than the first packet. Try using this instead:
iptables -A INPUT -i lo -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o lo -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT
I'm just shooting from the hip here, but that would be my first guess.
Grant. . . .
next prev parent reply other threads:[~2005-06-01 16:21 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 [this message]
2005-06-01 16:46 ` RE : " Thibault Le Meur
2005-06-01 17:45 ` Taylor, Grant
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=429DE09F.2060409@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox