meteohub.de

HeinrichH wrote:To find out your public IP just go to this http://www.whatsmyip.org/ site and you know your IP.
With a good configured DynDNS account there should be no problem to use Meteohub on a remote location.
My station is in Portugal and I'm living in the Netherlands.

I have a great idea for a fix. Why don't you come to red rock country in Southern Utah and fix my weather station and I'll go to Portugal to fix yours!B)

Yes, great idea! I've been there once for vacation and it was great but my station in Portugal is running fine.
The other problem is that I have to work :-( but if you are in Portugal sometime, send me a mail

P3R wrote:

In my experience most home routers won't do that but normally it doesn't work as a test anyway since dropping such traffic (with the same source and destination address) is among the most basic security filtering any sane ISP should do.

Pretty much ALL linksys routers do local loopback as a default setting. Local loopback is the old Linksys terminology which I think they have re-named to something like NAT redirection (sometimes aka WAN IP local NAT Loopback). Within the Firewall settings on a Linksys router there maybe a radio button option to Disable NAT redirection which is supposed to allow traffic out to the internet and then back to the server on the LAN.

Now as to markebailey assigning a private IP to a DynDNS address, I didn't even think that was possible and frankly I've never heard of anyone doing that. I thought DynDNS would have filters on their address assignments to protect against that possibility. I thought wrong because I just tested that it is possible.

When setting up an address with DynDNS, they clearly offer the option of linking the new address to the current IP that is accessing the service. I'm not sure how markebailey missed that option on the set up page.

Basicly it's very easy to bring your internal network address available on the internet.
Two easy possibilities:
1) Create a DynDNS account with the IP number you've got from your provider, tell your router on the settings tab to use the account you've created Linksys call this DDNS and your router is available on the internet even if your given IP number is changing. To access your Meteohub you have to switch on the port forwarding, if you are using the standard port 80 I advise you to use another port because port 80 is normal a webserver port and all the search engines on the Web are continue scanning port 80 of IP addresses. Use port 88 or so in the network setup of Meteohub.
If your Meteohub IP is somthing like 192.168.1.15 you have to forward port 88 to this IP address and Meteohub is available at http://your DynDNS name:88
The second option is to use the DMZ (de-militarized zone) to route your internal IP direct to your public address without use of the firewall or NAT function of your router, this can be dangerous for hacker attacks.

To use this options best thing to do is to give your Meteohub a fixed IP number so your internal IP is not changing with a restart or a end of lease period of your router.

I'm using a Linksys WAG54G2 router, internet acces by ADSL and I'm using DynDNS, port forwarding and a fixed IP for Meteohub, it's working perfect

THANK YOU for all the generous help.

My ISP sent me the Torrey address along with this: "This is a dynamic IP address that could change every 12 hours as the modem authenticates to our servers. You may want to consider a Static IP address for $10/month or run a IP tracking program to monitor the address, if you plan on remotely logging on occasionally."

Perhaps dyndns.org is an IP tracking program?

I put the given IP address in my new dyndns account. I also tried the IP address from my browser in Salt Lake. Both timed out. Is there a way to get into my Torrey router from Salt Lake?:S :dry: :woohoo: :unsure: :unsure: :unsure:

markebailey wrote:THANK YOU for all the generous help.

Perhaps dyndns.org is an IP tracking program?

Yes, DynDNS is tracking your dynamic IP number.

If youve have enabled the web maintenace function you can reach you router by using port 8080, this is the standard Linksys port.

http://your DynDNS name:8080

Good luck!

HeinrichH wrote:

Yes, DynDNS is tracking your dynamic IP number.

Well only if DDNS is set up and enabled in your Linksys router. Eventually, as your ISP told you, your IP will change in Torrey. In the router, you will have to select the DDNS service, DynDNS.org; enter your DynDNS account user name and password; and the new host name that you have registered with DynDNS. Once enabled in your router, the router will then notify DynDNS whenever your Torrey IP changes so they can continue to track you. Properly set up, DDNS simply replaces the need for a static IP.

Chances are that you will have to visit Torrey to set this up unless you have remote management enabled on your router. This function often uses port 8080 by default on Linksys routers. I think this router function is not enabled by default as it would offer a potential security hole into your network.

Meteohub hi-tech helper dudes- You are generous. Thanks for your time and help. My Torrey router DDNs is enabled to send data to dnydns, but not to the right ip. I do not believe the remote management on the router is enabled. I have changed the domain name and IP at dyndns.org but I get no response when I browse for http://my-dyndns-name.dyndns.tv:8080 which seems to confirm remote management is not set up.

