From: Patrick McHardy <kaber@trash.net>
To: devel@openvz.org
Cc: netfilter-devel@vger.kernel.org, johnpeng <johnpeng@unitytek.com.tw>
Subject: Re: [NETFILTER]: Unable to delete a SAME rule (Using SAME target problems)
Date: Tue, 13 Nov 2007 16:37:20 +0100 [thread overview]
Message-ID: <4739C4B0.9070009@trash.net> (raw)
In-Reply-To: <47399B38.8090805@sw.ru>
Konstantin Khorenko wrote:
> Dear all,
>
> The problem description: unable to delete a SAME target rule.
>
> [...]
> At the moment i can see only 3 ways of fixing this:
> * reassemble struct ipt_same_info - put 'ipnum' and 'iparray' at the end of the
> structure. This will save generic code both in kernel and userspace.
>
> * let struct ipt_same_info be as is, teach userspace to manipulate more complex
> masks (not only first X bytes of the structure)
>
> * let struct ipt_same_info be as is, teach kernel to zero pointers and all the
> fields which are used only in kernel.
>
> All these ways are quite painful, but could someone please comment this - may
> be i just missed and some decision had been already done on this issue?
Actually yes, thats why haven't got compat support for SAME yet.
Because of these issues and since SAME is obsolete nowadays I've
decided to put it on feature-removal-schedule instead of trying
to work around the problems, it will be removed at 1.1.08:
What: iptables SAME target
When: 1.1. 2008
Files: net/ipv4/netfilter/ipt_SAME.c,
include/linux/netfilter_ipv4/ipt_SAME.h
Why: Obsolete for multiple years now, NAT core provides the same
behaviour.
Unfixable broken wrt. 32/64 bit cleanness.
Who: Patrick McHardy <kaber@trash.net>
prev parent reply other threads:[~2007-11-13 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 12:40 [NETFILTER]: Unable to delete a SAME rule (Using SAME target problems) Konstantin Khorenko
2007-11-13 15:37 ` Patrick McHardy [this message]
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=4739C4B0.9070009@trash.net \
--to=kaber@trash.net \
--cc=devel@openvz.org \
--cc=johnpeng@unitytek.com.tw \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).