Re: ipset support in tc

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




3.6. hash:net,iface produces no matches
Still doesn't work. No matches are produced.

Hmm. The device is 'ifb0', not 'ethX'.  Should the ipset ematch
unconditionally set the inbound device to the real interface instead?

What do you think?
Hmm, never thought of that, but using the real interface (eth0 in my case) instead of ifb0 makes more sense, because in order to utilise the same set, which I would presumably use elsewhere, I need the real interface (i.e. eth0). Otherwise, just for tc matching I have to create a separate set and that would prove a real nightmare to maintain.

So, in short, I am for the inclusion/usage of the real interface (eth0) for the above reason...
--
To unsubscribe from this list: send the line "unsubscribe lartc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux