Possible bug in Zyxel XMG1915-18EP

dan_a

When setting System→IPv6→IPv6 Addressing→IPv6 Default Gateway I cannot use a ULA (I get an error about the address) or an LLA. It accepts the LLA address in the UI for IPv^ Default Gateway, but it ends up corrupt (discovered via the console with show ipv6 route). Only a factory reset and cold boot would recover it.

Zyxel_Tina

Hi @dan_a,

Thank you for providing the file!

First, we'd like to confirm with you that we cannot locate the next hop address "::ea60:874d:8d4:0:0" shown in your screenshot within the provided tech support file.

Therefore, we would like to clarify whether the information displayed in the screenshot appeared after you configured the LLA address in the IPv6 Default Gateway (as you mentioned: "It accepts the LLA address in the UI for IPv6 Default Gateway, but...")?

If possible, could you please provide the specific LLA address you used at that time? This will help us better understand the situation.

Thank you for your assistance.

Zyxel_Tina

Hi @dan_a,

You mentioned "discovered via the console with show ipv6 route". Is it the same as the information you provided in the picture (IPv6 Routing Table) before?

In addition, please collect the Tech-support Info and send it to us via private message. You may refer to the article below to see how to collect it.

https://community.zyxel.com/en/discussion/21237/switch-how-to-collect-the-tech-support-info-on-v4-80-firmware-version-and-newer

dan_a

Yes, it was the same as the picture shown. I will collect the information for you. Thank you.

Zyxel_Tina

Hi @dan_a,

Thank you for providing the file!

First, we'd like to confirm with you that we cannot locate the next hop address "::ea60:874d:8d4:0:0" shown in your screenshot within the provided tech support file.

Therefore, we would like to clarify whether the information displayed in the screenshot appeared after you configured the LLA address in the IPv6 Default Gateway (as you mentioned: "It accepts the LLA address in the UI for IPv6 Default Gateway, but...")?

If possible, could you please provide the specific LLA address you used at that time? This will help us better understand the situation.

Thank you for your assistance.

dan_a

The address shown in the screenshot (::ea60:874d:8d4:0:0) is the corrupt entry and is not valid on my network.

The LLA address I entered was fe80::da58:d7ff:fe02:6131 and I think it displayed correctly initially and wasn't until went back later and looked that it was corrrupt.