With all of your help I think I may now have the tools to set up the router correctly next time I am in Torrey. Yes, when setting up at Dyndns.org their screen starts with a local ip address and asks if you want to use an auto detected one instead. When I was setting it up I had no idea about one or the other being correct or local. Oh well. Torrey is a nice place to visit.

Dank u voor uw hulp! -Mark

You changed your dyndns address on the recommendation of P3R from what you originally entered in the router, correct?

Then the new dyndns address will have to be entered in the router as it is still updating the old address with whatever IP your router is receiving from your DSL ISP or the private IP if your DSL modem is issuing that to the router.

Possibly you might be able to access the router, if it has remote management enabled, by browsing to the actual IP that your ISP gave you rather than your dyndns address. This would be in the form of browsing to aaa.bbb.ccc.ddd:8080.

d_l wrote:You changed your dyndns address on the recommendation of P3R from what you originally entered in the router, correct?

Yes, I changed the DynDNS address as recommended by P3R. My router does not have remote management enabled, but thank you for the idea. I'll put the new domain name and a current public IP address into the router next time I am in Torrey.

Dank! -Mark

d_l wrote:Pretty much ALL linksys routers do local loopback as a default setting.

Okay, I didn't know that. Maybe I've been so focused on that it wouldn't work that I didn't even try it?

Local loopback is the old Linksys terminology which I think they have re-named to something like NAT redirection (sometimes aka WAN IP local NAT Loopback).

It's good that they renamned it as those names are way more descriptive.

Within the Firewall settings on a Linksys router there maybe a radio button option to Disable NAT redirection which is supposed to allow traffic out to the internet and then back to the server on the LAN.

Yes the Linksys may do that but as I said before, it wont work anyway because the traffic will never return, unless it's a crap ISP that don't use best practices in their router setup.

HeinrichH wrote:... if you are using the standard port 80 I advise you to use another port because port 80 is normal a webserver port and all the search engines on the Web are continue scanning port 80 of IP addresses. Use port 88 or so in the network setup of Meteohub.

Search engines aren't a threat but if you mean hackers in search of possible targets they will likely also try several other ports in the well known range (1-1023) and possibly a few among the registered ports (1024-59151). Changing from port 80 is always a good thing but if the reason is to become a less likely target for an attack, a random pick out of the private range (49152-65535) is really a much better choice.

The second option is to use the DMZ (de-militarized zone) to route your internal IP direct to your public address without use of the firewall or NAT function of your router, this can be dangerous for hacker attacks.

This is very dangerous as it makes the Meteohub a wide open honey pot for each and everyone on the internet. The so called DMZ-functions in home routers should never be used by anyone!!! DMZ is actually a very good thing when used in the original way but unfortunately the home router manufacturers kidnapped the term for their very risky implementation.

To use this options best thing to do is to give your Meteohub a fixed IP number so your internal IP is not changing with a restart or a end of lease period of your router.

I was trying to not overwhelm markebailey with information in my step-by-step-instructions but this is of course very good advice.

d_l wrote:

Chances are that you will have to visit Torrey to set this up unless you have remote management enabled on your router. This function often uses port 8080 by default on Linksys routers. I think this router function is not enabled by default as it would offer a potential security hole into your network.

Let's hope it isn't enabled and that it stays that way.

Having remote management enabled from the outside is extremely dangerous and isn't necessary once the router is setup correctly.

Before markebailey makes the long trip to Torrey, he should have a list of things to do and to test to make his system more robust and reliable down there.

1) The modem, router, and meteohub should be on a small UPS so that the system can survive short power outages that might mangle the network. He can decide how long of an outage he wants it to survive and how much to spend for that uptime. An NSLU2 meteohub won't reboot if there is a power outage unless he has made modifications to the circuitry.

2) Once he has set everything up so it is ready to be unattended, he should test the system by disconnecting and then reconnecting the phone jack to simulate a DSL IP change. Also he should pull the power plug on the UPS briefly to test for a power outage and the UPS's power to the devices.

I'm sure there are other things needed but I can't think of them off hand.

That's a great point that the NSLU2 doesn't reboot after power is off. Too bad. The modem and router do reboot with switches that stay in the on position. A UPS is a good idea as a band-aid. The rural power in Torrey is sketchy.

I'll pull the phone cord as well as the power cord as tests. Thanks for the tips. I'll take whatever tips you can think of. It is too long a trip to Torrey to take just to push the power button on the meteohub.