ASUS RT-AC68U FW: 3.0.0.4.378_3873 Bugs

[CiscoX]

Hi.

I have notice something strange when i enable my Adaptive QoS.
My RT-AC68U have been running good for some days, then i decide to enable Adaptive QoS. Bad thing to do.
I start getting this message in my syslog.

rc_service: rc 1297:notify_rc restart_wrs

So i decide to disable it, but still get the same.
So i have to do a factory reset

I believe the notify_rc restart_wrs has something to do with the NAT Loopback. Wasn't that fixed on FW 3.0.0.4.376.3626?

 

[RMerlin]

Hi.

I have notice something strange when i enable my Adaptive QoS.
My RT-AC68U have been running good for some days, then i decide to enable Adaptive QoS. Bad thing to do.
I start getting this message in my syslog.
So i decide to disable it, but still get the same.
So i have to do a factory reset

I believe the notify_rc restart_wrs has something to do with the NAT Loopback. Wasn't that fixed on FW 3.0.0.4.376.3626?

This line is normal, it's one of the services related to the DPI engine.

 

[CiscoX]

This line is normal, it's one of the services related to the DPI engine.

Thanks RMerlin.

I have to restart my firewall to get the NAT Loopback working or login via SSH and enter service restart_firewall

After that i can access my HTTP test server from outside.

My external IPORT

I've made a firewall rule for that

ALL TCP 8088 192.168.10.101 8088

I'm gonna test your FW again, don't remember I've seen this on your 378.50

 

[RMerlin]

Asus did fix some things related to the NAT loopback on the RT-AC87U recently, it's possible that their fix might not be complete.

I just wish the DPI engine didn't wipe out some of the iptables chains at (re)start time, so I could keep using my original NAT loopback code... That was working flawlessly.

There's too much factors at play here, including the DPI engine and the NAT acceleration. One of these (if not both) is causing a lot of random issues with NAT loopback and port forwards.

 

[CiscoX]

Asus did fix some things related to the NAT loopback on the RT-AC87U recently, it's possible that their fix might not be complete.

I just wish the DPI engine didn't wipe out some of the iptables chains at (re)start time, so I could keep using my original NAT loopback code... That was working flawlessly.

There's too much factors at play here, including the DPI engine and the NAT acceleration. One of these (if not both) is causing a lot of random issues with NAT loopback and port forwards.

Thanks RMerlin,

I appreciate your information, so let's hope ASUS fix this and the other bugs that has been reported, specially in RT-AC87U

 

[staticfree]

When will the AC68P router get its update fixes?

I am wondering when Asus is going to release its next update to fix the NAT loopback issue and other bugs reported for the AC68x routers.