From: "Hervé Eychenne" <rv@wallfire.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: iptables-save saves invalid negative --uid-owner expressions.
Date: Mon, 6 Jan 2003 03:02:19 +0100 [thread overview]
Message-ID: <20030106020219.GC423@comet.rv-int> (raw)
In-Reply-To: <35565.195.97.5.193.1041816667.squirrel@fs.tsaousis.gr>
On Mon, Jan 06, 2003 at 03:31:07AM +0200, Costa Tsaousis wrote:
Hi,
> I believe I have faced another, not-mentioned-in-2002, bug:
> [...]
> then iptables-save gives this:
>
> -A OUTPUT -d ! 127.0.0.1 -p tcp -m owner --uid-owner !squid -m tcp --dport
> 80 -j DNAT --to-destination 127.0.0.1:3128
>
> which produces a "user '!squid' not found" error when restored.
It seems to me that no single week passes without any post about this
kind of error (no space before a negation) in some save output module.
Sigh.
I must admit it seems quite strange to me that noone in the coreteam
didn't do that already. (hope I won't hurt anybody's feelings too
much though) ;-)
Would someone who's even more fed up than me with these recurrent
messages have time to audit the whole bunch of existing modules in
the CVS tree and fix this particular kind of problem _once and for all_?
Thanks in advance,
Herve
--
_
(°= Hervé Eychenne
//)
v_/_ WallFire project: http://www.wallfire.org/
next prev parent reply other threads:[~2003-01-06 2:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 1:31 iptables-save saves invalid negative --uid-owner expressions Costa Tsaousis
2003-01-06 2:02 ` Hervé Eychenne [this message]
2003-01-06 8:07 ` Bart De Schuymer
2003-01-06 8:15 ` [PATCH]: fix all iptables problems with "!" (hopefully) Patrick McHardy
2003-01-06 12:29 ` [PATCH]: fix all iptables problems with '!' (hopefully) Costa Tsaousis
2003-01-06 15:33 ` Patrick McHardy
2003-01-07 17:15 ` Harald Welte
2003-01-07 18:53 ` Patrick McHardy
2003-01-07 20:16 ` Harald Welte
2003-01-08 18:37 ` Patrick McHardy
2003-01-06 12:34 ` iptables-save saves invalid negative --uid-owner expressions 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=20030106020219.GC423@comet.rv-int \
--to=rv@wallfire.org \
--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.