This guide documents the process used to configure a TP-Link Archer NX500 V2 behind a Sky Max Hub while maintaining Internet connectivity over both IPv4 and IPv6.

The important discovery was that the NX500’s normal router configuration successfully obtained IPv4 connectivity, but its WAN-side IPv6 configuration only obtained a private ULA address.

Directly connecting the PC to the Sky Max Hub demonstrated that the Sky connection itself was capable of providing both public IPv4 and public IPv6.

The final configuration uses the Sky Max Hub as the primary router and the NX500 as an access point.

The NX500 was initially tested in its normal Wireless Router configuration.

Initial IPv4 topology

Sky Max Hub
192.168.0.1
│
│ WAN
▼
NX500
WAN: 192.168.0.x
LAN: 192.168.1.1
│
▼
PC
192.168.1.x

IPv4 connectivity was successfully established through this arrangement.

IPv6 problem observed

Although the Sky Max Hub itself possessed public IPv6 connectivity, the NX500 WAN obtained a private ULA address beginning with:

fd31:6f26:5b01:9477::/64

Devices behind the NX500 consequently received ULA addresses rather than the public 2a06: prefix.

Several controlled tests were performed to determine whether the IPv6 problem originated from the Sky connection, Windows, or the NX500.

Direct Sky connection

The PC was connected directly to the Sky Max Hub. This produced a public IPv6 address beginning with:

2a06:5902:2404:5c00:c6:85c:8bf2:9b6c

A temporary public IPv6 address was also assigned:

2a06:5902:2404:5c00:241f:d3ec:eae4:7916

IPv6 Internet connectivity was then confirmed using:

ping -6 google.com

The test returned approximately 7–9 ms replies, confirming working IPv6 connectivity through the Sky Hub.

NX500 WAN IPv6 result

The NX500’s WAN interface repeatedly showed:

IPv6 Address:
fd31:6f26:5b01:9477:1608:5ff:fe2f:4d83
Prefix:
64
Gateway:
fe80::1608:05ff:fe2f:4d80

This is a ULA address and not the public 2a06: prefix obtained directly from Sky.

IPv6 configuration tests

Because the NX500 was not successfully obtaining the required public IPv6 configuration while acting as a router, the configuration was changed so that the Sky Max Hub remained the primary router.

Final physical connection

SKY MAX HUB LAN PORT
│
│ Ethernet
▼
NX500 LAN PORT
NX500 WAN PORT
│
└── NOT USED

MAC address configuration

A custom MAC clone was tested during the router-mode investigation. It did not solve the IPv6 problem.

For the final access-point configuration, the NX500 was returned to its normal/default WAN MAC configuration.

The NX500 LAN IPv6 page contained the following configuration.

Public IP verification

Windows configuration

IPv6 Address:
2a06:5902:2404:5c00:c6:85c:8bf2:9b6c
Temporary IPv6:
2a06:5902:2404:5c00:81e2:f36b:7daa:4712
IPv4:
192.168.0.39
Default Gateway:
fe80::1608:5ff:fe2f:4d80%21
192.168.0.1

IPv4 Internet test

Test-NetConnection 8.8.8.8 -Port 443

The test returned:

TcpTestSucceeded : True

IPv6 Internet test

ping -6 google.com

The test returned four successful replies with approximately 8–9 ms latency and 0% packet loss.

Speed Test

A Speedtest result captured during testing recorded approximately:

Problem: NX500 receives fd31:: instead of 2a06::

When operating as a downstream router, the NX500 received a ULA IPv6 address beginning with fd31:.

Direct connection of the PC to the Sky Hub produced a public 2a06: address, demonstrating that public IPv6 was available from the Sky network.

Problem: LAN IP rejected

When attempting to place the NX500 LAN interface at 192.168.0.254 while its WAN was still connected to the same 192.168.0.x network, the router produced:

Error code: 5718
WAN DNS cannot be on the same subnet with the LAN IP.

The solution was to disconnect the active WAN Internet connection before converting the device into the LAN-to-LAN access-point configuration.

Problem: IPv4 does not work

Check that the Ethernet connection is:

Sky LAN
↓
NX500 LAN
NOT:
Sky LAN
↓
NX500 WAN

In access-point mode, the Sky Hub should be the device providing DHCP and the default gateway.

Problem: NX500 management page cannot be opened

The final management address is:

http://192.168.0.254

Make sure the PC has received a 192.168.0.x address from the Sky Hub.

Problem: Public IPv6 disappears

Check:

The key finding from this configuration was that the Sky Max Hub already provided working IPv4 and public IPv6 connectivity.

The difficulty occurred when the Archer NX500 V2 was placed behind the Sky Hub as a second router. IPv4 could be established, but the NX500’s WAN IPv6 configuration did not obtain the same public IPv6 delegation available directly from the Sky Hub.

Converting the NX500 into a LAN-to-LAN access point allowed the Sky Max Hub to remain the network’s routing authority. The NX500 could then provide additional Ethernet and wireless connectivity without attempting to perform a second layer of IPv6 routing.