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

DDNS External IP Address Checker: How?

Discussion in 'Tomato Firmware' started by delajed, Jul 13, 2009.

  1. delajed

    delajed Addicted to LI Member

    I'm just wondering what I need to do to make this feature work?

    Right now I'm trying to gain remote access to my wireless bridge. I'm using a dynamic dns service, to keep the ip address valid. I can get it to run fine on my actual access-point (router), using the WAN address.

    Since WAN is disabled on the bridge this wasn't an option, so I was wondering how to get the external ip address checker option to actually work?
     
  2. fyellin

    fyellin LI Guru Member

    I'm slightly confused as to what your set up is. What is your connection to the WAN?

    To answer some questions that you didn't ask:

    1) In general, the role of a ddns service is to keep track of your WAN address, when this address is something that's dynamically assigned to you. It doesn't keep track of your internal network.

    2) If you're trying to reach a computer on your internal network, this is done via port forwarding on your router. The machines you need are assigned static IP addresses within your LAN so that they have a fixed internal address.

    3) The external IP address checker works by contacting an address such as checkip.dyndns.org. This returns the value of the IP address that contacted it. It has no concept of any NAT that happened within your local network.

    So it's possible I'm completely misunderstanding your question. I'm not sure why you're using DDNS on a machine not attached to the WAN.
     
  3. delajed

    delajed Addicted to LI Member

    My setup is as follows:

    1. Access Point connected to a modem.
    2. Wireless Bridge connected to the Access Point (both running Tomato)

    What I'm trying to do is log into the bridge remotely because of WOL. The PC I'd like to wake up on demand is hard-wired to it.

    For some reason, using the MLPPP (1.19) version of Tomato allowed me to wake it up from remote access to the main access point. Again, using DDNS to update my IP. However, updating to the latest vanilla Tomato firmware I have been unable to do the same.

    I could however log into the bridge locally and WOL from there. So I was thinking that the solution to my problem would be having remote access to the bridge. I've set up my dyndns settings properly, but for some reason am unable to get an IP from the DDNS screen - leaving me unable to get proper remote access.
     
  4. fyellin

    fyellin LI Guru Member

    You're going to need to set up a a port forwarding on your access point. Something like: External Port 81 goes to Internal Port 80 of IP Address <Internal IP address of your bridge>

    That said, I think what you're doing is a bad idea. Allowing WAN traffic to access either your AP or your Bridge is just asking for trouble. If port 80 or port 81 is open to the outside world, I can guarantee that someone is trying to crack it. Your better bet is to use ssh to log into your machine and set up a tunnel.
     
  5. jan.n

    jan.n Addicted to LI Member

    If I get you right do this: connect to your router using its DDNS address and from your router you connect to your wireless bridge using its LAN address...
     
  6. delajed

    delajed Addicted to LI Member

    Thanks. Can you point me to a guide explaining ssh/tunnelling on Tomato?
     

Share This Page