IPv6 Configuration Support with Virtual WAN on ER605 v2.0 (KPN-NL)
I am currently using the TP-Link ER605 v2.0 router in combination with the Omada Controller, connected directly to KPN-NL fiber.
KPN provides both IPv4 and IPv6 connectivity, and I would like to ensure that my network is configured to support public IPv6 addresses alongside IPv4.
To enable IPTV functionality, I followed the official guide titled “How to configure Virtual WAN on Omada Gateway | TP-Link Nederland”.
IPTV is working correctly over IPv4 using VLAN 4, and internet access via PPPoE on VLAN 6 is also functioning as expected.
However, I am encountering difficulties enabling IPv6 when using Virtual WAN.
Despite configuring IPv6 settings on the PPPoE WAN profile (including prefix delegation), my router nore my LAN devices are receiving IPv6 addresses, and IPv6 connectivity appears to be non-functional.
Could you please advise on the correct procedure to enable IPv6 in this setup?
Specifically:
- Is IPv6 fully supported when using Virtual WAN profiles?
- Are there known limitations or firmware requirements for IPv6 with Virtual WAN?
- What additional steps are required to ensure proper IPv6 address assignment and routing?
I am currently running firmware version ER605 V2 firmware 2.3.0 and using Omada Controller version OC200 v1.0 firmware 1.36.7 Build 20250707 Rel.72474.
Thank you in advance for your assistance.
Hi @cmcouwenb
Thanks for posting here.
Did you test to dial up with the IPv6 connection via the physical WAN port? What's the result?
So the only way to configure IPv6 is on the physical WAN port. According to documentation ipv4 should net be configured using PPPoE. This should be done on the virtual WAN port when you need IPTV. The pictures show the physical and virtual WAN port configuration.
Now i get the following error message: PPPoE internet failed to connect to the server because sending PADI times out
This message only appears when ipv6 is enabled on the physical WAN that is also used for the virtual WAN.
But there are no IPv6 setting possible in a virtual WAN, which would make sense to have also a virtual WAN ipv6.
My next test, when nobody is using the network, is to remove the virtual WAN setting and to see if IPv6 works at all.
