I am attempting to use DDNS and not having any success for any provider. I am using a Trendnet router TEW-812DRUv2 and am on r52242 mini. No one else is reporting this type of issue, so it must be problem with my equipment/configuration, but don't know how to resolve.
The problem seems to have occurred after inadyn was refreshed to v2.10 and I have tried several releases in between. What happens is that no log output is generated at all after the configuration for any provider is saved. Initially I was using dnsomatic with the custom provider, but changed it to the dnsomatic provider that became available with the new release. After experimenting, this seems to happen with all providers so I do not believe it is a problem with the inadyn.conf file. I can see that ddns.log gets created in /tmp/ddns, but it is zero bytes. Stopping the service and running the command manually produces the same results. No other files are created.
Below is the contents of my inadyn.conf file, but I do not believe this is the source of the problem as stated above.
DDNS is broken in my configuration and I am thinking that perhaps this is a problem for the "mini" builds. I haven't seen anyone else mention that DDNS is working properly with a mini build since the new version of inadyn.
I have tried other providers and the same behavior occurs. What is strange is that no log messages are generated under any circumstance (zero-byte ddns.log file). When running the inadyn command manually, the only output I can get is with the -v or -h options.
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Fri Apr 14, 2023 17:44 Post subject:
klinebau wrote:
I have tried other providers and the same behavior occurs. What is strange is that no log messages are generated under any circumstance (zero-byte ddns.log file). When running the inadyn command manually, the only output I can get is with the -v or -h options.
Joined: 08 May 2018 Posts: 14244 Location: Texas, USA
Posted: Fri Apr 14, 2023 18:00 Post subject:
mwchang wrote:
Not sure whether Setup->DDNS (Inadyn) is using verbose logging to system log...
egc wrote:
Unfortunately you cannot set more verbose logging the very simple patch to add this was not accepted
The question in my mind remains, what are the configuration details in the webUI and how do they compare to what the DDNS provider require? Something seems missing from this tall tale. Also, to note, ~1-1.5MB of firmware image size decrease over time, and no idea why the firmware image is considered "mini" vs. "std" or "mega"... _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Attached is the UI that corresponds to the inadyn.conf file listed above. Note that the service status field is empty-- I should be getting some message even if the there is a problem with the provider configuration. That said, I know that these settings work with dnsomatic because I am running inadyn on my pi as a workaround. The only difference is that I am using the external ip check for that configuration.
_________________ "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
It is easy to get more logging first kill the process e.g:
killall inadyn
Then start it again with:
inadyn --cache-dir=/tmp/ddns -e ddns_success --exec-mode=compat -f /tmp/ddns/inadyn.conf -P /var/run/inadyn.pid -l debug -C
I think I mentioned in first post that I have tried executing the command manually (after killing or stopping service). I can set the log level (-l flag) to any value such as info, notice or debug. The process simply will not write any log messages to the ddns.log file.
Could it be that overriding the plugin defaults is causing your problems?
None of these values have been overriden:
.name - not entered from GUI (value in ddns.conf file is using this default)_
.request - not referenced in GUI or ddns.conf file
.response - not referenced in GUI or ddns.conf file
.checkip_name - only used for external IP check (currently set to no in GUI)
.checkip_url - only used for external IP check (currently set to no in GUI)
.server_name - not referenced from GUI (used by inadyn to update dnsomatic provider)
.server_url - not referenced from GUI (used by inadyn to update dnsomatic provider)
https://wiki.dd-wrt.com/wiki/index.php/OpenDNS _________________ "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
The documentation for dnsomatic is out of date and the custom provider is no longer used. DNS-O-MATIC now has its own drop-down entry. This changed with the inclusion of inadyn 2.10 into dd-wrt.
None of the providers are working in my build and none produce any log message at all. I believe the problem to be with the inadyn binary file or with one of its dependencies.
The documentation for dnsomatic is out of date and the custom provider is no longer used. DNS-O-MATIC now has its own drop-down entry. This changed with the inclusion of inadyn 2.10 into dd-wrt.
Thanks for the highly unnecessary history lesson <lol> But, in the past, using port 443 (SSL) was / wasn't required for authentication, which is quite possibly still valid (or not) as per my previous comment. <eyeroll>
klinebau wrote:
None of the providers are working in my build and none produce any log message at all. I believe the problem to be with the inadyn binary file or with one of its dependencies.
Quite possible. Don't know if the firmware image size decrease is due to development changes to reduce code size or a bad build.
kernel-panic69 wrote:
Also, to note, ~1-1.5MB of firmware image size decrease over time, and no idea why the firmware image is considered "mini" vs. "std" or "mega"...
I would suggest upgrading to current release, simply based on firmware image size differences and the possibility that the problem is already resolved:
_________________ "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
The documentation for dnsomatic is out of date and the custom provider is no longer used. DNS-O-MATIC now has its own drop-down entry. This changed with the inclusion of inadyn 2.10 into dd-wrt.
Thanks for the highly unnecessary history lesson <lol> But, in the past, using port 443 (SSL) was / wasn't required for authentication, which is quite possibly still valid (or not) as per my previous comment. <eyeroll>
Not unnecessary because using the custom provider for dnsomatic in the old configuration allowed you to configure using SSL or unencrypted and I agree that it was important to use the correct port. However, with dnsomatic built into the new version, inadyn handles it natively.
