ASUS RT-AC68U Firmware version 3.0.0.4.374.4561 is out

[SeCrEt_BoY]

So sad... I paid the best and must waiting for 2 weeks to have it in hand but the reboots issue make me disapointed... I saw in log file that the router reboot by me (by my username). Confusing...

Gửi từ SM-N900 của tôi bằng cách sử dụng Tapatalk

 

[L&LD]

No reason to be sad.

If it doesn't work for you, get a router that does. Or change your configuration to one that does work.

A systematic approach to testing and verifying at each step will do wonders to help yourself and also help the community in general if you can share your findings in an accessible manner.

 

[SeCrEt_BoY]

No reason to be sad.

If it doesn't work for you, get a router that does. Or change your configuration to one that does work.

A systematic approach to testing and verifying at each step will do wonders to help yourself and also help the community in general if you can share your findings in an accessible manner.

:| Buy an expensive router and you just say that buy another? I share the system log file to ASUS and waiting for the reply. I try to change many configurations but still have the reboot issues.

Gửi từ SM-N900 của tôi bằng cách sử dụng Tapatalk

 

[RMerlin]

:| Buy an expensive router and you just say that buy another? I share the system log file to ASUS and waiting for the reply. I try to change many configurations but still have the reboot issues.

Gửi từ SM-N900 của tôi bằng cách sử dụng Tapatalk

This bug was only recently introduced, so I'm fairly sure it will be eventually be resolved. Asus rushed out a lot of updates recently to address security issues, it's possible those releases didn't get the usual amount of QA testing they would usually get.

As a temporary solution, you can revert back to either Asus's 374_583, or to my own firmware, and make sure you have FTP and AiCloud disabled. Once the issue gets resolved by an update, you will be able to update to that new release.

 

[speedingcheetah]

This bug was only recently introduced, so I'm fairly sure it will be eventually be resolved. Asus rushed out a lot of updates recently to address security issues, it's possible those releases didn't get the usual amount of QA testing they would usually get.
.

This reboot issue appears to be exclusive to the AC68U and the last 2 firmware releases from what I have read so far.

Glad my AC56U isn't affected(been 14hrs with no issues on .4561)

Asus did drop the ball a couple times with bad firmware releases, a while back while the router was quite new.....one of their updates first killed my PPPoE connection, then a second update, router would freeze whenever you launched a torrent. So I had to revert to older firmware for a month or so before they released an update that worked for me. I was very surprised to see Asus actually interact a bit with users via this site and help out.

Now, my AC56U is freaking awesome....It was well worth the hiccups I had since I purchased it right after it was released.

Though, it seems the AC68U had had many more "hiccups" than the AC56U....wonder why that is since that is supposed to be their flagship router...they do have different hardware right?

 

[jmone]

I too was getting lots of reboots - trying 384.40_alpha6 - will report back

Lasted 4 Hours before it rebooted

 

[RMerlin]

Lasted 4 Hours before it rebooted

Then I have absolutely no idea. It's impossible to troubleshoot beside being connected with a serial cable to the router while the reboot occurs - and since I had only one single reboot in a whole week here, I can't troubleshoot this. Asus will have to.

 

[RMerlin]

Glad my AC56U isn't affected(been 14hrs with no issues on .4561)

This is the weird part about this, since code-wise the firmware is very similar on both routers, the biggest difference being the wireless driver itself - and that theory has been ruled out by one tester. I can see a few binary-only blobs that might potentially crash (the emf/igs modules, and the Ethernet et driver for instance), but those should be the same on both routers.

Best I can recommend for now is that people affected by this send an email to Networking_Support@asus.com. Mention:

• The firmware versions you tested, and the results
• Whether you tested with HW acceleration disabled or not
• The type of WAN interface (DHCP, PPPoE, etc...)
• Whether you have any USB disk plugged or not (we know that it's unrelated since people affected by this didn't have any USB disk plugged, so that'd be something for them to rule out)
• If you did test after a factory default reset + manual reconfiguration of your router (that would be the first thing support would recommend trying, so best you try this first before emailing them)

In the mean time, solutions that seem to work:

• Reverting back to Asus' 374_583, and making sure that FTP, Samba and AiCloud are all disabled
• My 374.40-alpha4 firmware released last week, which seems to work - I didn't receive any feedback about reboots with that one yet. It contains the security fixes of Asus's 4422, but all the binary-only bits for the RT-AC68U are the same as in 583 since I didn't have them at the time.

 

[RMerlin]

Lasted 4 Hours before it rebooted

I'll see if I can find the time tomorrow night to also revert all the other closed-source bits to those from 583 (I only reverted the wireless driver in that alpha6 build) and publish an alpha7 build, so hopefully I can have an alternative to offer until Asus resolves this new issue.

 

[jmone]

Happy to test - at present I'm trying - 3.0.0.4.374.39 (Merlin build) on the 68 (same version as my 2 x 66's and they have been running for days/weeks... but are being used as APs)

 

[jmone]

...or do you want me to try 374.40-alpha4 overnight?

 

[jonstatt]

Although not related to the crashing, why are my logs being filled with

Feb 24 08:38:35 miniupnpd[672]: sendto(udp): Operation not permitted
Feb 24 08:42:25 miniupnpd[672]: Expired NAT-PMP mapping port 5001 TCP removed
Feb 24 08:47:25 miniupnpd[672]: Expired NAT-PMP mapping port 5001 TCP removed
Feb 24 08:50:36 miniupnpd[672]: sendto(udp): Operation not permitted


It is pages and pages of it. The AC66U never logged any miniupnpd errors and as there is no IP address or anything listed, I cannot track what is trying to do the non-permitted operations!

Only since the 2 latest firmware builds has it started logging expiring NAT-PMP messages (5001 is a Slingplayer)

 

[SeCrEt_BoY]

24/2 13:43:57 GMT +7
Log file:
Syslog started busybox v1.17.4 and the time of log reset to 1/1
and I saw a lots of events in logs. After about 3min the router said WAN was restored... Still the reboot problems like tonight but I still dont know what make router reboot...
Reverting to older FW.

Gửi từ SM-N900 của tôi bằng cách sử dụng Tapatalk

 

[jjhowey]

I was at 22 hours or more .. and then a reboot (I saw a cached page before it refreshed). Coincidentally - it coincides when my guest network would get used.

If you're curious Merlin, can you enable your Guest and see if you can reproduce? If not, no worries.

 

[RMerlin]

Any of those affected by the reboots using (or not) IPv6?

 

[RMerlin]

...or do you want me to try 374.40-alpha4 overnight?

Go with 374.40-alpha4, since it has all the recent security fixes in it.

 

[SeCrEt_BoY]

Any of those affected by the reboots using (or not) IPv6?

No guest and no IPv6 enable > Still reboot...

Gửi từ SM-N900 của tôi bằng cách sử dụng Tapatalk

 

[jjhowey]

Any of those affected by the reboots using (or not) IPv6?

Nope, no IPv6

 

[PhiL_P]

Dang, made it to about 15 hours uptime on alpha6 but now rebooted. Seemed to coincide with my kids getting home from school and start using their iPads on the wifi. Not using IPv6 and nobody connecting via the guest wifi.

 

[jonstatt]

Dang, made it to about 15 hours uptime on alpha6 but now rebooted. Seemed to coincide with my kids getting home from school and start using their iPads on the wifi. Not using IPv6 and nobody connecting via the guest wifi.

I am wondering if its connected with devices that connect to both 2.4GHz and 5GHz. I got my first reboot after my phone decided to drop the 5GHz connection and switch to the 2.4GHz one....