Last I looked, it appeared that most of the scripts in the dnsapi directory were created for very specific platforms. I believe your dns_asus.sh script would fit in nicely with the existing collection... That's if it you're open to it.I don't know if it'd be suitable to be added to the dnsapi repo as it uses some asus only features, the nvram secret_code and hardware MAC address, and it also forces a ddns update for the asuscomm address.
I like the mount bind approach. I'll see if I can give it a try. The only issue is that I don't see any DDNS or LE entries in the System Log, so I do know whether the Asus UI is even executing them.The easiest way to find the arguments would be to just mount over the acme script and log them, something like
printf '%s\n' '#!/bin/sh' 'logger -t acme "$*"' '/tmp/acme_copy.sh "[email protected]"' > /tmp/acme_log.sh cp /usr/sbin/acme.sh /tmp/acme_copy.sh chmod +x /tmp/acme_copy.sh /tmp/acme_log.sh mount -o bind '/tmp/acme_log.sh' '/usr/sbin/acme.sh'
I see. I hadn't considered your implementation timeline vs Asus' implementation. Makes sense.As for not using the built in acme.sh, I had been using it since before it was added to asuswrt. Plus it's easier to work with a version I have complete control over.
I really appreciate your comments and guidance.