Sync monitor timer

[ghost]

No description provided.

[bennlich]

Woot!!! Awesome!

[bennlich]

This seems good to me. Have you tried creating a new exitnode with the script from this branch and tested to see if it worked?

I think it would be sufficient to test that your new script is getting called every two minutes like you expect.

P.s. One thing you could do to be a little fancy would be to curl the bash script from the monitor github repo instead of hardcoding it into this repo. E.g. https://raw.githubusercontent.com/sudomesh/monitor/master/post-routing-table.sh.

[ghost]

This seems good to me. Have you tried creating a new exitnode with the script from this branch and tested to see if it worked?

I think it would be sufficient to test that your new script is getting called every two minutes like you expect.

P.s. One thing you could do to be a little fancy would be to curl the bash script from the monitor github repo instead of hardcoding it into this repo. E.g. https://raw.githubusercontent.com/sudomesh/monitor/master/post-routing-table.sh.

This is the exact same script, timer, and service files on the HE exitnode, the only manual commands that needed to be run were:
systemctl enable exitnode-sync.timer and systemctl start exitnode-sync.timer which i dropped in the create_exitnode.sh script next to the start and enable babeld timer & service.

I would like to try this on a pre-production environment, but that would have to create an entire exitnode and also the monitor separately. The quick way to test this is add a test exitnode ip to exitnodeIPs.js on peoplesopen.net can i have access to that? also one of the HE routes is malformed and needs to be removed manually.

I would not rely on external services for the same reason that retrieve_ip might fail from certificate or resource availability problems.