All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Schaaf <bof@bof.de>
To: Jay Schulist <jschlst@linux-sna.org>
Cc: Harald Welte <laforge@gnumonks.org>,
	netfilter-devel@lists.netfilter.org,
	netfilter@lists.netfilter.org
Subject: Re: [PATCH] multiple devices with ranges match support
Date: Thu, 19 Sep 2002 00:02:57 +0200	[thread overview]
Message-ID: <20020918220257.GF10465@oknodo.bof.de> (raw)
In-Reply-To: <Pine.LNX.4.44L.0209172347190.10390-102000@hunger.screamingdaemon.com>

On Tue, Sep 17, 2002 at 11:47:42PM -0700, Jay Schulist wrote:
> Hello Harald,
> Here is a new match which allows the user to match by using multiple comma
> seperated devices each with range support.
> 
> Iptables userspace patch is against a clean iptables-1.2.7a
> Kernel patch is against a clean linux-2.4.19
> 
> mdev v1.2.7a options:
>  --i dev[,dev:dev,dev...]       match inbound device(s)
>  --o dev[,dev:dev,dev...]       match outbound device(s)

Wishlist item:

In the future, I wish the indev/outdev were gone from the generic
iptables rule, replaced with exactly such a match as Jay is presenting.
Maybe it could be more "built in", and the old plain "-i" and "-o"
would work without saying "-m mdev", but nevertheless do exactly that
internally. That way we'd have full backward compatibility, and all
those rulesets out there without device matches, would certainly
operate two cache lines (P-III, i.e. 64 byte total) per rule faster.

best regards
  Patrick


  reply	other threads:[~2002-09-18 22:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18  6:47 [PATCH] multiple devices with ranges match support Jay Schulist
2002-09-18  6:47 ` Jay Schulist
2002-09-18 22:02 ` Patrick Schaaf [this message]
2002-09-19  6:47   ` Harald Welte
  -- strict thread matches above, loose matches on Subject: below --
2002-09-18 18:52 Eble, Dan
2002-09-18 22:12 ` Patrick Schaaf
2002-09-18 10:35   ` Jay Schulist
2002-09-20 15:07   ` Harald Welte
2002-10-01  8:57 ` Roberto Nibali
2002-09-18  5:20 Jay Schulist
2002-09-18  5:20 ` Jay Schulist

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=20020918220257.GF10465@oknodo.bof.de \
    --to=bof@bof.de \
    --cc=jschlst@linux-sna.org \
    --cc=laforge@gnumonks.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@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.