What vendor/models out there do support today protocol-based vlans?
That is if host connected to int1 on the switch send in an untagged frame of ethertype IPv4 (0x0800) or ARP (0x0806) then it should lets say go into vlan100.
But if the same host sends to int1 an untagged frame of ethertype IPv6 (0x86DD) that should go into vlan101.
At the same time I want that host at int2 for IPv4 and ARP ends up at vlan100 (same as above) but for IPv6 it will go into vlan102 (which isnt as above).
This way for IPv4 I have a single vlan (using protected vlan to segment hosts from each other) while for IPv6 they are each in their own VLAN.
Like so:
IPv4+ARP: vlan100, protected vlan, untagged int 1-48, tagged uplink 49-50. IPv6: vlan101, untagged int1, tagged uplink 49-50 vlan102, untagged int2, tagged uplink 49-50 ... vlan148, untagged int48, tagged uplink 49-50
I do know that this works very well for HPE Comware5 and Comware7 devices - but what about the others (specially now when HPE is throwing both Comware5 and Comware7 under the bus as it seems)?
Googling on the subject this doesnt seem to be too common to have as a feature and some of those who seem to have this (Netgear, Zyxel, Cisco) only seem to do this as a global option.
Like everything IPv4+ARP goes into vlan100 and everything IPv6 goes into vlan200. But as I explained with the above example for IPv6 I want this to be per physical interface (so int1 IPv6 goes into vlan101 and int48 IPv6 goes into vlan148).
Then its the dist-router in my case who have the ip addresses (default gateway for the hosts) configured along with routing for each vlan.
No comments:
Post a Comment