DDNS connection

[fraumo]

Hello

I have a strange situation

I connect my lacie every morning
I have a DDNS adress and I connect from another pc
Then 1 hour later I loose my connection (I dont have cron jobs active during the morning)
When I arrive home (lunch time) I acess to the nas via the IP
I restart the nas and I get acess again via DDNS
During the afternnon I have allways the acess

I loose all days in the morning the acess to my nas but during the afternnon I dont have problems

Any idea?

Thanks in advance

[Jocko]

Hi fraumo,

Some questions:
- do you have a dynamic or not public address ?
- do you update your ddns by using the firmware feature or your ISP box feature (I advice not to enable in the same time the both features).
- Before rebooting (lunch time), you should check on what public IP address, your DDNS relies (in the firmware menu and in the provider's web site). I assume that the public IP address will be wrong at least on the provider's site.
- what is your DDNS provider and what firmware version do you use (before version 15.0, the firmware detected some times a wrong public IP)
- if you use the firmware feature what is DDNS Period

Otherwise, I don't understand well this

Code: Select all

When I arrive home (lunch time) I acess to the nas via the IP

what IP address do you talk : local IP or public IP? If it's the public IP address, I assume that it's the same than this one of the morning.

[fraumo]

Hello


Some questions:
- do you have a dynamic or not public address ? - I have an adress from no-ip

- do you update your ddns by using the firmware feature or your ISP box feature (I advice not to enable in the same time the both features). - firmware feature

- Before rebooting (lunch time), you should check on what public IP address, your DDNS relies (in the firmware menu and in the provider's web site). I assume that the public IP address will be wrong at least on the provider's site.

- what is your DDNS provider and what firmware version do you use (before version 15.0, the firmware detected some times a wrong public IP) - no-ip , version 15.0


- if you use the firmware feature what is DDNS Period - 29

Otherwise, I don't understand well this
Code:
When I arrive home (lunch time) I acess to the nas via the IP
what IP address do you talk : local IP or public IP? If it's the public IP address, I assume that it's the same than this one of the morning. - I use 192.168.1.75 and not the no-ip adress


I hope you can understand better my problem , I realise is not easy to understand

[Jocko]

I read again your two posts, could you confirm this point:
When one hour later, you loose your connection, you mean that no access is available via DDNS but you still have an access via your local IP.

So if it's only an issue with the DDNS feature, your problem is strange.

To understand what happens, still need some informations. So next time when you will fail to use your DDNS :
- check what is your current public address (information get from the web-interface of your ISP box)
- check what IP is saved with your no-ip account (https://www.noip.com/members/dns/). See also the last update time
- check what is the DDNS status on the DDNS menu of fvdwsl.
If there is an issue with the firmware, it will be useful to have syslog information. So run the syslog daemon.

Code: Select all

syslogd

and when the DDNS will fail, don't restart the NAS before saving the syslog file :

Code: Select all

cp /var/log/messages /share/1000/fvdw

In the messages files, you should find these lines at each 29 min:

Code: Select all

Feb  5 22:36:44 (none) user.notice /usr/bin/ez-ipupdate[1179]: try to connect to ip-detection server checkip.dyndns.org:80
Feb  5 22:36:51 (none) user.notice /usr/bin/ez-ipupdate[1179]: ip address found in server response: xx.xx.xx.xx

Note sometime, you could have this error (but few):

Code: Select all

Feb  5 22:36:14 (none) user.notice /usr/bin/ez-ipupdate[1179]: (your DDNS) unable to resolve interface web-detect

Note : I have also a no-ip account, I will test it on my 2d nwsp2

[Jocko]

I began to use my no-ip account and currently no issue :

Code: Select all

Feb  6 19:11:38 Shaula user.notice /usr/bin/ez-ipupdate[1443]: ez-ipupdate Version 3.0.11b8, Copyright (C) 1998-2001 Angus Mackay.
Feb  6 19:11:38 Shaula user.notice /usr/bin/ez-ipupdate[1443]: /usr/bin/ez-ipupdate started for interface web-detect host kappa-ftp.no-ip.biz using server dynupdate.no-ip.com and service noip
Feb  6 19:11:38 Shaula user.notice /usr/bin/ez-ipupdate[1443]: cache date: 0
Feb  6 19:11:38 Shaula user.notice /usr/bin/ez-ipupdate[1443]: cache IP: (null)
Feb  6 19:11:38 Shaula user.notice /usr/bin/ez-ipupdate[1443]: malformed cache file: /var/cache/ez-ipupdate/default-cache (<= this is a normal warning)
Feb  6 19:11:38 Shaula user.notice /usr/bin/ez-ipupdate[1443]: try to connect to ip-detection server checkip.dyndns.org:80
Feb  6 19:11:39 Shaula user.notice /usr/bin/ez-ipupdate[1443]: ip address found in server response: 86.221.149.217
Feb  6 19:11:39 Shaula user.notice /usr/bin/ez-ipupdate[1443]: hostname =xxxxxxxxxx.no-ip.biz
Feb  6 19:11:39 Shaula user.notice /usr/bin/ez-ipupdate[1443]: IP addres = xx.xx.xx.xx
Feb  6 19:11:39 Shaula user.notice /usr/bin/ez-ipupdate[1443]: request = GET /nic/update?hostname=xxxxxxx.no-ip.biz&myip=xx.xx.xx.xx?
Feb  6 19:11:39 Shaula user.notice /usr/bin/ez-ipupdate[1443]: dynupdate.no-ip.com says that your IP address has not changed since the last update
Feb  6 19:11:39 Shaula user.notice /usr/bin/ez-ipupdate[1443]: successful update for web-detect->xx.xx.xx.xx(xxxxxxx.no-ip.biz)

Feb  6 19:21:39 Shaula user.notice /usr/bin/ez-ipupdate[1443]: try to connect to ip-detection server checkip.dyndns.org:80
Feb  6 19:21:40 Shaula user.notice /usr/bin/ez-ipupdate[1443]: ip address found in server response: xx.xx.xx.xx

Feb  6 19:31:40 Shaula user.notice /usr/bin/ez-ipupdate[1443]: try to connect to ip-detection server checkip.dyndns.org:80
Feb  6 19:31:40 Shaula user.notice /usr/bin/ez-ipupdate[1443]: ip address found in server response: xx.xx.xx.xx

....


[Jocko]

Hi Fraumo,

After one day, my no-ip DDNS is still available :scratch

Could you check the credential that you use? Currently no warning is displayed if it is wrong (fixed in 15.1)

[uelpenich]

Hi Friends,
I prefer to use the ISP box feature (I have an AVM Fritz Box 7270), because the ISP box knows first the reconnection to the service provider and sends immediately the new IP adress to no-ip.

Werner

[Jocko]

Still I have no issue with my no-ip account after 48 hours.

[fraumo]

Hello
I haved made the update to new firmware version and I dont have this problem anymore

I dont understand whats happen but I think is solved

Thanks anyway

[Jocko]

Hi fraumo,

Glad to heard that your issue seems solved with 15.1 :-D
but it will stay mysterious. :scratch
Indeed, there are very few changes with the DDNS feature in 15.1 : only add a warning when the credential doesn't allow to connect to the provider. so maybe some files were corrupted or didn't have the right permissions...