I have been able to test the WAN side in 3 different ways, I am quite certain this is no loopback related issue; besides, problematic rules have already observed in the previous posts. Hence my conclusion.
I finally was able to take the time to try just that, and am sad to tell you that I have done just the above, and that port 80 and the administration pages were immediately available from the wan after :
-NVRAM clear (wps + on)
-flashing Shibby's tomato
-wiping with Shibby's
-flashing...
I am currently at work and will test as soon as I can.
I did reboot the Asus several times, flash and clear the NVRAM without any changes to the behavior : I will attempt more severe resetting, possibly by flashing Shibby's, using its thorough NVRAM wipe, and reflash back your firmware...
My goal it to set OpenVPN to port 80 : It was set on port 80 on the first iptables -L -v.
I set it back to 1194 and posted the result from http://forums.smallnetbuilder.com/showpost.php?p=106956&postcount=45 : Admin is still accessible from the WAN side.
I'm afraid this is not crucial to...
Alas the router's version of netstat does not know -p :-( It understands :
-r Routing table
-a All sockets
-l Listening sockets
Else: connected sockets
-t TCP sockets
-u UDP sockets
-w Raw sockets
-x Unix sockets
Else: all socket types
-e Other/more information
-n Don't...
To be more complete, I tested the behavior :
- both Merlin's 3.0.0.4_374.39_0 and Asus's 3.0.0.4_374_4561 firmwares,
- both with my current settings and right after a NVRAM clear (On+WPS), which I did after each flashing.
Each time the bug was present.
This was the setup I originally wanted, port 80 being able to go through most restrictive connections, and TAP being my favorite.
The problem occurs even when OpenVPN is on its default port, 1194 : port 80 still gives you access to the Asus's Admin page, not an OpenVPN related port.
The...
Sorry, I'll try to be more clear :
my initial configuration was :
[ISP's router] -> 192.168.0.x -> [ASUS] -> 192.168.1.x -> LAN
I did this for testing purposes, to be able to configure the Asus without exposing it to the Internet.
Then a few posts later, to be able to scan the Asus from...
yep, here my ISP's router can be configured as a bridge (hands the external IP to one single device), or as a full NAT router. This way I can test both configurations :-)
Sorry, I'll try to be more clear :
my initial configuration was :
[ISP's router] -> 192.168.0.x -> [ASUS] -> 192.168.1.x -> LAN
I did this for testing purposes, to be able to configure the Asus without exposing it to the Internet.
Then a few posts later, to be able to scan the Asus from...
- On my ISP's modem/router, NAT is disabled. It justs hands my external IP to he WAN side of the ASUS.
- On the Asus, NAT is enabled, the PC I'm on is currently plugged on the LAN port of the Asus, with an IP of 192.168.x.X
the setup is currently :
[ISP's Modem] Lan port -> WAN port...