What's new
  • 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!

Virtual Servers not refreshing after apply changes and reboot?

John Doran

New Around Here
My router is a Asus RTN66U running Asus Merlin 380.59_0.

When I edit port forwarding rules on the WAN tab (Advanced Settings/WAN/Virtual Servers - Port forwarding) and hit Apply then Reboot, the updates seem to stick just fine.

However, when I look on the Log Port Forwarding tab (Advanced Settings/System Log/Port Forwarding) the old values still show up unchanged in VSERVER lines!

Example:
Original port forwarding rule: port 4445 external to 192.168.1.200 port 4445 internal using BOTH protocol
I change this to: port 4446 external to 192.168.1.250 port 4446 internal using BOTH protocol
Hit Apply. Hit Reboot. Log in again when it comes back.
Still shows the original rule on the Log page as two separate lines (one for UDP, one for TCP)

I also tried adding a new rule instead of editing an existing rule. Following apply/reboot/refresh, the new rule shows up in the WAN tab but not in the LOG tab.

I am currently abroad and unable to power cycle the router.
I am accessing the router from the LAN (actually from abroad but via OpenVPN hosted on an internal server at yet another LAN address, none of the above).

Does anyone have any suggestions? (apologies if this is a known bug but googling did not yield anything)
 
Last edited:
I was able to send someone to do a power cycle and it solved the problem. I can now see the port forward rules fully synchronized on the WAN and LOG pages.

This seems to be two bugs then. Does anyone know where I should report them?

(1) Bug 1: port forwarding rules requiring a power cycle to be properly picked up as described above
(2) Bug 2: the bigger issue for me is that a remote reboot seems not to properly reset the router. Apart from the port forwarding rules issue described, there was also a second problem with the Core 1 CPU being 100% busy while no traffic (possibly caused by two long-running OpenVPN server applications?). This persisted through several remote reboots but was solved by the power cycle.

For the record, I think ASUS MERLIN is AWESOME and I use many of the advanced features - just want this to work even better.
 
Thank you.. I will upgrade when I get home. I read the release notes though and it does not seem like the above two topics are addressed between 380.59 and 380.61.

Is it reasonable to expect a remote reboot to have the same effect as a power-cycle or is this something impossible to implement? Seems clear from the above that they have a different effect today.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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