search for: vlan99

...e to routing table 1. The first route applies but the other ones not. If i try to add the routes manually to routing table 1 i have to add the first fe80::/64 route and append not add the other ones. does not work: ip -6 route add table 1 fe80::/64 dev vlan42 ip -6 route add table 1 fe80::/64 dev vlan99 works: ip -6 route add table 1 fe80::/64 dev vlan42 ip -6 route append table 1 fe80::/64 dev vlan99 Configuration files and error message below. /etc/shorewall6/interfaces net eth2 detect mss=1280 loc eth0 detect mss=1280 admin vlan42 detect mss=1280 mgmt vlan99 detect mss=1280 /etc/shore...

...to do the right thing for PV and HVM guests (including tap devices) and with stubdomains. In order to support VLAN tagging and trunking the "bridge" specified in the configuration can have a special syntax, that is: BRIDGE_NAME[.VLAN][:TRUNK,TRUNK] e.g. - xenbr0.99 add the VIF to VLAN99 on xenbr0 - xenbr0:99,100,101 add the VIF to xenbr0 as a trunk port receiving VLANs 99, 100 & 101 Waldi, can you confirm if I have correctly reverse engineered the syntax from the regexp please ;-) Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: waldi@debian.org --- tool...

I just realized that I hadn''t actually asked a question when I posted this before. Let me try again... I am trying to configure a Linux box with all possible VLANs (4094 of them), and a subnet on each VLAN. Creating the VLANs isn''t a problem. But, when I try to use "ip addr add ..." commands to assign an IP address to each VLAN interface, I get to do about 280 of