From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Changli Gao <xiaosuo@gmail.com>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] libxtables: change option precedence order to be intuitive
Date: Mon, 15 Nov 2010 11:38:02 +0100 [thread overview]
Message-ID: <4CE10D8A.1090102@trash.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1010291458200.3755@obet.zrqbmnf.qr>
On 29.10.2010 14:59, Jan Engelhardt wrote:
> On Friday 2010-10-29 07:26, Changli Gao wrote:
>>>>>
>>>>>> When using `-m mark --mark 2 -m connmark --mark 2`, the user currently
>>>>>> gets an error about the (libxt_mark) --mark option being used twice.
>>>>>> This is because libxt_connmark's option table does not override any
>>>>>> previous options. This patch changes this behavior, since the current
>>>>>> behavior does not allow connmark's option to be used at all, which is
>>>>>> illogical.
>>>>>
>>>>> As per fw's suggestion, I should nag you every 48 hours ;-)
>>>>>
>>>>> Really, this should be in the next tag.
>>>>
>>>> This stuff is pretty fragile and whenever we changed it, something broke
>>>> for users. Why not simply add new options (--connmark etc). That would
>>>> also be more consistent with the other extensions.
Something very non-intuitive is happening with this patch:
# iptables -A OUTPUT -p tcp --dport 10000
iptables v1.4.9: host/network `port' not found
Try `iptables -h' or 'iptables --help' for more information.
port is interpreted as parameter to '-d'. I'm reverting this for
now, please resend if you can come up with a way to fix this.
next prev parent reply other threads:[~2010-11-15 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 15:16 iptables: option precedence order change Jan Engelhardt
2010-10-19 15:16 ` [PATCH] libxtables: change option precedence order to be intuitive Jan Engelhardt
2010-10-25 21:57 ` Jan Engelhardt
2010-10-28 9:54 ` Patrick McHardy
2010-10-28 10:54 ` Jan Engelhardt
2010-10-29 5:26 ` Changli Gao
2010-10-29 12:59 ` Jan Engelhardt
2010-10-29 17:04 ` Patrick McHardy
2010-11-15 10:38 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-15 12:28 Jan Engelhardt
2010-11-15 12:56 ` Patrick McHardy
2010-11-15 13:13 ` Jan Engelhardt
2010-11-15 13:15 ` Patrick McHardy
2010-11-15 13:41 ` Jan Engelhardt
2010-11-15 13:46 ` Patrick McHardy
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=4CE10D8A.1090102@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=xiaosuo@gmail.com \
/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.