Marcs Updater
There have been some reports about issues with the Updater not updating anymore. Please try the latest beta version and switch to another IP Check provider instead of the previous default dnsomatic.com. For some reason they are rate-limiting the number of requests to their service. The new IP Check provider selection allows you to choose another provider in such cases. You can test the functionality with the new "Test" panel.
If you want to add a custom provider to the unstable testing version, store a JSON file like the following under %PROGRAMDATA%\Marcs Updater\ServiceProviders\dyndns.json:
{
"name": "DynDNS.org (Test)",
"endpoint": "https://members.dyndns.org/nic/update",
"method": "GET",
"queryString": "hostname={HOSTNAME}&myip={MYIP}",
"dataPayload": "",
"defaults": {
"username": "test",
"password": "test",
"hostname": "test1.customtest.dyndns.org"
}
}Supported query and payload tags are {USERNAME}, {PASSWORD}, {HOSTNAME} and {MYIP}. Restart the background service and foreground application to apply any changes.
Issue created on
Posted on
Guest wrote:
Do the local network or wireless filtering options do anything? I assumed that they were to restrict updates to when connected to those networks or only when using that DHCP server? I can't find any documentation on this.
However, as far as I can tell, the updater ignores these settings?
Bug, feature, misunderstanding?
Posted on
Marc wrote:
Yes, they do something. The wireless filter is active for wireless networks and the network filter for all others. The first one compares the SSID of the networks, the last one either the gateway's IP or the DHCP domain.
You can check the current value by opening the settings window and going to one of the tabs. The input field will default to the current value.
Posted on
Guest wrote:
Yes, I've done that and they show the current values. HOWEVER, and it's a big however, when I add the current values to the list, enable the function, then connect to a DIFFERENT network, the updater still fires.
To put it another way. Those filters do not work, at all, ever.
Posted on
Marc wrote:
Sorry, I can't find the issue in the code. Could you please enable logging by setting the system wide environment variable LOGLEVEL to 7 and then look for logfiles inside %ALLUSERSPROFILE% ?