GT-AX11000 IPV6 Not Working.

[Lotek]

I Just installed my new but IPV6 does not seem to be working on firmware 3.0.0.4.384_5979-g32d74f1. Anyone have a solution? I sent Asus a ticket regarding this issue.

[btrach144]

I am also failing https://test-ipv6.com on my GT-AX11000 running 3.0.0.4.384_5979

[Jedisquirrel]

Same here.

[Lotek]

I sent an email to Asus saying that IPV6 was not working. They sent me an email with a link to a beta version firmware file. Version GT-AX11000_9.0.0.4_384_6156-g5ade871_cferom_ubi. I can confirm that my IPV6 is working now.

Here is the link they sent me.

https://www.asuswebstorage.com/navigate/a/#/s/FB35D2EE8B894CE487B27D35802D28EEY

[raju2529]

Normally modem or router uses IPV4 , those setings are automatically applied to the mdem from telephone line through Internet service provider.

But IPV6 is entirely different , we need compaytible modem or router and supported Internet service provider.
Get IPV6 settings from isp and apply manually to modem or router on in lan settings on computer

[jumpsmm7]

it turns out in Version 3.0.0.4.384.5977 update, for what ever reason, asus did some updates to the ipv6 platform, which directly impacted how the router chose to advertise the eth0 style ipv6 connection. it was a change on one line of code that directly impacted this, in favor of detection of a different flavor of IPV6 which caused to negate eth0 router advertisement for IPV6 wan gateway. They did this executive decision to multiple of their routers and then had to turn around a fix it, but it turns out that this router is behind the race on receiving the update, simply because junior dev's are distracted by other features, such as the Version 3.0.0.4.384.5979 where they "fixed the light behavior".

[jumpsmm7]

this is strictly an ipv6 advertisement issue

[jumpsmm7]

In this case the issue impacted IPV6 native style connection,, No this is not because you didnt get information from ISP, on "native" style connection the router collects this information from Modem via IMCPv6 query and is collecting this information every reboot, it is simply because the router advertisement feature for certain style "native" supported connections is broken.