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.
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
