AP6 420 and IPv6 addressing

Hi folks,

I installed my AP6 420 today, local installation because for AP6s I am a home user.

The AP6 420 picks up IP4 addresses without any issues. IPv6 addressing appears to be a bit random, so far my AP6 has picked 3 IPv6 addresses using a different MAC address to what is shown on the AP6 420 case.

I resolved the issue by statically assigning the IP6 address in the AP6.

While most dynamic IPv6 addressing devices will pickup two addresses with a consistent MAC address. The IPv6 address management in the XG is still very limited while yes, the logviewer does show assigned addresses so should the DHCP tab in the networks on the GUI.

I consider the multiple address assignment a bug in the AP6 because you can only see one address in the AP6 GUI.

Yes, as a home user I will not see a firmware update to my AP6 420, but others might benefit from the fix when and if offered.

Ian



Added TAGs
[edited by: Raphael Alganes at 5:18 AM (GMT -7) on 1 Aug 2024]
  • This is weirdly like what I noticed over the years with Apple's AppleTV: it would present multiple MAC addresses to get multiple DHCP IP addresses. I definitely saw it with IPv4 and perhaps it was their unacknowledged hack to get multiple IPv4 IPs so they could use similar core logic for IPv4 or IPv6. Doesn't address your issue, but it's weird that devices from totally different manufacturers would do the multiple-MAC thing.

  • My AppleTV does the same thing. The issue with the AppleTV was triggered when I went from wifi to LAN. I suspect I would have reset the AppleTV to stop the issue.

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v20.0.2 MR-2

    If a post solves your question please use the 'Verify Answer' button.

  • My AopleTV has done this through multiple generations and only over WiFi -- I've never plugged an ethernet cable into it. So I'm positive that it is the AppleTV presenting multiple MAC addresses. I think it's also tied in to when it is the HomeKit hub and I think it does this to create IPs that it uses on behalf of other (sleeping?) Homekit devices.