From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Cc: FiloSottile <filosottile.wiki@gmail.com>
Subject: Re: Iptables without ipt_state using xt_state
Date: Tue, 12 Jan 2010 19:36:32 +0100 [thread overview]
Message-ID: <4B4CC130.40204@chello.at> (raw)
In-Reply-To: <4B4CB29D.9000506@gmail.com>
On 12.01.2010 18:34, FiloSottile wrote:
> I am running on a OpenVZ box with static unmodifiable kernel.
> I have no ipt_state and ipt_connmark but i have xt_state and xt_connmark.
> I want to build a simple firewall, but when i run that:
>
> # iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables: No chain/target/match by that name
>
> How to use xt_state instead ipt_state? Or there is an alternative way to
> build firewall?
> Thank you
>
eris:~# modinfo xt_state
filename:
/lib/modules/2.6.24-etchnhalf.1-686/kernel/net/netfilter/xt_state.ko
license: GPL
author: Rusty Russell <rusty@rustcorp.com.au>
description: ip[6]_tables connection tracking state match module
alias: ipt_state
alias: ip6t_state
vermagic: 2.6.24-etchnhalf.1-686 SMP mod_unload 686
depends: x_tables,nf_conntrack
eris:~# grep -w xt_state /lib/modules/$(uname -r)/modules.alias
alias ipt_state xt_state
alias ip6t_state xt_state
xt_state is the successor of ipt_state.
what does modprobe -v xt_state say?
uname -a?
regards
Mart
next prev parent reply other threads:[~2010-01-12 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 17:34 Iptables without ipt_state using xt_state FiloSottile
2010-01-12 18:36 ` Mart Frauenlob [this message]
2010-01-12 20:42 ` FiloSottile
2010-01-12 22:43 ` Pascal Hambourg
2010-01-13 8:21 ` Patrick McHardy
2010-01-12 23:02 ` /dev/rob0
-- strict thread matches above, loose matches on Subject: below --
2010-01-13 12:50 FiloSottile
2010-01-16 12:34 ` Mart Frauenlob
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=4B4CC130.40204@chello.at \
--to=mart.frauenlob@chello.at \
--cc=filosottile.wiki@gmail.com \
--cc=netfilter@vger.kernel.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.