Laszlo Attila Toth wrote:
Patrick McHardy írta:
Laszlo Attila Toth wrote:
The only reason why it can't be set to zero again seems to
be this part from the iproute patch:
+if (rtnl_ifgroup_a2n(&group, *argv) || group == 0)
Why don't you allow a value of zero?
It has historical
Patrick McHardy írta:
Laszlo Attila Toth wrote:
Hello,
Here is the new version of ifgroup patches.
The interface group value is u_int32_t in net_device which should be
enough.
Previously it was an int.
Usage:
ip link set eth0 group 4
but currently it cannot be unset, only changed to anot
Laszlo Attila Toth wrote:
Hello,
Here is the new version of ifgroup patches.
The interface group value is u_int32_t in net_device which should be enough.
Previously it was an int.
Usage:
ip link set eth0 group 4
but currently it cannot be unset, only changed to another value.
The only re
Hello,
Here is the new version of ifgroup patches.
The interface group value is u_int32_t in net_device which should be enough.
Previously it was an int.
Usage:
ip link set eth0 group 4
but currently it cannot be unset, only changed to another value.
In /etc/iproute2/rt_ifgroup each value ma
Philip Craig írta:
Laszlo Attila Toth wrote:
Hello,
Different network interfaces can be grouped using the same group ID. With this
patch fewer netfilter rules are necessary but it may also be used by routing.
This allows an interface to belong to only one group. I expect there are
situations
Laszlo Attila Toth wrote:
> Hello,
>
> Different network interfaces can be grouped using the same group ID. With this
> patch fewer netfilter rules are necessary but it may also be used by routing.
This allows an interface to belong to only one group. I expect there are
situations where you want
Hello,
Different network interfaces can be grouped using the same group ID. With this
patch fewer netfilter rules are necessary but it may also be used by routing.
The interface group (ifgroup) member of the net_device can be modified via
netlink (with iproute2) and it is used in the new 'ifgroup
