Agree… This is will becoming a nightmare for all retailers.
Should be full IPv6 at 8.5.x !!!
Next month (May/2025) I am starting the certification of MAX-BR1-MINI-LTE-MX-T-PRM, renew of 2023 certification, with ANATEL (Brazil) and … NO IPv6… this will be a real challenge!!!
Hi Peplink team and community,
It’s been 10 years since this thread was created, and it’s surprising — and frankly disappointing — that full native IPv6 support is still not available across the Peplink router lineup.
Over the last decade, IPv6 adoption has become critical. Many ISPs now offer native IPv6, cloud services depend on it, and enterprise and government networks increasingly require it. In 2025, proper IPv6 support is no longer a nice-to-have — it’s essential.
Peplink has been a leader in multi-WAN and SD-WAN technologies, yet continues to fall behind in a fundamental area of networking. The lack of comprehensive IPv6 functionality — including DHCPv6-PD, proper SLAAC handling, and reliable prefix delegation — is a serious limitation.
Can we please get an official update from the Peplink team on where IPv6 support stands today?
Is full IPv6 support on the roadmap? If so, when can users expect it?
This thread, and the continued interest from the community over the years, makes it clear that this feature is still highly requested and urgently needed. A transparent answer would go a long way.
Thanks in advance.
I want to chime in and say that … I just want to minimize layers of NAT. So towards that end, when can we have IPv6 on just the WAN side? Having a Peplink router be outwardly IPv6 would be a huge improvement even if it’s still IPv4 on the LAN side.
IPv6 on just the WAN side
I agree this would be a useful compromise.
Again, just focusing on fixing problems, if a WAN link has an IPv6 prefix delegation, then it would also allow Peplink routers to avoid all the quirks/bugs associated with port translation. I.e. the router could just stick to pure address translation.
I’d personally consider “outwardly IPv6 with simpler NAT” to be essential and pragmatic IPv6 support without overhauling the whole user experience, especially for a product that thrives/exists because of NAT.
Hello, guys…
I was reading and helping in another forum… and found this video tutorial…
It teach how to configure ipv6 at DLink DIR615 device…
So… a very simple device like this can support ipv6 configuration… and Peplink don’t…
Agree with @jpmx
Can Peplink give an official update about IPv6?
I also really need this supported as having over 30,000 devices behind an HD4 leads to NAT exaustion.
That is crazy. What type of devices are they?
Also IPv6 won’t automatically fix your 30k device problem. So much depends on what your ISPs are willing to support (or not) with IPv6 and what if any refinements Peplink makes to their NAT design once they start supporting IPv6.
Any news on the IP6 support (at least Peplink Router to provide DHCP v6 and IP6 firewall)?
The 30k isn’t a problem when a standard /64 will allow 18,446,744,073,709,551,616 hosts. The NAT or rather PAT exaustion is an issue as not all ISPs will give you more than one IP (ex. Starlink). If I had IPv6, there would be no reason for PAT. On other routing devices, I can tweak various timeouts and what range of ports PAT will use. Peplinks don’t expose that option.
IPv6 is becoming a necessity for some websites and services. Most ISPs (especially mobile) have this supported now. Your competitors (Cradlepoint et al.) all have SLAAC and DHCPv6 support. Ever so patiently waiting and happy to beta test!
