From: Pablo Neira Ayuso <pablo@eurodev.net>
To: Michal Rokos <michal.rokos@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: x_tables userspace
Date: Mon, 16 Jan 2006 13:38:28 +0100 [thread overview]
Message-ID: <43CB93C4.4060500@eurodev.net> (raw)
In-Reply-To: <333e1ca10601160212g4a9f21e8p78c26fd113197a60@mail.gmail.com>
Michal Rokos wrote:
> now when x_tables are merged one question has to come:
>
> Is there any userspace prog that can manage x_tables? Something like ip46tables?
No, this does not suppose any change from userspace side. It's just part
of the ipv4-ipv6 code reunification.
> (All I really want is to finally use ipv6 stateful netfilter. And when
> iptables and ip6tables are already merged somewhere it would be
> great!)
Stateful ipv6 went into 2.6.15, so you can give it a try in this -rc1.
Just check the following boxes:
Network packet filtering (replaces ipchains) ---> Core Netfilter
Configuration ---> Layer 3 Independent Connection tracking (EXPERIMENTAL)
And then add support for IPv4 and IPv6:
Network packet filtering (replaces ipchains) ---> IP: Netfilter
Configuration ---> IPv4 support for new connection tracking (EXPERIMENTAL)
Network packet filtering (replaces ipchains) ---> IPv6: Netfilter
Configuration (EXPERIMENTAL) ---> IPv6 support for new connection
tracking (EXPERIMENTAL)
Previously, don't forget to uncheck the old connection tracking support.
Otherwise the IPv6 support won't be available.
--
Pablo
next prev parent reply other threads:[~2006-01-16 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 10:12 x_tables userspace Michal Rokos
2006-01-16 12:38 ` Pablo Neira Ayuso [this message]
2006-01-16 13:25 ` Krzysztof Oledzki
2006-01-16 20:08 ` Michal Rokos
2006-01-17 2:06 ` YOSHIFUJI Hideaki / 吉藤英明
2006-01-16 20:01 ` Michal Rokos
2006-01-21 14:48 ` Harald Welte
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=43CB93C4.4060500@eurodev.net \
--to=pablo@eurodev.net \
--cc=michal.rokos@gmail.com \
--cc=netfilter-devel@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.