ASUS RT-N66U Firmware Version 3.0.0.4.374.2239

[-AndyH-]

Who is your ISP? Comcast's IPv6 implementation works with this version of firmware here.

It's a UK ISP, Plusnet.

Here's my router log (tried it again and it still does not work):

Jan 1 00:00:26 syslog: module nf_conntrack_ipv6 not found in modules.dep
Jan 1 00:00:26 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 1 00:00:26 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan 1 00:00:26 kernel: nf_nat_rtsp v0.6.21 loading
Jan 1 00:00:26 rc_service: ip-up 372:notify_rc stop_upnp
Jan 1 00:00:26 miniupnpd[349]: received signal 15, good-bye
Jan 1 00:00:26 rc_service: ip-up 372:notify_rc start_upnp
Jan 1 00:00:26 miniupnpd[432]: HTTP listening on port 34113
Jan 1 00:00:26 miniupnpd[432]: Listening for NAT-PMP traffic on port 5351
Jan 1 00:00:26 rc_service: ip-up 372:notify_rc stop_ntpc
Jan 1 00:00:26 rc_service: ip-up 372:notify_rc start_ntpc
Jan 1 00:00:26 rc_service: waitting "stop_ntpc" via ip-up ...
Jan 1 00:00:27 WAN Connection: WAN was restored.
Jan 1 00:00:35 rc_service: ipv6-up 370:notify_rc start_rdnssd
Jan 1 00:00:35 syslog: module nf_conntrack_ipv6 not found in modules.dep
Jan 1 00:00:35 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 28 09:36:02 rc_service: ntp 437:notify_rc restart_upnp
Jan 28 09:36:02 rc_service: ntp 437:notify_rc restart_radvd
Jan 28 09:36:02 rc_service: waitting "restart_upnp" via ntp ...
Jan 28 09:36:02 miniupnpd[432]: received signal 15, good-bye
Jan 28 09:36:02 miniupnpd[473]: HTTP listening on port 44053
Jan 28 09:36:02 miniupnpd[473]: Listening for NAT-PMP traffic on port 5351
Jan 28 09:36:03 rc_service: ntp 437:notify_rc restart_diskmon
Jan 28 09:36:03 rc_service: waitting "restart_radvd" via ntp ...
Jan 28 09:36:03 radvd[475]: no auto-selected prefix on interface br0, disabling advertisements
Jan 28 09:36:04 rdnssd[451]: Get IPv6 address & DNS from DHCPv6
Jan 28 09:36:04 rc_service: rc 483:notify_rc start_dhcp6c
Jan 28 09:36:04 dhcp6c[484]: yyerror0: /etc/dhcp6c.conf 4: syntax error
Jan 28 09:36:04 dhcp6c[484]: yyerror0: /etc/dhcp6c.conf 4: fatal parse failure: exiting (1 errors)
Jan 28 09:36:04 dhcp6c[484]: main: failed to parse configuration file

 

[RMerlin]

It's a UK ISP, Plusnet.

Here's my router log (tried it again and it still does not work):
Jan 28 09:36:04 rc_service: rc 483:notify_rc start_dhcp6c
Jan 28 09:36:04 dhcp6c[484]: yyerror0: /etc/dhcp6c.conf 4: syntax error
Jan 28 09:36:04 dhcp6c[484]: yyerror0: /etc/dhcp6c.conf 4: fatal parse failure: exiting (1 errors)
Jan 28 09:36:04 dhcp6c[484]: main: failed to parse configuration file

This is a bug in recent Asus firmwares, they are missing a carriage return between two config lines, causing the syntax error.

 

[-AndyH-]

Would that cause the IPv6 not to work properly?

Thanks

 

[jim769]

Still keep losing ipv6 address and I have to reboot the router to get it to reassign another one. I have decided to just disable v6 for now in anticipation that the next Merlin release will fix this most annoying issue. Merlin any idea when you will have another firmware release and will you be able to implement a fix for this issue ? Thanks Jim !!


