26 Apr
2024
26 Apr
'24
11:45 a.m.
I would second Rob’s suggestion - by far the best option - you receive the routes the
moment anything changes rather than having to download them manually or on a cron script.
Chris - G1FEF
—
ARDC Administrator
Web: https://www.ardc.net
On 26 Apr 2024, at 08:58, Rob PE1CHL via 44net
<44net(a)mailman.ampr.org> wrote:
I would recommend that unless you have an environment that cannot support that, instead
of the encap file you use the RIP broadcasts with the program ampr-ripd. It keeps the
routing table uptodate without regular file downloads and it can write an encap.txt file
when you require that for some purpose (and which you can use as a backup when the RIP
broadcasts are down for some reason)
Rob
On 2024-04-26 00:32, Lee D Bengston via 44net wrote:
Hello,
If I use the line from the Wiki below in order to retrieve the file via API (and convert
it back to the text forma), I get a parsing error - presumably from jq. If I download
only the file taking jq out of the equation, it's not a json file, but rather, a HTML
file. I assume that's why there's a parsing error when jq reads it. Is the info
from the Wiki out of date?
Thanks,
Lee K5DAT
curl -s https://user:key@portal.ampr.org/api/v1/encap
<https://user:key@portal.ampr.org/api/v1/encap> | jq -r '.[] | "route
addprivate \(.network)/\(.maskLength) encap \(.gatewayIP)"'
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org