Joined: 18 Mar 2014 Posts: 12837 Location: Netherlands
Posted: Sat Nov 05, 2022 13:32 Post subject:
the-joker wrote:
nyddwrtuser330 wrote:
Added the after, screenshot above.
It MAY be working correctly, but in previous it woul actually say "IP updated Succcessfully" or IP update failed" or something to the effect of No change, IP not updated.
Seems like its either hanging or not looging results
If you're talking about the old inadyn forget it, the new one is nothing like the old.
For the new inadynv2 DDWRT has set the standard logging at "notice" that means no logging of the 10/15 minute update only of the forced update.
As I also was curious if it worked I had set the logging at "info" and then you will see much more:
Code:
Thu Jan 1 01:00:21 1970 In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Thu Jan 1 01:00:21 1970 Startup delay: 90 sec ...
Sat Nov 5 13:54:28 2022 Cached IP# xx.xx.xxx.xxx for egcpn.hopto.org from previous invocation.
Sat Nov 5 13:54:28 2022 Last update of egcxxx.xxx.xxx on Sat Nov 5 13:54:28 2022
Sat Nov 5 13:54:29 2022 Checking for IP# change, connecting to ip1.dynupdate.no-ip.com([xx.xx.xxxx.xx]:80)
Sat Nov 5 13:54:29 2022 No IP# change detected for default@no-ip.com, still at xxx.xxx.xxx.xxx
Sat Nov 5 13:54:29 2022 Update forced for alias egcxxx.xxx.xxx, new IP# xxx.xxx.xxx.xxx
Sat Nov 5 13:54:29 2022 Sending IP# update to DDNS server, connecting to dynupdate.no-ip.com([xx.x.x.x]:80)
Sat Nov 5 13:54:29 2022 Successful alias table update for egcpn.hopto.org => new IP# xxx.xxx.xxx.xxx
Sat Nov 5 13:54:29 2022 Updating cache for egcxxx.xxx.xxx
Sat Nov 5 14:04:35 2022 Checking for IP# change, connecting to ip1.dynupdate.no-ip.com([xx.xx.xx.xx]:80)
Sat Nov 5 14:04:35 2022 No IP# change detected for default@no-ip.com, still at xx.xx.xx.xx
Sat Nov 5 14:14:41 2022 Checking for IP# change, connecting to ip1.dynupdate.no-ip.com([xx.xx.xx.xx]:80)
Sat Nov 5 14:14:41 2022 No IP# change detected for default@no-ip.com, still at xx.xx.xx.xx
That patch needs reviewing properly by someone that understands radvd, it is also likely that such patch if not handled properly will not be backwards compatible, so existing setups will suffer.
OK, that fixes the web UI being unwilling to save user-entered Hostname info.
The problem that remains: if I have the hostname field populated with more than one hostname (using the '-a' parameter), I receive the "400 Bad Request" response from (I assume) DynDNS.
I have confirmed that /tmp/ddns/inadyn.conf contains inadyn 2.9.1 compliant format/info. For testing, I have simplified to update only two of my five sites, "site1" and "site2":
If I remove the trailing "-a site2.dyndns.org", a successful update is (kind of) reported.
If I again add site2, "400 Bad Request".
With multiple sites configured in hostname:
50595 = works (1.96-ADV), and has very good user feedback on Status screen; the 2.9.1 version is much less clear about what it's reporting.
50671 = does not work (stalls at "Connecting to server") (2.9.1)
50755, 50786, 50814 = does not work ("400 Bad Request" from server)
It appears that either the multiple DDNS hostname functionality is broken, or the syntax to use it ('-a') it has changed, with the wiki being out of date. Should I open a ticket for this?
Meanwhile, I'm staying with 50595, which continues to update all five of my sites.
---
Also, the UI hostname field's 99-char limit I ran into two years ago is still extant. While I can use alternate means to be able to populate hostname with more than 99 char, I think it would be a better user experience if that limitation was raised to a higher value. For my use case, I'm about 15 chars too many to be able to use the UI to update any of my sites. _________________ Regards,
Al Savage
----------------
R7800 x2
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon Nov 07, 2022 10:10 Post subject:
asavage wrote:
50595 = works (1.96-ADV), and has very good user feedback on Status screen; the 2.9.1 version is much less clear about what it's reporting.
It's clear enough on the updates logging, its not as verbose but its clear when updates succeed or fail. If you're not happy about it keep reading.
asavage wrote:
It appears that either the multiple DDNS hostname functionality is broken, or the syntax to use it ('-a') it has changed, with the wiki being out of date. Should I open a ticket for this?
No tickets here please. Like blkt pointed above, you need to read the configuration details on the inadyn project upstream, the configuration from 1.96ADV from 2005 is incompatible with new inadyn 2.9.1 from 2022, you need to read the new supported configuration methods on their documentation, if anything is unclear on their documentation, you ask upstream how to do this. seems answer is hostname = ( fo.o, foob.ar, foo.bar }
DD-WRT is not responsible for inadyn development bug fixing or adding features, for such you need to make any requests or bug reports upstream at https://github.com/troglobit/inadyn/issues/new taking care to search if a current similar report exists. Generally speaking no one likes duplicate reports.
DD-WRT's responsibility is only to ensure the implementation in DD-WRT works as per what they (inadyn) support currently, which is a priority to our lead developer.
asavage wrote:
Also, the UI hostname field's 99-char limit I ran into two years ago is still extant. While I can use alternate means to be able to populate hostname with more than 99 char, I think it would be a better user experience if that limitation was raised to a higher value. For my use case, I'm about 15 chars too many to be able to use the UI to update any of my sites.
Joined: 06 Jun 2020 Posts: 22 Location: Oak Harbor, Washington, USA
Posted: Mon Nov 07, 2022 17:35 Post subject:
Thanks for that. Increasing that input field to 255 should cover the majority of use cases. In my case, I need about 104 chars.
I'm unfamiliar with the review/merge process here; can you expand on "was not merged"? It was only committed 3 hours ago; are commits accepted/rejected that fast? _________________ Regards,
Al Savage
----------------
R7800 x2
Last edited by asavage on Mon Nov 07, 2022 18:03; edited 1 time in total
Joined: 06 Jun 2020 Posts: 22 Location: Oak Harbor, Washington, USA
Posted: Mon Nov 07, 2022 18:01 Post subject:
Thanks, both of you, that was very helpful.
Using the info at those links, the DDNS wiki provides outdated info that applies to the previous version of inadyn; the '-a' parameter is no longer needed.
Adding the braces and insulating spaces "{ " and " }" (either by editing /tmp/ddns/inadyn.conf directly, or by using the UI's input field) yields this:
and the corresponding output when inadyn processes it remains "400 Bad Request" (see screenshot below).
I was thinking that possibly inadyn won't parse the quotes, so I next tried removing them. When I remove the quotes, the next boot they're back, so I'm not editing correctly. This is the process I've used:
Code:
stopservice inadyn
vi /tmp/ddns/inadyn.conf
reboot
I see that default inadyn is expecting /usr/etc/inadyn.conf but dd-wrt locates it /tmp/ddns/inadyn.conf .
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon Nov 07, 2022 18:49 Post subject:
asavage wrote:
I'm unfamiliar with the review/merge process here; can you expand on "was not merged"? It was only committed 3 hours ago; are commits accepted/rejected that fast?
I made a pull request including the maxlength="255" however The head developer elected to ignore the change without any reason given.
As for config for multiple serer I have mentioned it with PR that inadyn supports multiple hostname entries, so its unclear why the merge was refused or if dd-wrt supports that scenario as of yet.
It's possible that it is how the DD-WRT implementation parses the multiple servers to the config file, not anything to do with inadyn, and not necessarily a character length problem. The DDNS provider is expecting one thing, which is not being correctly parsed and provided from DD-WRT, or is being entered incorrectly by the user. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio