What's new

[Official] RT-AC68U Firmware version 3.0.0.4.380.1842

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I'm running it.

I'm running it. I haven't done any formal speed testing yet, but this morning I observed steady 220 Mbps for SMB file transfer from my MacMini across wired LAN to 5 GHz 802.11n to my MacbookPro. This is the fastest speed I've ever seen for this combo. Prior to this, the best I'd seen was about 180 Mbps.
 
watchdog: restart httpd
rc_service: watchdog 445:notify_rc start_httpd
RT-AC68R: start httpd - SSL

I keep getting this in the log a few times a minute since upgrading to 3.0.0.4.380.1842. Anybody else? Any advice?


I did do a complete factory reset and even took the time to manually re-enter all the settings instead of importing them. But the same thing still happens.
 
I was about to post the same question. I'm seeing the same thing in the logs on mine with the new version. Also, is anyone else seeing just the word "App" beside the three indicator icons in the upper right of the firmware interface? Normally I thought this would be the spot that the firmware check icon would appear, no? You can see what I mean in this screenshot. Note also the regular as clockwork CPU spikes showing up, even though there's very little network activity as I write this. Fairly certain those are corresponding to the constant httpd restarts. Ugh.

screenshot.jpg


watchdog: restart httpd
rc_service: watchdog 445:notify_rc start_httpd
RT-AC68R: start httpd - SSL

I keep getting this in the log a few times a minute since upgrading to 3.0.0.4.380.1842. Anybody else? Any advice?


I did do a complete factory reset and even took the time to manually re-enter all the settings instead of importing them. But the same thing still happens.
 
watchdog: restart httpd
rc_service: watchdog 445:notify_rc start_httpd
RT-AC68R: start httpd - SSL

I keep getting this in the log a few times a minute since upgrading to 3.0.0.4.380.1842. Anybody else? Any advice?


I did do a complete factory reset and even took the time to manually re-enter all the settings instead of importing them. But the same thing still happens.

I'm seeing the same thing as well for my B1 68U.
 
I had to go back to release 3.0.0.4.378.9313 . My Netatmo will not work with any of the newer releases. Hopefully this issue will be resolved.
 
1842 build is sucky.

Port forwarding suddenly stopped working yesterday after power outage.

I had to restore the router to factory defaults with WPS button trick and set it up all over again.
 
Made the mistake of upgrading to the latest 1842 build and immediately lost wifi connectivity on the 2.4GHz side. The SSID shows up, but no clients were able to connect, even with NAT acceleration enabled. After many, many hours of troubleshooting and pulling my hair out, I finally traced the issue to the Traditional QoS setting (which I had been running -- and NEED). I disabled QoS and clients were able to connect again. Turned it back on and they couldn't. I tried downgrading to the prior version (which was working fine with QoS + 2.4GHz clients) and the problem persisted. It appears that the firmware upgrade must have made some permanent changes in ROM that can't be undone by downgrading. If anyone else could test and verify the issue using QoS (adaptive OR traditional), I would be curious to know if the problem can be reproduced. (Also would like to add that disabling NAT acceleration also caused loss of connectivity on 2.4GHz band.)
 
  • Like
Reactions: msb
watchdog: restart httpd
rc_service: watchdog 445:notify_rc start_httpd
RT-AC68R: start httpd - SSL

I keep getting this in the log a few times a minute since upgrading to 3.0.0.4.380.1842. Anybody else? Any advice?


I did do a complete factory reset and even took the time to manually re-enter all the settings instead of importing them. But the same thing still happens.

mine did this too if HTTPS authentication method enabled.
 
Has anyone tested the repeater-mode problem. Is it solved in this Firmware.
 
Installed this firmware about two weeks ago. Seems to be running fine except that I just noticed my system log showing a run time of 9 hours and there has not been a power failure.
 
I had to go back to release 3.0.0.4.378.9313 . My Netatmo will not work with any of the newer releases. Hopefully this issue will be resolved.

I also had to revert back from 3.0.0.4.380.1842 to 3.0.0.4.378_9313
2.4Ghz devices are not working correctly with firmwares 3.0.0.4.380.1031 and 3.0.0.4.380.1842 on my network
 
1842 build is sucky.

Port forwarding suddenly stopped working yesterday after power outage.

I had to restore the router to factory defaults with WPS button trick and set it up all over again.

Same here, i cant access my AC68U after a day or two using the latest firmware 1842. Portforwarding seems to be bad as well. Tried to setup my Plex on a port but its not working :/
Will go back a version to see how that works.
 
I just want to mention that my 68U B1 is occasionally loosing internet access. Seems to take anywhere from a few weeks to a month from the time of a reboot. The LAN and wireless remain functional though.
 
I just want to mention that my 68U B1 is occasionally loosing internet access. Seems to take anywhere from a few weeks to a month from the time of a reboot. The LAN and wireless remain functional though.

Can you test/verify that the modem is healthy?

Try turning off all network equipment for an hour or more (physically unplug everything you can from the AC outlets).

After waiting for as long as you can with the system down,

Turn on/plug in the modem and wait 5 minutes (or more) for it to stabilize.

Turn on/plug in the router and wait 5 minutes (or more) for it to stabilize.

Turn on/plug in any switches you may have in your network.

Turn on all your wired devices.

Turn on all your wireless devices.


Before doing the above, you may want to use new ssid's too for each band (you can use the old passwords).

If all the above doesn't help, make sure you are on the latest stable firmware and follow the additional steps in the link below.

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top