PRThomasUK wrote

I had the same problem after changing the management port to 8080.... However, after power cycling the router I could access to the management page on port 8080,,,,

In terms of port forwarding 80(HTTP) the port forward will work great externally, however internal clients will not be able to access as NAT Loopback is not enabled. I couldn't find an option in the management pages to enable it, however I found a post on another forum that allowed me to enable it via TELNET (only really suitable if you have a static external IP). This change does NOT survive a reboot so will need to be re-done every time the router is restarted!

Example: (external ip 1.1.1.1, internal network 192.168.1.0/24, webserver 192.168.1.10, router 192.168.1.1)

Connect via SSH (or telnet then type SH) and enter:

iptables -t nat -A PREROUTING -d 1.1.1.1 -m tcp -p tcp --dport 80 -j DNAT --to-destination 192.168.1.10

Repeat for each port you have forwarded.

Then enter the following ONE SNAT rule:

iptables -t nat -A POSTROUTING -d 192.168.1.10 -s 192.168.1.0/24 -j SNAT --to-source 192.168.1.1


Hopefully NAT Loopback will appear via a firmware update!