Page 1 of 1

Offsite Access Guide?

Posted: Tue Mar 31, 2009 5:37 pm
by AAMFlyer
Just wondering if anyone out there can take a few mintues to write or post a quick guide on how to access your meteohub from offsite or another location?

I know I have to forward ports 22 and 7777 on my router....but just not sure how to access it from that point....is it done only through ssh or can it be done through IE which I hope you can? Address for that? This is just one of many areas I'm not very familiar with and would like the ability to access the meteohub to perhaps do updates etc...

Thanks!

Re:Offsite Access Guide?

Posted: Tue Mar 31, 2009 6:45 pm
by d_l
To access the Meteohub's GUI remotely through port 7777, you of course have to forward port 7777 to your Meteohub's IP on your LAN. If your router allows it, it might be better to forward an alternate port number such as 27777 to port 7777 on your Meteohub. The reason for this is that there are some trojans that operate on 7777, but 27777 is presently a trojan free port (at least for the present).

You also need some way of keeping track of your router's IP if you do not have a static broadband account. A DDNS service such as DynDNS.com will do this for you and your router should be able to update the DDNS service with its IP.

So once you set up your DDNS account, you would access your Meteohub's GUI remotely by entering something like mywebaddress.ddns.com:7777, mywebaddress.ddns.com:27777, or whatever port address you chose in IE and you should be able to see it.

Normally after you think you have set everything up to work remotely, it is best to do a dry run before leaving for a remote site. If your DSL ISP has dial up back up, try a dial up access of your Meteohub as a test. I don't know what cable ISPs use for back up. Invariably something always needs to be adjusted/tweaked before a remote access works perfectly. :) Better to do it from home than having to return from the remote site.

Re:Offsite Access Guide?

Posted: Wed Apr 01, 2009 4:27 pm
by AAMFlyer
Thanks - got it to work on 7777....although I'm not sure I understand on how to forward a port to a port...if you forward 7777 to the ip address of your meteohub your opening it up regardless - unless you can forward any port to the meteohub address?

Re:Offsite Access Guide?

Posted: Wed Apr 01, 2009 6:13 pm
by skyewright
AAMFlyer wrote:Thanks - got it to work on 7777....although I'm not sure I understand on how to forward a port to a port
Different routers have different capabilities. Not all offer the facility to do that sort of thing.

Re:Offsite Access Guide?

Posted: Wed Apr 01, 2009 6:18 pm
by d_l
Only some routers have the ability to forward an external port to a different internal port on the LAN and many only allow this for one internal port, e.g. port 8880 forwarded to only aaa.bbb.ccc.ddd.:80 instead of allowing something like both port 8880 forwarded to aaa.bbb.ccc.ddd.:80 AND port 8881 forwarded to aaa.bbb.ccc.eee.:80.

Thus if you have two devices on your LAN that you want to remote HTTP access, you are out of luck unless you expose one to all the prying and common port 80 traffic on the web. It was a good decision by Boris to provide a alternate port for HTTP access. Port 7777 is relatively free from trojans, isn't commonly used for HTTP access like ports 80, 8080, etc., and it solves the problem that some routers don't have that "port forwarding translation" feature.

Most Linksys routers that provide the "port forwarding translation" feature "hide" the set up screens on the UPnP set up page. It isn't really UPnP, but they just put it there. I don't know how other router maanufacturers handle it.