Meteohub dyndns through a router

[bobball]

With little knowledge of dyndns and port forwarding, I've somehow managed to access, most of the time, my router and NSLU2 when I'm away from home. It was useful, for example, when TH0 failed while I was vacationing; I was able to specify my backup TH1 for data forwarded to WUnderground.

I've turned on DYNDNS functions both on the NSLU2's and the Linksys router using DD-WRT, and turned on port forwarding in the Linksys, although I'm dense enough not to know if it's the Linksys proviiding me with access to Meteohub or the NSLU2/Meteohub itself.

I'm considering replacing the router with an Apple Airport Extreme, which doesn't support DYNDNS. Question: Do other users have success with the Meteohub use of DYNDNS, and can it operate through a router? Forgive the ignorance of this subject, and the possible ignorance as I try to grasp the answer.

[HeinrichH]

You have to turn on DynDNS only in your router, one place is enough because your NSLU give his own IP number (internal) to DynDNS.
To reach your Meteohub you heave to turn on port forwarding in your router, standard Meteohub uses port 80.
When that's done you can reach your meteohub simply by typing your DynDNS name like this http://yourDynDNSname.
When using port 80 you don't have to type the port number after your address, when your Meteohub uses another port you must type the number after the address like this http://yourDynDNSname:1022
Port 1022 must be forwarded to the internal IP address of your Meteohub.

[bobball]

I wasn't clear: The router I wish to buy, an Apple "Airport Extreme," can do port forwarding but lacks the DDNS implementation. I cannot tell it to monitor my WAN address and keep dyndns informed of that address and its changes when I'm away from home.

Meteohub at the moment is correctly displaying my WAN address, 66.227.226.132. Can its dyndns implementation successfully tell dyndns, through my new router, to point "bobball.ham-radio-op.net" -- my dyndns domain -- to my WAN address?

If no, is it possible to place a cheap router which does have DDNS capability between the NSLU2 and the new router?

[YJB]

You might be able to create a script and install that on Meteohub. I guess that some of the generic DynDns xnix utils will work (http://www.dyndns.com/support/clients/unix.html).

The other thing that you can do, is let the box that is running meteohub send you an email when the ip address changes. This is not going to update your dyndns account, but at least you know how to get to it.

[P3R]

There should be only one instance of DynDNS-configuration and it is always preferred to have it in the router/firewall connected to the WAN.

Since I try to follow the above advice myself I haven't tried it, but it's probably okay having the Meteohub do the DynDNS-stuff instead. Especially since it does seem to correctly sense your external address. By the way, don't expose your WAN IP address on a public forum unless absolutely necessary.

Since I had to help a friend that had bought the Airport Extreme I noticed it isn't very good to work with. Unlike every other router in the universe (well almost) the Airport Extreme can't be administered through a web-inteface. As far as I could find out instead you had to have a special application installed to configure it. Also the configuration wasn't in any way logical or intuitive. It's a beautifully designed piece of equipment but really awkward to work with. Unless it has some other special feature that's important to you I'd recommend you to also have a look at similar products from other well known manufacturers. If you do, you could also add DynDNS-capability as a requirement.

If no, is it possible to place a cheap router which does have DDNS capability between the NSLU2 and the new router?

That would be no improvement at all (it can be worse though) compared to having Meteohub do it. If going down that road it would be much better to have it in between the WAN and the Airport Extreme.

[bobball]

Thanks for the responses. I'm leaning toward the Apple product in part because it's a dual-band device capable of providing guest Internet access. I'm not put off the the interface, I've used it on an Apple Time Capsule and a few Airport Express modules. A more compelling reason: My daughter gave me an Apple gift certificate for Christmas.
But to go back to the NSLU2/Meteohub: Is Meteohub's use of ddns, and inclusion only of dyndns in the dropdown box, intended to operate through a router to tell dyndns what the WAN address is? And does it work?

An aside on posting my WAN address: I never gave it a thought, but the warning reminded me of the response I got when I carried a 20-pound liquid propane gas bottle into a store to have it refilled. My ignorance was about the same.

[P3R]

Thanks for the responses. I'm leaning toward the Apple product in part because it's a dual-band device capable of providing guest Internet access.

Several others can do that as well.

I'm not put off the the interface, I've used it on an Apple Time Capsule and a few Airport Express modules. A more compelling reason: My daughter gave me an Apple gift certificate for Christmas.

Those are of course very good reasons to stick with your original choice.

But to go back to the NSLU2/Meteohub: Is Meteohub's use of ddns, and inclusion only of dyndns in the dropdown box, intended to operate through a router to tell dyndns what the WAN address is?

Quoting from the Meteohub manual: "Meteohub supports dynamic domain name service "dyndns.org". Please use this service only in combination with a modem connection or if your router does not provide dyndns services itself."

And does it work?

I haven't tried it but I'd says the odds are pretty good since you're saying that it does correctly sense your WAN IP-address.

Since your plan is to have a router that doesn't support DynDNS I'd suggest disabling it in your current router and enable it in Meteohub to test it for a while. If it works for you now it is almost certain to rock with the Airport Extreme as well.

Of course you may not know if it is working until your router gets a new WAN IP from your ISP. Depending on their setup it may happen frequently or almost never, YMMV.

An aside on posting my WAN address: I never gave it a thought ...

Don't be alarmed as this wasn't that much of a risk. I just wanted to give you and others in the forum some friendly advice about being very careful with what you reveal on the net, and at least not post any vital information unless absolutely necessary.

[P3R]

Sorry