What is up with ASUS and NAT loopback?

[oturn]

On my RT-AC68U, NAT loopback became very unstable starting at 3.0.0.4.378.3813. It works for a day or so, then stops. I've spent far too much time trying to figure out what the heck is going on. At first I thought port forwarding was broken, since disabling and re-enabling port forwarding allowed me to connect to my internal hosts for a while. Next, I noticed adding an external DNS server on the LAN side fixed things. I read this wasn't the best idea, so I tried the next "fix", which was disabling NAT acceleration. This is working, but it's not something I want permanently disabled. Finally, someone on another thread suggested that disabling OpenVPN stabilizes NAT loopback. I haven't tried this yet.

Can someone with far more expertise than me please stop my twisting in the wind? I just want stable NAT loopback. Will ASUS ever figure this out, or is Asuswrt-Merlin the solution?

 

[RMerlin]

The current NAT loopback issues are probably related to the DPI engine, which was only added with 378_xxxx.

 

[oturn]

The current NAT loopback issues are probably related to the DPI engine, which was only added with 378_xxxx.

Any idea when it will become stable again? Does your build overcome the problem? In the meantime, is there a preferred temporary fix?

 

[CiscoX]

Any idea when it will become stable again? Does your build overcome the problem? In the meantime, is there a preferred temporary fix?

ASUS released a new firmware version for the RT-AC68U today

http://www.snbforums.com/threads/rt-ac68u-new-fw.23302/