What's new

ASUS RT-AC68U Firmware version 3.0.0.4.374.4561 is out

  • 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!

Glad they specifically acknowledged the Sonos bug and fix. Running okay with this build now.

Does anyone know specifically what happens in the EU if you choose a channel like 100 without the DFS tick box being enabled? Technically I guess this means you are running illegally?
 
Observation: I have a Intel Ult N 6300 wireless nic connected to my 5GHz .. I manually pointed it to the 5 after I had problems with 4422 reboots. I will look into this after the Acceleration tests. Could be something with Intel drivers perhaps?

12 hours stable with NAT Acceleration disabled. So what changed in 4422 (and consequently carried into 4561) in this area?

PS: Yay Team Canada!~
 
Updated my AC68U to latest 4561 build from 583 and I am now also seeing random reboots.

WAN connection PPPoE
No USB disk connected
DLNA DISABLED
NAT acceleration DISABLED
Some port mappings
2.4 / 5gz wifi ENABLED and Guest ENABLED
VPN currently disabled.
Firewall / DOS ENABLED

On one of the reboots, I saw in log that I was getting Port Scanned before the reboot.

The last reboot I just had, this was in the log

Feb 23 14:25:21 miniupnpd[687]: Expired NAT-PMP mapping port 52179 UDP removed
Feb 23 14:25:21 miniupnpd[687]: Expired NAT-PMP mapping port 52179 TCP removed

From reading the forum, there seems to be no common setting causing it at the moment. I might have to downgrade back to 583 as the family keep moaning about loss of access :mad:
 
Wondering if this reboot issue is exclusive to the AC68U.....

I just flashed .4561 to my AC56U and it's been abut an hour with no issues.

I also had no issues with the previous version (.4422).
 
I have the problems about reboot issue too... Haiz... so terible! Playing game and the router reboot automaticly... >>> Angry!!!!!! Firmware 4561!
 
I'm still ok.

Mostly default:
Custom IP range.
WPA2
One port forwarded.
Bumped 2.4 power to 100mW
Ch 1 20Mhz, Ch157 20/40/80 Mhz
No USB or Guest
Preamble Type Short
Anywhere from 10-21 devices at any given time.
Memory running at 666MHz
 

Attachments

  • 4561_uptime.JPG
    4561_uptime.JPG
    14.9 KB · Views: 538
Last edited:
I'm still ok.

Mostly default:
Custom IP range.
WPA2
One port forwarded.
Bumped 2.4 power to 100mW
Ch 1 20Mhz, Ch157 20/40/80 Mhz
No USB or Guest
Preamble Type Short
Anywhere from 10-21 devices at any given time.
Memory running at 666MHz


There should be no need to touch the power output. The default should be at max even though the GUI only says 80mW. It's not intuitive but changing that value will likely cap the power output.
 
Feb 23 22:22:17 miniupnpd[646]: Expired NAT-PMP mapping port 9585 UDP removed
Feb 23 22:22:17 miniupnpd[646]: Expired NAT-PMP mapping port 9585 TCP removed

This is the last log and the router reboot. I thinks ASUS Staff must fire some members...
 
Increasing numbers of reboots here as well.

Feb 22 14:26:26 miniupnpd[668]: Expired NAT-PMP mapping port 34956 UDP removed
Feb 22 14:26:26 miniupnpd[668]: Expired NAT-PMP mapping port 34956 TCP removed
Feb 22 15:01:09 miniupnpd[668]: Expired NAT-PMP mapping port 8105 UDP removed
Feb 22 15:01:09 miniupnpd[668]: Expired NAT-PMP mapping port 8105 TCP removed
Feb 22 18:06:17 miniupnpd[668]: Expired NAT-PMP mapping port 8105 UDP removed
Feb 22 18:06:17 miniupnpd[668]: Expired NAT-PMP mapping port 8105 TCP removed
Feb 22 19:29:07 miniupnpd[668]: Expired NAT-PMP mapping port 34956 UDP removed
Feb 22 19:29:07 miniupnpd[668]: Expired NAT-PMP mapping port 34956 TCP removed
Jan 1 01:00:12 syslogd started: BusyBox v1.17.4
Jan 1 01:00:12 kernel: klogd started: BusyBox v1.17.4 (2014-02-20 18:49:12 CST)
Jan 1 01:00:12 kernel: Linux version 2.6.36.4brcmarm (gitserv_asus@wireless-pub1) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Thu Feb 20 18:55:38 CST 2014
Jan 1 01:00:12 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f

