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
| ||
|
Date: Fri, 23 Jan 2015 07:42:44 -0800 From: roopa <roopa@...ulusnetworks.com> To: Stephen Hemminger <stephen@...workplumber.org> CC: davem@...emloft.net, netdev@...r.kernel.org, vyasevic@...hat.com, wkok@...ulusnetworks.com, sfeldma@...il.com Subject: Re: [PATCH net-next v2] iproute2: bridge: support vlan range On 1/22/15, 10:51 PM, Stephen Hemminger wrote: > On Thu, 22 Jan 2015 22:25:10 -0800 > roopa@...ulusnetworks.com wrote: > >> From: Roopa Prabhu <roopa@...ulusnetworks.com> >> >> This patch adds vlan range support to bridge command >> using the newly added vinfo flags BRIDGE_VLAN_INFO_RANGE_BEGIN and >> BRIDGE_VLAN_INFO_RANGE_END. >> >> $bridge vlan show >> port vlan ids >> br0 1 PVID Egress Untagged >> >> dummy0 1 PVID Egress Untagged >> >> $bridge vlan add vid 10-15 dev dummy0 >> port vlan ids >> br0 1 PVID Egress Untagged >> >> dummy0 1 PVID Egress Untagged >> 10 >> 11 >> 12 >> 13 >> 14 >> 15 > Doing on vlan id per line gets ridiculous with 1000 vlan's > how about something more compact? yes, I was going to do that in a separate patch ...the kernel can dump in ranges with the new flag. I did not want to change default (current) show to print ranges. Was planning on submitting a new patch with a new option. If you think there are not many users out there today.. ..and no fear of breaking users, i will include it in the current patch in v3. thanks. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists