Hi @JohnXu 

Thanks for posting in our business forum.

By any chance that you can share a screenshot of the v6 config?

And the problem IP on your phone that persists after your WAN v6 has refreshed? With screenshots.

Please mosaic your sensitive information. Here is a list of information considered sensitive:

1. Public IP address on your WAN if your WAN is.

2. Real MAC address of your device.

3. Your personal information including address, domain name, and credentials.

For troubleshooting purposes, when a WAN IP is needed, please leave some values visible for identification.

BTW, the latest firmware is 2.2.6, if you are not on the latest one, try this: https://www.tp-link.com/en/support/download/er605/v2/#Firmware

  @Clive_A 

Yes, i am using the latest firmware

2.2.6 Build 20240718 Rel.82712

WAN setup

LAN setup, i had the issue with SLAAC+stateless DHCP for the prefix update, but now i have changed it to RDNSS.

Since ISP's prefix has not been changed today (will last for a few days i guess), i cannot tell if RDNSS will work or not.

On the win11 side, for example, if ISP change the prefix, you will see four ipv6 addresses, one set (public and temporary) are deprecated, and the new set with the new prefix can be used and working good. On iphone or ipad side, also four ipv6 addresses, but i cannot tell if the old ones are deprecated, don't know how to check in ios. I can only say if I check some ipv6 specific website, it won't open or it will just say your IPV4 address. Any idea what might be wrong here? Thanks.

I suppose RA shall send something to tell the clients that the prefix has changed and any previous IPV6 address becomes invalid or with lifetime set to zero. Looks in windows side, this RA msg is well received, but not on the apple side.

Hi @JohnXu 

Thanks for posting in our business forum.

JohnXu wrote

  @Clive_A 

Yes, i am using the latest firmware

2.2.6 Build 20240718 Rel.82712

 

WAN setup

 

LAN setup, i had the issue with SLAAC+stateless DHCP for the prefix update, but now i have changed it to RDNSS.

Since ISP's prefix has not been changed today (will last for a few days i guess), i cannot tell if RDNSS will work or not.

 

 

On the win11 side, for example, if ISP change the prefix, you will see four ipv6 addresses, one set (public and temporary) are deprecated, and the new set with the new prefix can be used and working good. On iphone or ipad side, also four ipv6 addresses, but i cannot tell if the old ones are deprecated, don't know how to check in ios. I can only say if I check some ipv6 specific website, it won't open or it will just say your IPV4 address. Any idea what might be wrong here? Thanks.

 

I suppose RA shall send something to tell the clients that the prefix has changed and any previous IPV6 address becomes invalid or with lifetime set to zero. Looks in windows side, this RA msg is well received, but not on the apple side.

It could be a compatibility issue if this can behave normally with the Win11, yet it does not work with Apple.

Do you have any chance to try a different one with the same PPPoE with IPv6?

For further analysis on this, I might consult with the test team as soon as they are back.

  @Clive_A 

just to update here. It looks with RDNSS, it's a little better as the prefix can be used without a change for a month, maybe because that's the correct way to config ipv6 from my isp. However, still no luck to expire ipv6 address on apple devices. It won't expire right after the prefix change, but have to wait for about 24 hours. All is good in windows 11.

if the testing team can help to check/verify this, it'll be much appreciated.

Hi @JohnXu 

Thanks for posting in our business forum.

JohnXu wrote

  @Clive_A 

just to update here. It looks with RDNSS, it's a little better as the prefix can be used without a change for a month, maybe because that's the correct way to config ipv6 from my isp. However, still no luck to expire ipv6 address on apple devices. It won't expire right after the prefix change, but have to wait for about 24 hours. All is good in windows 11.

if the testing team can help to check/verify this, it'll be much appreciated.

There is no strong evidence to indicate that this is a problem resides in our product.

As for now, other types of devices work fine but just Apple. And there is no similar feedback in the past.

I highly doubt that this is a problem with Apple. And so does the test team. We discussed what you described earlier.

You can do a simple test by using a different router to verify if this behavior.

If it is possible, we recommend you Wireshark to find out the difference between Apple and Windows. I think there is something wrong with the Apple system about how to renew the IPv6.

At least so far Windows can work okay, which means the IPv6 function in the router is intact. Or the Windows or Android would experience the same thing.

  @Clive_A 

probably you are right it's the issue with apple. But I didn't have issue with my old router which is not tplink.

anyway I have updated my iOS to 18, hope it can help to solve the issue later. 
thanks.