TomatoUSB

Hey guys,
I just setup Tomato successfully on my RT-N66U router this past weekend, and everything is working… except port forwarding.

- This WAS working on Friday just before my old router gave up the ghost. So I know my ISP IS NOT blocking port 80 (they don't block any ports actually)
- I have flushed my NVRAM (both via hardware and tomato interface).
- I added the forwards via the web interface, NOT iptables.
- When I do an iptables —list -v -n I see the Wanin chain and the 3 port forwards I setup exist. I don't however fully understand iptables, so I could (most likely have something wrong)
- When I test the website from within the network it loads as expected.
- Web management interface is set to https only (so it shouldn't be reserving port 80 if I understand correctly?)
- I've setup DDNS, and can find the router and manage it remotely as desired (with https and the configured port)

The problem:

I need to be able to have my DDNS forward port 80 to my internal web server… preferably on port 80.

Currently, when I try the DDNS address with no port specified I get a response from *a* Apache web server saying "Service Temporarily Unavailable" answering on port "3128".

Here's the odd part… I have no linux box running Apache (other then Tomato itself).

Do I need to modify apache to relinquish port 80 so that it can forward it correctly, or is there something I'm missing?

Here's a link to both exports of the iptables commands:

www DOT hammerandfist DOT com/ipt_list_v.log

www DOT hammerandfist DOT com/ipt_list_v_n.log

Any help is appreciated!

- Spyrule

Nope.

Have you changed the port the TomatoUSB gui runs on? By default, when you go to your broswer ie 192.168.1.1, this always defaults to port 80. In order to be able to port forward 80 to another server, you need to change the port the tomato web page runs on. The tomato web page can't run on port 80 and forward port 80 to another pc at the same time.

I've set the routers management to https only on port 443, and remote management on another alternate port with https only. So I'm presuming that's all I have to change?

If not, where can I check this to make sure?

Is there something in the CLI that I can check to confirm this other then iptables ?

edit: Why am I not getting emails about this thread updates? I've subscribed and "watching" this thread with no joy. I hate custom forums. argh!

anybody?

Ah, now saw that you mentioned first that the tomato gui is running on not port 80.

I'm inclined to say there's an issues with the dyndns setup. Tomato does not run Apache. Not unless you explicitly are running apache with optware/entware. I think this is not the case though, so I think you dyndns is pointing somewhere else. What happens when you type your IP address instead of you ddns domain name? (with port forwarded). Can you confirm that ddns is working correctly. If you run 'ping youddns.com', does it show your actual ip?

Yes,

the DDNS is working, as I can connect to my router on it's remote https port, plus my public IP matches what my DDNS shows in the online profile. So I'm highly doubtful that, that is the problem. Also, just prior to this router (RT-N66U) I was using a dlink DIR-615 with the same DDNS account info and I never had issues.

I'm seriously thinking it is my port forwarding conflicting with something else.

I've gone as far as using PFPortCheck app to test the port, and (for testing), I've enabled WAN side ping, and it responds, but the port is always closed. I've also tried alternative ports to no avail.

I've flashed back to ASUS firmware, did a full NVRAM reset, then a 30-30-30 reset, then powered off. Flashed back to Tomato, again another 30-30-30 reset, used the interface command for a thorough reset as well, and then re-setup the router. Sadly, the problem persists.

I'm tempted to switch to DD-WRT just to test the port forwarding to see if it's tomato or not, but I'd rather get this working, since everything else is working as expected.

Cheers!

Actually, I just tried something new, and I think I've narrowed it down.

It seems the real issues is port forwarding to a device connected via wifi.

If I change my port forward to point to my desktop, and run a basic service on it. the port forwarding works as expected.

But, when I attempt to connect to another device that is joined the network via wifi, the port forwarding fails (the device IS working though if I connect via IP internally).

Is there a way to work around this?

Just to clarify,

the pattern that works :

Modem > Tomato Router >— - [ cable]—-> Desktop PC works!

fails :

Modem > Tomato Router > … [wifi] … TPLink Wifi Bridge >— - [ wired]—> WebServer

If I load the page inside my network, the WebServer loads (which means the bridge is working as expected).
The bridge does NOT have any firewall or other methods to block ports/etc. Its running in true straight wifi pass-through mode, and is a complete slave to the router.

So, it has to do with either port forwarding blocking any forwards to WLAN 0/1 or the firewall service blocking port 80 calls to the WLAN.

Any help/suggestions are seriously welcome!

Spyrule

Problems with DHCP over wifi leads me to believe the problems might be related.
"Keith Sibson (guest) 17 Aug 2013, 18:57
I had the same issue until I changed the encryption to WPA Personal, it simply didn't like WPA2. Best bet is to get it working without any security, then enable it later. Also, I set it up in Wireless Client mode instead of Bridge mode, which was a little simpler to set up. The only difference is that in client mode your non primary router is on a subnet, which for practical home networking makes no difference. There's a good howto on wi-fiplanet.com, search google for tomato bridge dhcp"
Also Teddy Said:
"Did you specify your main router's IP address as the "Default Gateway" and "Statis DNS" (in the Basic->Network->LAN section) on your client router? Also, set "Advanced->Routing->Mode" to "Router"."