Alt-F 1.0 ddns - what is wrong?

[Zoltan Kovacs]

Hi There!

Last week I changed my NAS' original firmware to Alt-f 1.0
Originally I looked for a solution for the samba v1 problem of DNS-320 and I found a fantastic firmware. :-)
It Is smarter than the original and the GUI is more comfortable. Everything is good but dynamic dns.

I used same settings when I used the original firmware. But it doesn't work.
When I try to start ddns, the page is updated (disappear and appear) and I see ddns remained in stopped state.

My settings are:

provider: dyndns.org <-- dlinkddns.org suggested this setting
IP server: 204.13.248.118 (or dlinkddns.com)
hostname: somebody.dlinkddns.com
username: somebody
password:

I don't know what the problem is. Did I forget something?

[João Cardoso]

On Monday, 19 February 2018 17:29:12 UTC, Zoltan Kovacs wrote:

Hi There!

Last week I changed my NAS' original firmware to Alt-f 1.0
Originally I looked for a solution for the samba v1 problem of DNS-320 and I found a fantastic firmware. :-)
It Is smarter than the original and the GUI is more comfortable. Everything is good but dynamic dns.

I used same settings when I used the original firmware. But it doesn't work.
When I try to start ddns, the page is updated (disappear and appear) and I see ddns remained in stopped state.

My settings are:

provider: dyndns.org <-- dlinkddns.org suggested this setting
IP server: 204.13.248.118 (or dlinkddns.com)

Read the tooltip (keep the mouse quiet >3 seconds within) at the IP server entry.

Turn verbose log on and examine the System log.

That's the only help I can provide, there are too many DDNS providers and each one uses it's own method.

Alt-F uses inadyn-mt as the client, I believe they have its own forum or mailing list

[Zoltan Kovacs]

I've try the url with and without "/" at the end.
I've turned verbose log on and examined the System log. But there isn't any information in the system log. There isn't any new row. I tried it several times.

[João Cardoso]

On Tuesday, 20 February 2018 16:43:43 UTC, Zoltan Kovacs wrote:

I've try the url with and without "/" at the end.

Try using the default, an empty field. It will use 

checkip.dyndns.org /

Anyone should be OK. There are occasional missing replies.

I've turned verbose log on and examined the System log. But there isn't any information in the system log.

 

