All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: netfilter-devel@lists.netfilter.org,
	Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH] Unspecified proto should print as "all" in iptables -L
Date: Mon, 30 Apr 2007 10:36:54 -0700	[thread overview]
Message-ID: <20070430173654.GB6904@linuxace.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0704301924021.29151@yvahk01.tjqt.qr>

On Mon, Apr 30, 2007 at 07:25:17PM +0200, Jan Engelhardt wrote:
> On Apr 30 2007 10:13, Phil Oester wrote:
> >On Mon, Apr 30, 2007 at 10:38:38AM +0200, Jan Engelhardt wrote:
> >> Hey btw, how would you go about matching protocol 0 since 0 is unfortunately
> >> defined as "all" in iptables?
> >
> >I suppose you wouldn't, although AFAIK protocol 0 isn't actively
> >used.  Have you seen it used in the wild?
> 
> /etc/protocols lists ipv6hopbyhop as 0.
> But also see
> http://lists.netfilter.org/pipermail/netfilter/2007-April/068496.html

That is indeed unfortunate, but at this point we can't change the
meaning of this within iptables without potentially breaking compatibility
with existing rulesets.  Perhaps someone is using a rule such as this:

    -p 0 -j DROP

to drop all traffic to a box.  If we changed it, now it would only block
protocol 0.

Sure, far-fetched, but I think our hands are tied to the current definition.

Phil

  reply	other threads:[~2007-04-30 17:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28 22:02 [PATCH] Unspecified proto should print as "all" in iptables -L Phil Oester
2007-04-29 23:06 ` Pablo Neira Ayuso
2007-04-30  8:38   ` Jan Engelhardt
2007-04-30 17:13     ` Phil Oester
2007-04-30 17:25       ` Jan Engelhardt
2007-04-30 17:36         ` Phil Oester [this message]
2007-04-30 18:17           ` Jorge Davila
2007-04-30 20:09             ` Phil Oester
2007-05-03 16:16               ` Jorge Davila
2007-05-03 16:33                 ` Carl-Daniel Hailfinger
2007-05-03 17:31                   ` Phil Oester
2007-05-03 17:45                     ` Carl-Daniel Hailfinger
2007-06-02 18:49           ` How to match protocol 0 Jan Engelhardt
2007-06-02 21:19             ` Jan Engelhardt

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=20070430173654.GB6904@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@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.