I'm getting the same thing.
Is the logic for this right?
#ifdef RTCONFIG_IPV6
if (nvram_get_int("ddns_ipv6_update")
&& ipv6_enabled() && (_get_ipv6_addr(wan_ifname, ip6_addr, sizeof(ip6_addr)) != 0))
{
logmessage("ddns", "%s has not yet obtained an WAN IPv6...
Either should work, but as I mentioned interface-name will also resolve the IPv6 address.
Dnsmasq is what provides the client's DNS responses, so it seems to me like the appropriate place to set the configuration. Just personal preference really.
I believe he means accessing it locally, but using the ddns hostname. It should be possible by adding a dnsmasq.conf.add line to point it to the routers LAN address instead of resolving to the WAN address.
I think using the interface-name option should let it work for both IPv4 and IPv6, but 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.
The easiest way to find the arguments would be to just mount over the acme script and...
Actually, after looking through the code you might want to use --reloadcmd instead. It can be used with either --install-cert or --issue and runs after success, while --renew-hook can only be used with --issue and only runs on renewal (so not the first certificate request).
If you've already set your router to use a custom certificate, you don't need to set any nvram values. There's also some variables set by acme which can make it a bit easier.
#!/bin/sh
# Preset variables
# CERT_PATH
# CA_CERT_PATH
# CERT_FULLCHAIN_PATH
# CERT_KEY_PATH
# Le_Domain
# Check the...
ncurses is included in asuswrt, but many of the utilities which usually come with it are not. While it's possible to install it from entware, it's probably best to make something like your command prompt as fail-safe as possible (best not to even add it to your profile.add until you've tested...
It might be helpful to include this in the upgrade notes section of the first post.
- NOTE: Some users upgrading might have to go through some
database maintenance on first boot, which means the
router might be slower or have a non-responsive webui
for a while...
Seems like a problem with your entware installation. Usually there'd be an entry in /jffs/scripts/post-mount which would call /opt/etc/init.d/rc.unslung start "$0" when the drive is mounted, and that'd load all the enabled /opt/etc/init.d/S## scripts.
Entware puts itself first on the PATH list in /opt/etc/profile, which is included from /etc/profile ([ -f /opt/etc/profile ] && . /opt/etc/profile). I suspect there's a problem with Turgut's installation.