RT-N66U (3.0.0.4_374_38_2em)

 

[Techno]

All-

Thinking about jumping from 3.0.0.4.374.979 to 3.0.0.4.374.2239 sometime soon to help resolve some wireless range issues but had a few questions?

1. Will it keep current configuration or wipe the device?
2. Should you "always" do a factory reset when upgrading firmware or is it not really necessary?

Thanks.....

 

[DavidEBSmith]

Doing a reset appears to be better but I went from .979 to .2239 without doing a reset and kept and the settings and had no issues.

BTW for those of us with the RT-N66W, there was a bug with saving settings that is fixed in .2239.

 

[Techno]

Doing a reset appears to be better but I went from .979 to .2239 without doing a reset and kept and the settings and had no issues.

BTW for those of us with the RT-N66W, there was a bug with saving settings that is fixed in .2239.

David-

Did you see a "decent" increase in wifi range? Right now...to be honest mine sucks...which in itself sucks because that was one of my main reasons for deciding to go with Asus RT-N66W.

 

[DavidEBSmith]

Couldn't say that it made a difference or not in wifi range. I'm surrounded by about 25 other routers on 2.4 ghz so signal strength and range bounce around all the time anyway.

What did make a difference was getting a set of those giant 9 db antennas on eBay.

My main reason for going to 2239 was for OpenVPN.

 

[jkill28]

have upgraded to this Beta firmware thinking it could solve my OpenVPN client issue, when I VPN to an OpenVPN server outside my network it works but then the routes aren't removed from the routing table when I disconnect and I have to reboot the router to remote the route.

I don't think this is part of the .ovpn profile since I tried it on a Windows machine and on disconnect the routes are being removed so definately no persistent route specified in the profile...

The firmware didn't solve that though, any one else has the error?

 

[Trentors]

have upgraded to this Beta firmware thinking it could solve my OpenVPN client issue, when I VPN to an OpenVPN server outside my network it works but then the routes aren't removed from the routing table when I disconnect and I have to reboot the router to remote the route.

I don't think this is part of the .ovpn profile since I tried it on a Windows machine and on disconnect the routes are being removed so definately no persistent route specified in the profile...

The firmware didn't solve that though, any one else has the error?

I have the exact same problem. I need to reboot the router constantly in order for my OpenVPN connection with the office to work.

The problem started with 3.0.0.4.374.2050 and this version does not solve it.

 

[Bulldog]

When I updated my RT-N56U to this firmware, the word 'Beta' did not appear anywhere in the description on Asus' website. I'm really upset. I never install beta firmware or drivers. Is it possible to go back to the previous (stable) version?

 

[MarkyPancake]

It says 'Beta Version' in red text in front of the version number when I visit Asus' support page.

http://www.asus.com/Networking/RTN66U/#support

 

[slyphnier]

When I updated my RT-N56U to this firmware, the word 'Beta' did not appear anywhere in the description on Asus' website. I'm really upset. I never install beta firmware or drivers. Is it possible to go back to the previous (stable) version?

not sure if they forgot mentioning beta back when the put on sites
but now BETA showed beside the driver version

yea u can roll back to any firmware you like, its same like bios
just to make sure everything ok, do hard-reset before&after flashing firmware

 

[bodean]

Channel 44 Control Channel, 48 Bonded Channel

inssider shows 100% @ -48dBm - significant? Maybe.

Ookla speed test 52.91/11.46 @ 16ms latency. - significant? No.

File download ~29MB/s avg. - throughput - MUCH, MUCH better by 17MB/s

So it looks like 44 channel is a winner based on your tests

 

[L&LD]

So it looks like 44 channel is a winner based on your tests

Yes, but don't forget; the point is that each one of us has to do this kind of testing to see which channel is the best for our specific environment and specific equipment.