RT-AC68R / FW 3.0.0.4.378_3873 / NAT loopback stops working

[TSloper]

The latest FW appears to have an issues with NAT loopback stopping within a few minutes after booting. I can use my public address for a brief time from my LAN to access my NAS but after a few minutes it will no longer connect. If I am not on the LAN I can still access the NAS via the public address. I've loaded the FW twice and cleared the NVRAM each time.

FW 3626 did not have any problem with NAT loopback.

Is anyone else seeing an issue with FW 3873?

 

[staticfree]

The latest FW appears to have an issues with NAT loopback stopping within a few minutes after booting. I can use my public address for a brief time from my LAN to access my NAS but after a few minutes it will no longer connect. If I am not on the LAN I can still access the NAS via the public address. I've loaded the FW twice and cleared the NVRAM each time.

FW 3626 did not have any problem with NAT loopback.

Is anyone else seeing an issue with FW 3873?

Yes, I noticed the same thing with my RT-68P router when I loaded this firmware. I cannot access my devices when I am on my own internal LAN using the outside network addressing but I can still access then from outside my network (from the WAN internet remotely). So NAT loopback seems to be disabled or not functionining properly on this latest firmware version. I wish that they would fix it and give us a menu option to enable or disable the
NAT loopback feature.

 

[ontwowheels]

The latest FW appears to have an issues with NAT loopback stopping within a few minutes after booting. I can use my public address for a brief time from my LAN to access my NAS but after a few minutes it will no longer connect. If I am not on the LAN I can still access the NAS via the public address. I've loaded the FW twice and cleared the NVRAM each time.

FW 3626 did not have any problem with NAT loopback.

Is anyone else seeing an issue with FW 3873?

On an RT-AC68U (TM-AC1900), ran 3873 loopback didn't work. Had Time Machine problems so I bailed back to the latest Asus firmware, where loopback does not work either.