I am setting up a Powerconnect 6248 switch with IPv6. I noticed that the management access-list does not seem to apply to IPv6! The ACL seems to work just fine against IPv4 clients, but when I use the IPv6 address on the switch, it just bypasses them. Is this a bug? Is there a work around?
I thought I would work around the issue by creating an IPv6 ACL and applying the filter to the VLAN, but again I ran into a bit of a roadblock. If I have a IPv4 access group defined, the switch will not allow me to add an IPv6 traffic filter. It is either one or the other.
Currently experiencing the same issue on a PowerConnect 7024. There doesn't seem to be a viable solution to restrict management access to the device's IPv6 addresses without creating an IPv6 ACL including all possible IPv6 address entry points and applying that to all interfaces, an un-wieldy and sub-optimal solution.
Thanks for the response, that was my first avenue but unfortunately there's no IPv6 support under management ACLs. Also supplying an IPv6 address with ip-source is not valid. This seems to be a pretty glaring oversight for a device that supports IPv6 management.
Console(config-macl)#permit ?
Press enter to execute the command.
Gigabitethernet Enter a GigabitEthernet port.
Tengigabitethernet Enter a TenGigabitEthernet port.
mask Specify the source IP address network mask or the
number of bits that comprise the source IP address
Thanks again, I've tried including the vlan and priority and a number of variations but all return the "Error:Invalid IP address." message when using IPv6 addresses.
pemontto
3 Posts
570
0
Posted December 6th, 2012 12:00
Currently experiencing the same issue on a PowerConnect 7024. There doesn't seem to be a viable solution to restrict management access to the device's IPv6 addresses without creating an IPv6 ACL including all possible IPv6 address entry points and applying that to all interfaces, an un-wieldy and sub-optimal solution.