bignerd95/asusddns

Asus ddns update and registration script for DD-WRT and others platforms.

asusddns's Issues

Unknown result code. (000)

Hellow. This script worked fine until yesterday 2017-04-17. However today (2017-04-18) I could not connect on my dynamic name, in the logs this error:
ASUSddns: Unknown result code. (000)

I tried to run from the console:
~/ASUSddns.sh MAC SCODE NAME register console
And again I received:
ASUSddns: Unknown result code. (000)

Couldn't resolve host 'ASUSddns.sh

Couldn't resolve host 'ASUSddns.sh ？？？

Deregister DDNS

Hi,

There's a new deregister button in the recent firmware. Anyone knows the URL for this? Blindly trying '/ddns/deregister.jsp' seems to return 404.

-ash: nvram: not found

root@OpenWrt:~# nvram get et0macaddr
-ash: nvram: not found
root@OpenWrt:~# opkg install nvram
Unknown package 'nvram'.

ASUS RT-AC58U

Deregister as an option

It seems that the script only supports register and update.

There is also a button called Deregister:

That could be handy if it supports that too, so you could deregister the DDNS with this script.

I did found the issue #5, but that was closed and nothing was added to this script.

CN version of asus ddns?

There is the CN version of ASUS DDNS. Would you like to make the CN version of the ASUSddns script and ASUSddns_slim script?

local: ns1.asuscomm.com: bad variable name

Hi there,
I had the following error:
./ASUSddns.sh: 28: local: ns1.asuscomm.com: bad variable name

after googling a bit I found this:
"local" is a bash-specific feature which is not defined in the POSIX standard for sh (the POSIX shell).

after changing the top of the script to #!/bin/bash everything works fine.
I am running Ubuntu 19.10 and just wanted to give this as a feedback if someone else has the same error.

Thanks for the great script!

P.S.: My Mac address was stored in "et2macaddr" and not "et0macaddr" as mentioned in the docu.

Slim request should use HTTP 1.0

Hi,

As stated in the subject, the two requests made for api.ipify.org and ns1.asuscomm.com should use HTTP 1.0 or add a header "Connection: close\r\n" for its HTTP 1.1 else the request will stall longer than required due to persistent keep alive connection.