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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 23 Mar 2022 10:44:45 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Boris Sukholitko <boris.sukholitko@...adcom.com> Cc: netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>, Jamal Hadi Salim <jhs@...atatu.com>, Cong Wang <xiyou.wangcong@...il.com>, Jiri Pirko <jiri@...nulli.us>, "Gustavo A . R . Silva" <gustavoars@...nel.org>, Vladimir Oltean <vladimir.oltean@....com>, Eric Dumazet <edumazet@...gle.com>, zhang kai <zhangkaiheb@....com>, Yoshiki Komachi <komachi.yoshiki@...il.com>, Ilya Lifshits <ilya.lifshits@...adcom.com> Subject: Re: [PATCH net-next 0/5] flower: match on the number of vlan tags On Wed, 23 Mar 2022 12:55:57 +0200 Boris Sukholitko wrote: > Our customers in the fiber telecom world have network configurations > where they would like to control their traffic according to the number > of tags appearing in the packet. > > For example, TR247 GPON conformance test suite specification mostly > talks about untagged, single, double tagged packets and gives lax > guidelines on the vlan protocol vs. number of vlan tags. > > This is different from the common IT networks where 802.1Q and 802.1ad > protocols are usually describe single and double tagged packet. GPON > configurations that we work with have arbitrary mix the above protocols > and number of vlan tags in the packet. > > The following patch series implement number of vlans flower filter. They > add num_of_vlans flower filter as an alternative to vlan ethtype protocol > matching. The end result is that the following command becomes possible: > > tc filter add dev eth1 ingress flower \ > num_of_vlans 1 vlan_prio 5 action drop # Form letter - net-next is closed We have already sent the networking pull request for 5.18 and therefore net-next is closed for new drivers, features, code refactoring and optimizations. We are currently accepting bug fixes only. Please repost when net-next reopens after 5.18-rc1 is cut. RFC patches sent for review only are obviously welcome at any time.
Powered by blists - more mailing lists