1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Can't host servers or use remote access

Discussion in 'Tomato Firmware' started by joe012594, Apr 19, 2014.

  1. joe012594

    joe012594 Reformed Router Member

    I'm having a major issue I can't seem to figure out. I'd like to be able to host some servers and be able to use the remote access feature but I'm not able to. Hope someone here could help. Here's my setup.

    LTE Hotspot (tethered USB) > RT-N56U stock firmware > RT-N66U TomatoUSB (plugged into LAN)

    I've read that having multiple NATs can cause this issue. Since the phone already has NAT, would I need to disable NAT on both routers? I've also read that some sort of port forwarding needs to be done to access router behind another router. How do I go about setting this up properly so I can host servers over WAN and be able to remotely access the router's GUI through the WAN? Lastly, would something like DDNS help in this situation at all? Thanks in advanced! :)
     
  2. gfunkdave

    gfunkdave LI Guru Member

    Uhhh...why on earth do you have so many routers behind each other?

    You'd need to configure port forwarding on all of them. But it's likely you just can't host servers if you're using a cellular connection. You probably have a private WAN IP, and if so you're out of luck. That's the first thing to check.
     
  3. joe012594

    joe012594 Reformed Router Member

    Because it's the only way I've been able to get my internet access working. It's not like this type of setup is a common one. If I had guidance on how to properly set it up, I would do so. Also, I have to use multiple routers because stock ASUS firmware doesn't have the bandwidth cap/limiter feature like TomatoUSB does, but TomatoUSB also doesn't support USB tethering for my device while the stock ASUS firmware does. I have to use the stock ASUS firmware for tethering then the TomatoUSB firmware to cap the LAN bandwidth to avoid tower congestion and throttling.

    Also, the device has a public IP of 172.x.x.x and a Gateway IP of 100.x.x.x. Does it matter? Could I just use DDNS to get around any WAN IP issues?
     
    Last edited: Apr 19, 2014
  4. Grimson

    Grimson Networkin' Nut Member

    Well if your LTE Hotspot does NAT you need to put the RT-N56U into its DMZ or forward the required ports to the RT-N56U.
    You'll also have to put the RT-N66U into the DMZ from the RT-N56U and then forward the ports on the RT-N66U to the target devices.

    AFAIK Toastmans, Victeks and Shibbys builds do support USB modems.

    But without more information about your "LTE Hotspot" it's hard to say what works and how.
     
  5. joe012594

    joe012594 Reformed Router Member

    Ah ok. Well, if it helps at all, my device is an HTC Vivid. Is there anyway to add in the proper USB support for that device?
     
  6. gfunkdave

    gfunkdave LI Guru Member

    If your LTE device has a public IP of 172.16.0.0 to 172.31.255.255, you won't be able to access it from the internet. That's a non-routable IP range. For further info see http://en.wikipedia.org/wiki/Private_network.

    Well, you COULD access it in the manner you want, but you'd need to get your cellular provider to manually open a port in its network to your device, and the chances of that are slim to none. In general, all cellular ISPs operate this way. They really don't want people operating servers over a cellular connection.

    If hosting servers is important to you, you'll need to get a new ISP or move the servers you want to host into the cloud.
     
    Last edited: Apr 20, 2014
  7. joe012594

    joe012594 Reformed Router Member

    I just tested to see if any connection could be established to the "External WAN IP" at 172.x.x.x and ping tests all failed with 100% packet loss. However, the "Internal WAN IP" could be reached with 0% packet loss from a completely different WAN connection I had access to. So, could this mean I can establish a connection to my network from outside of the WAN or no? If no, then what are my options? Would DDNS work?
     
  8. joe012594

    joe012594 Reformed Router Member

    Actually, the IP for my device is 172.56.x.x and the range is 172.32.0.0 to 172.63.255.255. Also, I have confirmed that, although the 172.56.x.x IP is completely locked down, the other WAN IP 100.x.x.x assigned to my device is very much available according to a few ping tests I ran from a completely different/separate WAN.
     
  9. Grimson

    Grimson Networkin' Nut Member

    The 100.x.x.x IP is your gateway and not your WAN IP. And of course the gateway is reachable from WAN, but that won't help you. And as port forwarding on android phones isn't reliable, if it works at all, you'll need a different ISP like gfunkdave already posted.
     
  10. joe012594

    joe012594 Reformed Router Member

    Getting a different ISP is not an option. Trust me, I would if I could. There's a reason I'm stuck with using tethering and relying off of it isn't all rainbows and unicorns, but it gets the job done. Now, if I can't host servers the old fashioned way, then how about DDNS or some other work-around method? Would that help me at all or do I have no choice but to have my servers hosted professionally?
     
  11. gfunkdave

    gfunkdave LI Guru Member

    DDNS will just provide a domain name for your publicly facing IP. It won't change settings in your cellular provider's routing equipment to allow you to do what you want. I think Amazon EC2 or Rackspace are in your future. :)
     

Share This Page