After Submitting, the System log, shows (after filtering with INA

Feb 20 19:05:56 DNS-325 user.warn INADYN[2471]: Tue Feb 20 19:05:56 2018: W:CACHE_LIST Address, alias pairs read from cache file (/var/cache/ddns/inadyn_ip.cache):

Feb 20 19:05:56 DNS-325 user.warn INADYN[2471]: Tue Feb 20 19:05:56 2018: W:CACHE_LIST 188.37.86.13 zonzo.strangled.net:auto freedns.afraid.org...

Feb 20 19:05:56 DNS-325 user.notice INADYN[2471]: Tue Feb 20 19:05:56 2018: N:INADYN: The request for IP server: GET / HTTP/1.0^M Host: checkip.dyndns.org^M User-Agent: inadyn-mt/02.28.10 bho...@wecs.com^M ^M

Feb 20 19:05:56 DNS-325 user.notice INADYN[2471]: Tue Feb 20 19:05:56 2018: N:DYNDNS: My IP address: 188.37.86.13

Feb 20 19:05:56 DNS-325 user.warn INADYN[2471]: Tue Feb 20 19:05:56 2018: W:INADYN: IP address for alias 'zonzo.strangled.net:auto' needs update to '188.37.86.13'...

Feb 20 19:05:57 DNS-325 user.notice INADYN[2471]: Tue Feb 20 19:05:57 2018: N:INADYN: expanding url in get_req_for_http_dns_server:  /dynamic/update.php?

Feb 20 19:05:58 DNS-325 user.notice INADYN[2471]: Tue Feb 20 19:05:58 2018: N:INADYN: DYNDNS my Request: GET /dynamic/update.php?cUwyTDhyTlVZeGZwV2dkVzhheno6MTcwMDk0MDA=&address=188.37.86.13 HTTP/1.0^M Host: freedns.afraid.org^M User-Agent: inadyn-mt/02.28.10 bhoover@wecs.

Feb 20 19:05:58 DNS-325 user.warn INADYN[2471]: Tue Feb 20 19:05:58 2018: W:INADYN: Alias 'zonzo.strangled.net' to IP '188.37.86.13' updated successfully.

Feb 20 19:05:58 DNS-325 user.warn INADYN[2471]: Tue Feb 20 19:05:58 2018: W:INADYN: DYNDNS Server response: HTTP/1.1 200 OK^M Server: nginx^M Date: Tue, 20 Feb 2018 19:05:58 GMT^M Content-Type: text/plain; charset=utf-8^M Connection: close^M Vary: Accept-Encoding^M Cache-Con

Feb 20 19:10:10 DNS-325 user.warn INADYN[3199]: Tue Feb 20 19:10:10 2018: W:CACHE_LIST Address, alias pairs read from cache file (/var/cache/ddns/inadyn_ip.cache):

Feb 20 19:10:10 DNS-325 user.warn INADYN[3199]: Tue Feb 20 19:10:10 2018: W:CACHE_LIST 188.37.86.13 zonzo.strangled.net:auto freedns.afraid.org...

Feb 20 19:10:10 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:10:10 2018: N:INADYN: The request for IP server: GET / HTTP/1.0^M Host: checkip.dyndns.org^M User-Agent: inadyn-mt/02.28.10 bho...@wecs.com^M ^M

Feb 20 19:10:10 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:10:10 2018: N:DYNDNS: My IP address: 188.37.86.13

Feb 20 19:20:10 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:20:10 2018: N:INADYN: The request for IP server: GET / HTTP/1.0^M Host: checkip.dyndns.org^M User-Agent: inadyn-mt/02.28.10 bho...@wecs.com^M ^M

Feb 20 19:20:11 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:20:11 2018: N:DYNDNS: My IP address: 188.37.86.13

Feb 20 19:30:11 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:30:11 2018: N:INADYN: The request for IP server: GET / HTTP/1.0^M Host: checkip.dyndns.org^M User-Agent: inadyn-mt/02.28.10 bho...@wecs.com^M ^M

Feb 20 19:30:11 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:30:11 2018: N:DYNDNS: My IP address: 188.37.86.13

Feb 20 19:40:12 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:40:12 2018: N:INADYN: The request for IP server: GET / HTTP/1.0^M Host: checkip.dyndns.org^M User-Agent: inadyn-mt/02.28.10 bho...@wecs.com^M ^M

Feb 20 19:40:12 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:40:12 2018: N:DYNDNS: My IP address: 188.37.86.13

Feb 20 19:50:12 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:50:12 2018: N:INADYN: The request for IP server: GET / HTTP/1.0^M Host: checkip.dyndns.org^M User-Agent: inadyn-mt/02.28.10 bho...@wecs.com^M ^M

Feb 20 19:50:14 DNS-325 user.notice INADYN[3199]: Tue Feb 20 19:50:14 2018: N:DYNDNS: My IP address: 188.37.86.13 

[Zoltan Kovacs]

Dear João,

I've took another try. I started the ddns service but it stopped again.

I' checked the system log and I used the "INA" string for filter.

But there wasn't any info about ddns. I saw only a blank page.

After that I restarted the system. When the system restarted I found two rows in the system log about ddns:

Feb 21 18:09:20 DNS-320-FFE15A user.notice root: Starting inadyn-mt: OK.
Feb 21 18:09:24 DNS-320-FFE15A user.notice root: inadyn-mt stopped

So It started but didn't try to connect. Just stopped.

--
You received this message because you are subscribed to a topic in the Google Groups "Alt-F" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/alt-f/XFgZ7kuTAkg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to alt-f+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/alt-f.
For more options, visit https://groups.google.com/d/optout.

[João Cardoso]

On Wednesday, 21 February 2018 17:19:49 UTC, Zoltan Kovacs wrote:

Dear João,

I've took another try. I started the ddns service but it stopped again.

I' checked the system log and I used the "INA" string for filter.

But there wasn't any info about ddns. I saw only a blank page.

After that I restarted the system. When the system restarted I found two rows in the system log about ddns:

Feb 21 18:09:20 DNS-320-FFE15A user.notice root: Starting inadyn-mt: OK.
Feb 21 18:09:24 DNS-320-FFE15A user.notice root: inadyn-mt stopped

So It started but didn't try to connect. Just stopped.

Try diagnosing it at the command line:

inadyn-mt --verbose 5 --input_file /etc/inadyn.conf

The output might provide insights on what is wrong 

[Zoltan Kovacs]

Something wrong: 

Wed Feb 21 19:36:41 2018: W:MAIN: Main: Error 'RC_CMD_PARSER_INVALID_OPTION_ARGUMENT' (0x51).
[root@DNS-320-FFE15A]#

[João Cardoso]

On Wednesday, 21 February 2018 18:37:44 UTC, Zoltan Kovacs wrote:

Something wrong: 

Wed Feb 21 19:36:41 2018: W:MAIN: Main: Error 'RC_CMD_PARSER_INVALID_OPTION_ARGUMENT' (0x51).

This means that some option in the  /etc/inadyn.conf configuration file is wrong or isn't recognized.

The better is to start with a fresh one:

mv /etc/inadyn.conf /etc/inadyn.conf.old

Now use the webUI to create a new one, leaving the "IP server:" field empty by now. After Submiting, a fresh /etc/inadyn.conf will be generated. Now invoque the client from the command line and watch the output

inadyn-mt --verbose 5 --input_file /etc/inadyn.conf

[root@DNS-320-FFE15A]#

[Zoltan Kovacs]

Dear João,

Thank you!  It works well!

Everything works well.

Now I have a very smart NAS and no need to buy a new one for lot of money!

Thank you for this excellent firmware!