-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2016-12-04 a las 21:21 +0100, Carlos E. R. escribió:
Well, it is finally working. Cronjob setup and working. Every five minutes a cronjob interrogates the router, using a expect autogenerated script, issuing a command that prints the external IP and other things. The script extracts that IP, compares with the currently assigned IP, and if changed, updates the new IP to the dyndns service. If there was a change it sends an external email to me so that I know how things are going.
Thanks everybody :-))
Well, it failed when I was away, I lost connectivity to it from remote. Fortunately, it told me that with an email, and the email headers contained the IP address and I could connect up again and investigate. It turned out that name resolution of "router" failed, because dnsmasq was configured to look also at the bind server on my desktop machine... which was switched off (and on during testing). Time out and failure solving local names, but not remote names (or postfix did not give up on timeout that easily). Very curious. Problem repaired. Phew! Redundancy is a good thing... - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhLQDIACgkQja8UbcUWM1yxzAD+LKljyaUhLVMk7cIQiamrJXhf SJde0CSFZ2lAA51YeywA/jPXCfn3AlUGfL6gko26ZC186RF1/2fzaIWja/xaTw7k =YKpS -----END PGP SIGNATURE-----