IPv6 => bridged@HWC ?

[e***@gmx.com]

Hi James,

it seems I´ve missed your email. I actually use "***@VLAN" for users
who insist having IPv6 over wlan . So I created an own virtual routing
instance (And no, I will not create ONE big VLAN all over my core and
locations), put in IPv6 adresses, created own "-IPv6" SSIDs,... It´s
ugly and bothers me to create new VNS with different topologies/VLAN
IDs, tag to the next switch/gateway, got extra firewalls to separate
traffic. Man, I started to create another LAN only to support IPv6 over
WLAN....

I just read the CLI guide, too. So it seems, support is already there,
but someone decided to block IPv6 traffic. Does someone know who we
could contact to get another IPv6 enabled firmware?

Michael

Hi Michael,

Well, 8.31 has been released. Unfortunately there´s no sign of
CAPWAP+IPv6 within the release notes :(

Even worse, I read the 8.31 CLI guide and in the filter section on
matching ethernet typees it says "On the controller the Ethertype=IPv6
rule is ignored. The controller always drops IPv6 traffic. The rule is
applied on Bridged At AP topologies."
Has anyone played with the contain2vlan feature yet? The part I'm
curious about is how traffic from that different VLAN gets back to the
client.
Thanks,

---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org