And:
Feb 23 16:49:16 miniupnpd[662]: sendto(udp): Operation not permitted
Jan 1 01:00:12 syslogd started: BusyBox v1.17.4
Jan 1 01:00:12 kernel: klogd started: BusyBox v1.17.4 (2014-02-20 18:49:12 CST)
 
Last edited:
There should be no need to touch the power output. The default should be at max even though the GUI only says 80mW. It's not intuitive but changing that value will likely cap the power output.

Can anyone else confirm or deny the statement above. I made this slight boost in power for my furthermost locations based on what I saw with inSSIDer.
 
Airplay issues

Has anyone determined if the Airplay/Bonjour issues in bridge mode have been resolved?

Airplay-ing content to a target behind an RT-AC68U/R in bridge mode has been problematic for some time. Bonjour host names can't be resolved for targets behind the bridge.

The Netgear R6300 and R7000 suffer from the same issue.

Iv had similar issues with the RT-AC66 *AND* 68 in AP mode... even with IGMP snooping enabled
 
Can anyone else confirm or deny the statement above. I made this slight boost in power for my furthermost locations based on what I saw with inSSIDer.


In my testing (RT-N66U RMerlin 374.39_0-em) the Tx power set to 100mW offers the best performance.

When I set it to 120mW for example; the throughput dropped significantly, although the signal stayed strong.

I don't test for the best signal (as indicated by inssider, for example); I test for best throughput and for the RT-AC66U, RT-AC56U, RT-N56U and RT-N66U's that I've configured, the 100mW Tx power setting proved to be the best overall each time.

See/search some of my previous posts for more details (use Report to RMerlin RT-N66U or RT-AC56U for your search terms).
 
Feb 23 22:22:17 miniupnpd[646]: Expired NAT-PMP mapping port 9585 UDP removed
Feb 23 22:22:17 miniupnpd[646]: Expired NAT-PMP mapping port 9585 TCP removed

This is the last log and the router reboot. I thinks ASUS Staff must fire some members...

Those entries are perfectly normal. It means you have something on your network which forwarded these two ports at some point, and the forwards have expired from being unused for a while and were removed by the firmware.
 
In my testing (RT-N66U RMerlin 374.39_0-em) the Tx power set to 100mW offers the best performance.

When I set it to 120mW for example; the throughput dropped significantly, although the signal stayed strong.

I don't test for the best signal (as indicated by inssider, for example); I test for best throughput and for the RT-AC66U, RT-AC56U, RT-N56U and RT-N66U's that I've configured, the 100mW Tx power setting proved to be the best overall each time.

See/search some of my previous posts for more details (use Report to RMerlin RT-N66U or RT-AC56U for your search terms).

I use 110mW on my AC56U on the 5ghz band...seems to be the best for me.
 
I use 110mW on my AC56U on the 5ghz band...seems to be the best for me.


I wondered how granular the Tx setting would be for optimum performance. I will certainly be trying this in my next test cycle when the new 374.40_0 firmware is released.

I may even try every 5mW and maybe even single digit Tx power changes and throughput tests if my time permits.
 
Those entries are perfectly normal. It means you have something on your network which forwarded these two ports at some point, and the forwards have expired from being unused for a while and were removed by the firmware.

I know. But after that the router reboot... Haiz... seem I need to downgrade to 385 again... Just have a reboot issue but ASUS can not fix it :(
 
Last edited:
Had another reboot on 4422. I have the idea it will reboot as soon as my phone disconnects from the network when it's out of range i.e. when leaving the house.

I'm using identical SSID's on the 2,4 and 5G network, perhaps that's causing a problem.
Will change the name on the 2.4G network and see if it does anything.
 
Hy,
I had problems with restarting the router as well. I had the wrong hour programmed in (not the real one). Since I have changed the exact hour in the router I had no other problems with the restart.
I hope this helps.

Uptime: 1 days 1 hours 27 minutes 9 seconds (without restart)
FW_RT_AC68U_30043744561
WAN connection - PPPoE
No USB disk connected
NAT acceleration - ENABLE
IPV6 Connection type - Native , interface - PPP
Wireless 2,4/5 Ghz WPA2-Personal
VPN Server - OFF
WPS - OFF
 
I wondered how granular the Tx setting would be for optimum performance. I will certainly be trying this in my next test cycle when the new 374.40_0 firmware is released.

I may even try every 5mW and maybe even single digit Tx power changes and throughput tests if my time permits.

Originally, Asus's granularity was 20mW (that is, it would apply different power settings out of a table for every 20 mW increments). Not sure if that's still the case, I haven't looked at that part of the code in a long time.
 

Latest threads

Sign Up For SNBForums Daily Digest

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