From: Phil Oester <kernel@linuxace.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: Greg KH <gregkh@suse.de>,
gcoady@gmail.com, netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
stable@kernel.org
Subject: Re: Linux 2.6.14.5
Date: Mon, 26 Dec 2005 22:07:14 -0800 [thread overview]
Message-ID: <20051227060714.GA1053@linuxace.com> (raw)
In-Reply-To: <20051227054519.GA14609@alpha.home.local>
On Tue, Dec 27, 2005 at 06:45:19AM +0100, Willy Tarreau wrote:
> On Tue, Dec 27, 2005 at 04:42:00PM +1100, Grant Coady wrote:
> > + iptables -A INPUT -p all --match state --state ESTABLISHED,RELATED -j ACCEPT
> > iptables: No chain/target/match by that name
>
> So it's not only the NEW state, it's every "--match state".
Odd...works fine here
# uname -r
2.6.14.5
# iptables -nL | grep state
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
logdrop tcp -- 0.0.0.0/0 0.0.0.0/0 tcp flags:!0x17/0x02 state NEW
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
Phil
WARNING: multiple messages have this Message-ID (diff)
From: Phil Oester <kernel@linuxace.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: gcoady@gmail.com, netfilter-devel@lists.netfilter.org,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
stable@kernel.org
Subject: Re: Linux 2.6.14.5
Date: Mon, 26 Dec 2005 22:07:14 -0800 [thread overview]
Message-ID: <20051227060714.GA1053@linuxace.com> (raw)
In-Reply-To: <20051227054519.GA14609@alpha.home.local>
On Tue, Dec 27, 2005 at 06:45:19AM +0100, Willy Tarreau wrote:
> On Tue, Dec 27, 2005 at 04:42:00PM +1100, Grant Coady wrote:
> > + iptables -A INPUT -p all --match state --state ESTABLISHED,RELATED -j ACCEPT
> > iptables: No chain/target/match by that name
>
> So it's not only the NEW state, it's every "--match state".
Odd...works fine here
# uname -r
2.6.14.5
# iptables -nL | grep state
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
logdrop tcp -- 0.0.0.0/0 0.0.0.0/0 tcp flags:!0x17/0x02 state NEW
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
Phil
next prev parent reply other threads:[~2005-12-27 6:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 0:53 Linux 2.6.14.5 Greg KH
2005-12-27 0:54 ` Greg KH
2005-12-27 3:06 ` Grant Coady
2005-12-27 3:33 ` David S. Miller
2005-12-27 20:01 ` Grant Coady
2005-12-27 20:40 ` Gene Heskett
2005-12-28 8:02 ` Denis Vlasenko
2005-12-28 15:51 ` Lee Revell
2005-12-27 3:46 ` [stable] " Greg KH
2005-12-27 5:28 ` Grant Coady
2005-12-27 4:48 ` Patrick McHardy
2005-12-27 4:48 ` Patrick McHardy
2005-12-27 5:45 ` Grant Coady
2005-12-27 5:17 ` Willy Tarreau
2005-12-27 5:42 ` Grant Coady
2005-12-27 5:45 ` Willy Tarreau
2005-12-27 5:45 ` Willy Tarreau
2005-12-27 5:59 ` Grant Coady
2005-12-27 6:07 ` Phil Oester [this message]
2005-12-27 6:07 ` Phil Oester
2005-12-27 6:41 ` Yasuyuki KOZAKAI
2005-12-27 6:41 ` Yasuyuki KOZAKAI
2005-12-27 6:51 ` Grant Coady
[not found] ` <200512270641.jBR6f6vt024777@toshiba.co.jp>
2005-12-27 6:58 ` Willy Tarreau
2005-12-27 6:58 ` Willy Tarreau
2005-12-27 7:12 ` Yasuyuki KOZAKAI
2005-12-27 7:12 ` Yasuyuki KOZAKAI
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=20051227060714.GA1053@linuxace.com \
--to=kernel@linuxace.com \
--cc=gcoady@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.org \
--cc=willy@w.ods.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.