Asus rt-ac66u 3.0.0.4.374.2050

[krum]

wonder if Parent Controls are fixed, It doesn't say anything about it,

1. Allowed LAN stateful settings for DHCP6.
2. Allowed manually scan after resetting.
3. Modified DMZ settings in load-balanced mode.
4. Modified virtual server settings in load balanced mode.
5. Modified some FAQ hyperlinks.
6. Modified configurations of WeTelecom WM-D300.

Fixes:
1. Fixed several UI issues.
2. Fixed download master install issue.
3. Fixed VPN client DNS issues.
4. Fixed open VPN manual client list setting issues.
5. Fixed PPPoE throughput issues.
6. Fixed media-server related issues.
7. Fixed httpd vulnerably issues.

Additions:
1. Add new Malaysia 3G ISP in USB modem.
2. Add media-bridge mode.
3. Add OpenVPN, VPN Client.
4. Enable WPS under AP mode.

 

[bluepoint]

Wrong Forum, please post it here.

 

[krum]

Wrong Forum, please post it here.

No Really RT_AC is here in the right forum...

DO you need a link

RT_AC_
http://support.asus.com/Download.aspx?SLanguage=en&m=RT-AC66U&p=11&s=2

 

[bluepoint]

Ooops, sorry my bad. Same version for RT-N66u, read your post with that thinking.

 

[FLA NL]

I've a strange issue with this firmware using Native IPv6 with DHCP-PD. When I reboot the router the IPv6 gateway doesn't get assigned. If I afterwards turning the internet connection off and on again through the router's webinterface the gateway does get assigned and IPv6 is working.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

 

[RMerlin]

I've a strange issue with this firmware using Native IPv6 with DHCP-PD. When I reboot the router the IPv6 gateway doesn't get assigned. If I afterwards turning the internet connection off and on again through the router's webinterface the gateway does get assigned and IPv6 is working.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

Asus broke the DHCPv6 client in recent code, I suspect it might be the same issue in 374.2050.

I think you can work around the issue by having DNS automatically obtained from your ISP rather than manually specifying IPv6 DNS servers.

 

[FLA NL]

Asus broke the DHCPv6 client in recent code, I suspect it might be the same issue in 374.2050.

I think you can work around the issue by having DNS automatically obtained from your ISP rather than manually specifying IPv6 DNS servers.

Thanks for your answer but it occurred when DNS was set to be obtained automatically. I did set it manually before but after a while the ipv6 connection was lost so I tried it with obtaining it automatically to see if that was more stable and noticed this issue.

Don't remember if I also had to turn the internet connection on/off the get it working when the DNS was set manually. Don't have time now to test that again.

 

[RMerlin]

Thanks for your answer but it occurred when DNS was set to be obtained automatically. I did set it manually before but after a while the ipv6 connection was lost so I tried it with obtaining it automatically to see if that was more stable and noticed this issue.

Then I'm afraid you will have to either revert to a previous firmware, wait for the next one, or switch to my firmware once I release a new build that includes this fix (should be sometime this week).

 

[FLA NL]

Then I'm afraid you will have to either revert to a previous firmware, wait for the next one, or switch to my firmware once I release a new build that includes this fix (should be sometime this week).

Reverted for now to the previous version. But I will try your firmware when the issue is fixed

 

[taedan]

Traffic monitor seems broken on this. Went back to 726 and it works again.