netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>,
	netfilter-devel@vger.kernel.org, linux-netdev@vger.kernel.org
Subject: Re: [PATCHv6 0/3] Interface group patches
Date: Fri, 23 Nov 2007 01:41:43 +0100	[thread overview]
Message-ID: <474621C7.7040807@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711230120560.11776@bizon.gios.gov.pl>

Krzysztof Oledzki wrote:
> 
> 
> On Fri, 23 Nov 2007, Patrick McHardy wrote:
> 
>> Wolfgang Walter wrote:
>>> From: Patrick McHardy
>>>> I'm working on the incremental ruleset changing API BTW :)
>>>> One of the changes will be that interface matching is not
>>>> a default part of every rule, and without wildcards it will
>>>> use the ifindex. But since the cost of this feature seems
>>>> pretty low, I don't see a compelling reason against it.
>>>
>>> Using ifindex instead of string matching the interface name in -i and 
>>> -o would be a serious problem as it changes the semantics.
>>>
>>> 1) Now you can match a non existing interface. This is certainly 
>>> used. I.e. with vlan interfaces, ppp etc.
>>> 2) Now your rule will match an interface even if the ifindex of the 
>>> interface changes. This is used (i.e. you activate a backup interface 
>>> and rename it, build new bridges etc.).
>>>
>>> If one wants to use the ifindex instead of a string match on the name 
>>> one should explicitly request that (i.e. by using "-i =eth0" or 
>>> something like that).
>>
>>
>> Don't worry, it will subscribe to netdevice events and adjust the
>> ifindex when necessary. For userspace its still a device name match.
> 
> Also for "-i ppp+"?


No, see above :) Its a single device match, for wildcards it will
still use the pattern-based matching.

  reply	other threads:[~2007-11-23  0:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-22 14:37 [PATCHv6 0/3] Interface group patches Wolfgang Walter
2007-11-23  0:10 ` Patrick McHardy
2007-11-23  0:21   ` Krzysztof Oledzki
2007-11-23  0:41     ` Patrick McHardy [this message]
2007-11-23  0:56       ` Krzysztof Oledzki
  -- strict thread matches above, loose matches on Subject: below --
2007-11-20 13:14 Laszlo Attila Toth
2007-11-20 13:26 ` Jan Engelhardt
2007-11-20 13:52   ` Laszlo Attila Toth
2007-11-20 21:42     ` David Miller
2007-11-21  0:25       ` Patrick McHardy
2007-11-21  1:17         ` David Miller
2007-11-22  9:05           ` Laszlo Attila Toth
2007-11-21 15:56         ` Balazs Scheidler

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=474621C7.7040807@trash.net \
    --to=kaber@trash.net \
    --cc=linux-netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=ole@ans.pl \
    --cc=wolfgang.walter@studentenwerk.mhn.de \
    /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).