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
Released version 1.5.0.247
- Replaced registry based logging with the Windows Event Log.
- Added local network filtering based upon gateway IP or DHCP domain.
- Added /autostart, /userstart and /nostart switch to program.
- Added /autostart, /nostart, /nostartmenu and /nocontrolpanel switch to installer.
- By default the installer launches the program if autostart is enabled.
- Testing fix for application updater crashes.
- OpenDNS update frequency lowered to at least every 2.5 + rand(0.5) hours.
Posted on
Thank you very much for changing the logging to the Event Log. Beautiful! :-)
Posted on
Thanks Marc from me too! The update was completely smooth (no problem whatsoever) and I can see the events being created in the Event Viewer (i.e. Source: Marcs Updater, Event ID: 100).
Posted on
Nice to hear that. EventIDs: 100 = Success, 101 = Warning (next update is postponed), 102 = Error (next update is disabled until settings are changed).
Posted on
Marc, would you be so kind and briefly explain what's the purpose of Local Network filtering option (who should use it and who not). You see, in my case I have a 3G USB modem that uses some Vodafone Mobile Connect software and some (let's say "virtual" :D) LAN connection (acting as a gateway?) to connect to my ISP mobile Internet.
In Marcs Updater's "Local Network" section there is the right IP address detected as a gateway (assigned by DHCP. Should I use this option or in my case it doesn't matter?
For you to better understand the situation I am also adding links to three screenshots (images are hosted on imgur.com); the first one is a screenshot of LAN Status - Support tab: http://i.imgur.com/7BwyH.png, the second one is a screenshot of Network Connections (with mouse pointer over this LAN connection that's used by USB modem): http://i.imgur.com/rJvxx.png, and the third one is a screenshot of "Local Network" section in Marcs Updater: http://i.imgur.com/Dx6jp.png
Thanks for any reply, Tadej from Slovenia
1
Posted on
It does basically allow you to restrict updates to a certain LAN. Just like the wireless filtering allows you to restrict updates to a certain WLAN. For example: You travel with your laptop and only want to send updates through certain LAN connections.
From my understanding you don't need the filtering, because you are using your own 3G connection anyway.