WS-10-AC-250 IPv6

[StefanN]

Hi, I need some assistance as I am very new to these devices.
Sitting with a situation that the a functioning IPv6 link no-longer passes traffic since the Switch was installed, not even point-to-point reachability.
On IPv4 all works 100%, no problems.

IPv6 also moved to different end devices, still going across the switch. Same story, IPv4 works fine, IPv6 not.


Please advise if there are any known issues? Specific settings, Features that need to be active or if it might possibly be Firmware related?

Many thanks
Stefan

[StefanN]

Hi,

Will it be advisable to perform a Firmware Upgrade to the latest version, to try and resolve the IPv6 issue?

Thanks again,
S

[sirhc]

You should ALWAYS upgrade to the latest firmware and see if the problem still exists before reporting a suspected issue.

Current version in development is v1.5.1rc1, v1.5.0 is closed and no longer being developed.

We tested ipv6 in the LAB but I do not use ipv6 at my WISP so I can not confirm it works in the real world, hoping someone else weighs in with real life experience.

[mducharme]

We are rolling out IPv6 now. On firmware version 1.5.0 IPv6 is working *except* the web server appears to not be listening on IPv6. It is possible to ping the switch and connect via SSH but the web management is not working. It passes IPv6 traffic just fine to other devices, but I am forced to keep IPv4 routed there for management to keep the web interface working on the Netonix. I would prefer that this was fixed so that we can remove IPv4 from our management subnets.

[mducharme]

Update: SNMP also does not work on the IPv6 address of the netonix. Only ping and SSH work.

[sirhc]

We are rolling out IPv6 now. On firmware version 1.5.0 IPv6 is working *except* the web server appears to not be listening on IPv6. It is possible to ping the switch and connect via SSH but the web management is not working. It passes IPv6 traffic just fine to other devices, but I am forced to keep IPv4 routed there for management to keep the web interface working on the Netonix. I would prefer that this was fixed so that we can remove IPv4 from our management subnets.

Did you assign the switch an IPv6 address under the Device/Configuration TAB?

[mducharme]

Did you assign the switch an IPv6 address under the Device/Configuration TAB?

No. We are using SLAAC for all devices (automatic IP address). They are basically static anyway, and allow us to move devices to new subnets without having to touch them. We have the switch set on "DHCP" since it didn't seem to have a "SLAAC" option, it gets a SLAAC address with the DHCP option and we can SSH it and ping it but no HTTPS/HTTP and no SNMP.

[mducharme]

Did you assign the switch an IPv6 address under the Device/Configuration TAB?

The other strange thing is that the switch reports through CDP that it doesn't support IPv6 and doesn't provide an IPv6 address. Yet you can ping it and SSH into it with IPv6.


Seeing the IPv6 address in CDP is very helpful, especially when using SLAAC.

EDIT: Also, the firmware version being reported through CDP is 1.4.7, even though the unit has been upgraded to 1.5.0?

[StefanN]

Thanks so much for the insights and guidance. Will arrange for an Update on the Firmware and then provide feedback.

Thanks again...

Stefan

[mducharme]

Hi @sirhc,

We are trying to move our management networks to IPv6 only. The Netonix switch is one of the last components of that. If we could get SNMP working and the web interface working we would be set. Any chance of getting those fixed?