netdev - Feature Request : iface may be allowed as datatype in all ipset

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAA5aLPgHYCxwMCObDY6pw85Y5CP7WCbFvBbc05KXAqgN4GG-Cw@mail.gmail.com>
Date:   Wed, 30 May 2018 15:33:07 +0530
From:   Akshat Kakkar <akshat.1984@...il.com>
To:     netdev <netdev@...r.kernel.org>
Subject: Feature Request : iface may be allowed as datatype in all ipset

Is there a reason why iface is allowed to be paired only with net to
create an ipset?

I think with feature of skbinfo in every ipset, it should be allowed
to add iface in all ipset. As skbinfo can store tc classes, it might
make more sense if I can pin point on which outgoing interface this
class should be applied.

One direct way of doing could be adding iface in skbinfo itself, but I
dont think its a good suggestion.

So, other thing left is to have ipset storing interface too. Besides,
when I create a tc class, I create it on a known interface, so I know
beforehand on which interface this class is created. So I can easily
specify while adding entry in ipset.