I think I know what is going on. I put this into different issues, so that it is easier to address.
** Issue one **
Here are some notes about listening:
a) If you are on Windows I point you to http://www.howtogeek.com/howto/28609/how-can-i-tell-what-is-listening-on-a-tcpip-port-in-windows/
b) If you are not on Windows (Mac, Unix/Linux), go look lookup listen on port and then your OS name using Google (or your other favorite search engine).
c) If nothing is listening any TCP ports that you check with a web based port checker, then TCP ports does not show up as open.
d) Be advised that you can not have two servers listening on the same the port on the same computer. So for example before you use an inbond-client side port checker you must make sure that uTorrent is not running - which explains on http://portforward.com/softwareguides/utorrent/utorrent.htm that they say
If uTorrent is currently open, you will need to completely close it at this time. Make sure that the green uTorrent icon is not still hiding in your notification area (next to your clock). If it is, right click on it and choose "Exit". Before moving forward to things like selecting torrents, seeders, and leachers, we need to verify that your port is open. We recommend downloading our free Open Port Check Tool to test if incoming connections are being allowed through your router on your uTorrent Listening Port
e) And generally if the program/app is running that you are trying to forward for, then the server is listening.
** Issue two **
For example with my router..
#1 With loopback set to ALL, if I enter my IP Address or Domain name that points to the Public / Route+able / True WAN IP Address - when I am behind this router, it is as remote control of the router is turned on.
#2 With loopback set to OFF/Disabled, if I enter my IP Address or Domain name that points to the Public / Route+able / True WAN IP Address - when I am behind this router, I can not connect to anything.
#3 With loopback set to Forward Only, if I enter my IP Address or Domain name that points to the Public / Route+able / True WAN IP Address - when I am behind this router, and if I am running a web server - I can connect to my web server.
It has a UI that looks something like what you see at
http://victek.is-a-geek.com/virtual/tomatok26/advanced-firewall.html#4 I have to say that not all routers support:
a) loopback
b) loopbask the same way. There are others with it is only allowed (ALL) or Filtered (OFF).
For example of All of Off, the Linksys E4200 hardware version one with Linksys official firmware (that has a UI that looks like what you see at
http://ui.linksys.com/E4200/2.0.25/firewall.html )PSST/Hint also could called
Internet NAT Redirection instead of
Loopback.
#5 Besides a client side port checker, there is a client side Loopback/Internet NAT Redirection/Reverse NAT tester.
It is addressed at
http://www.pcwintech.com/test-for-reverse-nat** Issue three **
Your LAN IP Address of your routers should always be RFC 1918 complaint. This means that they should be in one of these three ranges:
a) 10.0.0.0 to 10.255.255.255
b) 172.16.0.0 to 172.31.255.255
c) 192.168.0.0 to 192.168.255.255
** Issue three part b **
Since there is more than one NAT router, you could have one at 192.168.0.1/24 and the other at 192.168.1.1/24