Dyndns client on Jolla
Are there any dyndns clients for Jolla?
Alternatively, are there any mechanisms in the networking stack (connman etc) to trigger a program whenever a network interface becomes active. Ala /etc/network/if-up.d on Debian.
I know I could have a permanent daemon listening for dbus-events or whatever, but I'd prefer a more lightweight method.
Doesn't Jolla have crontab? Maybe add line there with something to poke the DynDNS-services update url, like wget or curl?
avhakola ( 2015-01-22 13:04:45 +0200 )editJolla touches blank websites to confirm that it is online, you can probably add your update url there. And I'd be more interested in free services like
chemist ( 2015-01-22 13:35:25 +0200 )editafraid.org
Using cron for this may be possible, but rather clumsy. I prefer to have my phone be in "deep sleep" as much as possible, instead of having to wake up every N minutes to check if network interface status has changed.
Vegard Vesterheim ( 2015-01-22 15:48:30 +0200 )editMaybe udev rules are the solution for you then. I am not familiar with writing udev rules, but worth to take a look IMHO.
Edit: @chemist: DO you mean this parameter (Ipv4StatusUrl) in the /etc/connman/main.conf? Did not figured out if it is possible to add more than one url.
xllndr ( 2015-01-22 16:21:10 +0200 )editChanging Ipv[46]StatusURL in /etc/connman/main.conf to a URL that I control myself is a workable solution. I already have my own mechanism for doing the actual DNS update, via a small CGI script. I have adapted this script to also handle this case.
This is not an ideal solution though. I observe that my Jolla is revisiting this URL regularly, which triggers DNS updates unnecessarily. It also seems that supplying a username/password in the URL is not working, so instead of supplying the hostname directly into the CGI script, I instead supply a 'random' key. In my CGI script I have a static mapping from this key to hostnames. I haven't tested whether connman supports visiting https, and if so, how it handles SSL certificates.
Additionally, when using a "normal" dyndns client, the DNS entries can normally be deleted when the interface goes down. This will not work with this approach.
So, a good answer to my original question is still wanted.
Vegard Vesterheim ( 2015-01-23 12:37:36 +0200 )edit