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.
Posted on
Hi Marc,
Just a question about the network and wireless tabs.
If I have a laptop at home, and I sometimes use it with NIC and sometimes with wifi, then I DO NOT tick those boxes? So if I go to friends house, it should also automatically filter any wifi or NIC connections I make there.
In other words, local networks and wireless should Only be ticked if you want filtering to work ONLY on Specific local and wifi networks, but if they aren't ticked they will filter ALL connected wifi and local networks that are connected?
Is this correct, or have I understood it backwards? :-p
Thank youÂ
Posted on
Hi Tia,
I think you misunderstood the functionality. You have to tick the box in each tab in order to enable the specific filtering. Once enabled, updates will only be send over the specified LANs or WiFis. This is also working completely separate, so while you are connected to a WiFi network, the LAN filtering is not used and also the other way around.
Best regards,
Marc