Loss of access through dyndns

[oliverb]

Since upgrading to 3.3 on my NSLU2 I have lost access to meteohub via my dyndns.

The manual says" 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."

My router has all the details for my dyndns access set and working so I have left this set to mone. Is this why I have lost access?
Brett.

[P3R]

No, if your router does the dynamic dns stuff the Meteohub shouldn't. If you're sure the router is doing it right there must be some other problem.

Perhaps there's a change between the previous version you ran and 3.3? Check the release notes and compare documentation between the two. Double-checking the router's port forwarding configuration is another tip.

[oliverb]

One of the main changes is Meteohub supports dyndns.
This is why I was wondered if this could be the problem.
Can anyone confirm if dyndns works on 3.3 on the NSLU2?

My web cam still works through my router via dyndns so I presume the settings are fine.

The only thing that has changed is I installed meteohub 3.3.

[P3R]

One of the main changes is Meteohub supports dyndns.
This is why I was wondered if this could be the problem.

No, it shouldn't be a problem as long as you keep it turned off in Meteohub.

[oliverb]

Too late I have already tried turning it on in Meteohub. Can access my NSLU2 at all now.:(

edit know how I can get access to turn it off agian?

[oliverb]

Managed to get back into Meteohub. My Hub had assigned it to another IP address. I have now disabled dyndns and meteohub is now set as it was when I started. This time however dyndns acces now works.

[admin]

When your router does not assign fixed IPs based on the cleint MACs, I would suggest to set Meteohub to a static IP (switching DHCP off, and settting DNS and Gateway manually).

The dyndns switching did no harm to your setup. But the automated reboot after having installed the update gave your router a chance to hand over a new LAN IP to meteohub. Whith the next reboot, this might happen again, unless you switch off DHCP at your Meteohub.

[oliverb]

My router has given my Meteohub a static IP address of 192.168.1.67. My meteohubs is set to DHCP and the greyed out settings confirm this address.

All was fine until the midnight reboot when it lossed connection again and now shows no internet access.
Any ideas?
My router can see my Meteohub.

edit I can't seem to set my own IP address from Meteohub. If I disable DHCP and enter my own address it just changes back to 192.168.1.67 even when I delete it from my router.

[admin]

I suggested to set DHCP off for the Meteohub.

Please consult your routers pages to find out what IP it has given Meteohub this time.

Some routers do not provide all Info (Gateway/DNS) so Meteohub does not get all info needed to connect to the outside world.

So disabling DHCP for the Meteohub is the way to go.

[oliverb]

Have disabled DHCP on meteohub and left the IP as it was. Deleted it on my router and let it find it again. It found meteohub OK and has assigned the same IP as set in meteohub. Meteohub WAN IP still says "no internet access".

Also I now can't forward my meteohub ports after disabling DHCP in meteohub.

It all work fine originally with this router. Do you think it is worth reseting the router to default settings and starting again. I notice my IP cam keeps losing it's name on the router. Never did that before. Meteohub lost it's name a few times as well.
Thanks Brett.

[admin]

Hi,
your router should be ok.

Please do with Meteohub:
1) unmark DHCP
2) insert IP
3) insert Mask (255.255.255.0)
4) insert Gateway (the LAN IP of your Router)
5) insert DNS (mostly the IP of the Gateway)
6) press save, ignore what data gets displayed.
7) Reboot.

If it then shows again "no internet connection" please post "System information" page to me.

[oliverb]

Enclosed "System info page"

[admin]

set gateway to 192.168.1.254 as DNS (your router provides both, gateway and DNS)

[oliverb]

Thanks for your help. All seems to be working now including dyndns acces.
:)