Securifi Community Forum
Securifi Products => Almond+ => Topic started by: akashk on July 14, 2014, 07:54:39 pm
-
Upon enabling the service and adding my details, the Last Update Status shows: Update Output: nohost.
I am using the free service from changeip. Any ideas?
-
I'd like some input as well. I've tried a couple of the different options listed as compatible with openwrt, but I always keep getting a 'badauth' response. I think it may be some difference in the configuration of 'luci-app-ddns' and 'luci-app-ddns-simple' [the latter of which is installed on the router].
-
I've informed the software team about this and it'll be investigated.
-
This issue has been verified and we're working on a fix for it.
-
Ok, Firmware R065 no longer uses luci-app-ddns-simple and is back to using luci-app-ddns (yay!)
Though I can't seem to get it to work with "-- custom --"
I'm using DNS-O-Matic (http://dnsomatic.com) (from the OpenDNS folks)
From what I gathered based on this post on the OpenWRT forums (https://forum.openwrt.org/viewtopic.php?pid=141166#p141166), I have the following set:
Enable: Checked
Service: -- custom --
Custom update-URL: https://[USERNAME]:[PASSWORD]@updates.dnsomatic.com/nic/update?hostname=[DOMAIN]&myip=[IP]&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG
Hostname: all.dnsomatic.com // (…to update all my linked domains)
Username: (dnsomatic username)
Password: (dnsomatic password)
Source of IP address: network
Network: wan
Check: 10 min
Force: 72 hours
But I can't get it to work… Anyone else have any luck with the custom setting?
I also tried it with another free service, DNSDynamic (http://www.dnsdynamic.org) using the settings from their API page (https://www.dnsdynamic.org/api.php) and had no luck either.
A reply to that OpenWRT topic above also suggested to uncheck "Use DNS servers advertised by peer" setting under WAN > Advanced, but toggling that didn't seem to have any effect.
-
I'm having the same issue here and have tried all of the same things. I'm using dyndns.org and tried the dyndns.org option from the dropdown but that didn't work. I have a pro account so I don't know if that affects anything.
Also it would be nice if there was a force update button or at least a way for it to login and check to see if your credentials are good. I know mine are, but it's not updating.
-
In regards to using dnsdynamic, there appears to be an issue with wget. I'm getting the following:
root@AlmondPlus-CLC:/usr/lib/ddns# ./dynamic_dns_updater.sh myddns
update_url=http://[USERNAME]:[PASSWORD]@www.dnsdynamic.org/api/?hostname=[DOMAIN]&myip=[IP]
force seconds = 86400
check seconds = 3600
old process id (if it exists) = "15629 root 1436 S /bin/sh /usr/lib/ddns/dynamic_dns_updater.sh mydd
ns 0"
time_since_update = 0 hours
Running IP check...
current system ip = REAL_IP
registered domain ip = 222.222.222.222
update necessary, performing update ...
updating with url="http://MYREALUSENAME:MYREALPASSWORD@www.dnsdynamic.org/api/?hostname=MYREALHOSTNAME&myip=MYREALIPADDRESS"
Connecting to www.dnsdynamic.org (84.45.76.100:80)
wget: server returned error: HTTP/1.0 401 Authorization Required
Update Output:
update complete, time is: Sun Aug 17 22:22:49 EDT 2014
I'm trying out some alternate methods, but no luck as of yet.
-
We're working on fixing the DDNS stuff, we're aware that there are some issues and it will hopefully be addressed in the next firmware release.
-
OK. I'm completely baffled as to why this is working the way it is:
I have the following script,
#!/bin/sh
WANIF="eth0"
MYHOST="MYHOSTNAME"
USERNAME="MYUSERNAME"
PASSWORD="MYPASSWORD"
MYIP=`ifconfig ${WANIF} |grep -o -E 'inet addr:([0-9.]+)' |grep -o -E '([0-9.]+)'`
URL="http://${USERNAME}:${PASSWORD}@www.dnsdynamic.org/api/?hostname=${MYHOST}&myip=${MYIP}"
/usr/bin/wget -O - --no-check-certificate "$URL"
And this actually works to update DDNS from the router (I just ran the script directly and set it up to run on a cron).
Considering this works, I thought I could just modify the wget params in the dynamic_dns_updater.sh script to match the ones in this script and that should fix the issue.... nope. Still getting the 401 auth issue.
At least this workaround will "solve" my ddns issue for now.
-
Ok, figured out the problem that's causing the auth issue. The dns updater is escaping out symbols in the username provided from the ddns config file, thus wget is returning an auth failure (specifically for me this is the '@' sign since my email is my username).
Within the /usr/lib/ddns directory is a file called url_escape.sed. I removed the line from this file containing the @ to %40 escape and now ddns updates successfully.
-
Not trying to hijack the thread, but I am unable to use DUCKDNS.org's custom url either.
-
It appears to be an issue with how @ are being handled and we're working on a fix.
-
Not trying to hijack the thread, but I am unable to use DUCKDNS.org's custom url either.
I was able to get DuckDNS working, but it took some extra steps beyond just filling out the fields as a custom service. This was my first time using SSH and VI, so I was kinda all over the place, but I think the key steps were the following:
- Editing /usr/lib/ddns/services to include DuckDNS (see the instructions at http://wiki.openwrt.org/doc/howto/ddns.client (http://wiki.openwrt.org/doc/howto/ddns.client))
- Editing /etc/config/ddns to include the service_name option as specified in the DuckDNS entries
I have an extremely limited understanding of OpenWRT, but looking back now I think if you do the first step then DuckDNS shows up as an option in the GUI and you may not need to do the second step. From there I just filled in the fields as specified in the DuckDNS instructions.
-
I was able to get DuckDNS working, but it took some extra steps beyond just filling out the fields as a custom service. This was my first time using SSH and VI, so I was kinda all over the place, but I think the key steps were the following:
- Editing /usr/lib/ddns/services to include DuckDNS (see the instructions at http://wiki.openwrt.org/doc/howto/ddns.client (http://wiki.openwrt.org/doc/howto/ddns.client))
- Editing /etc/config/ddns to include the service_name option as specified in the DuckDNS entries
IT WORKED
Yeah I didn't do step 2 and just configed it through open wrt.
Thanks so much.
-
Within the /usr/lib/ddns directory is a file called url_escape.sed. I removed the line from this file containing the @ to %40 escape and now ddns updates successfully.
I removed this entry based on your experience and now DNSDynamic entries are updating using the "--custom--" service.
Considering how many services use email (with the @ symbol) as the username, I wonder why it's escaped by default.
While I'd like to update the /etc/config/ddns file to include new server entries, I'm afraid (ok, lazy) of having to re-edit it when new A+ firmware gets released.
-
Ok, so I caved and modified the /usr/lib/ddns/services file to include DNSDynamic - very easy!
I just added the following line to the end of the file:
"DNSDynamic" "http://[USERNAME]:[PASSWORD]@www.dnsdynamic.org/api/?hostname=[DOMAIN]&myip=[IP]"
Updating the address has been working flawlessly after getting rid of the @ entry in the /usr/lib/ddns/url_escape.sed file.
I'm still having difficulty getting DNS-O-Matic to work. Looking around other forums, it's possible that the OpenWRT script checking to see if the IP address has changed is checking "all.dnsomatic.com" which will not necessarily report the correct address, unneccessarity triggering an update process.
-
I was able to get DNS-o-Matic to work, and it was pretty self explanatory. Using their API page, I just added the following line to /usr/lib/ddns/services
"DNS-O-Matic" "http://[USERNAME]:[PASSWORD]@updates.dnsomatic.com/nic/update?myip=[IP]&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG"
The problem I had was that I inadvertently deleted the closing quotation mark from the entry above it, which caused issues.
Another issue not related to A+ is now Hurricane Electric's IPv4 endpoint updater doesn't seem to be working, either using DNS-o-Matic nor directly using their own update URL:
"Tunnelbroker" "http://[USERNAME]:[PASSWORD]@ipv4.tunnelbroker.net/nic/update?hostname=[DOMAIN]&myip=[IP]"
It just returns good 127.0.0.1.
-
Ok, after a few days of leaving it alone to see if it would update, it looks like I got HE/Tunnelbroker's DynDNS to work:
Used the "custom" Dynamic DNS choice and the custom update URL is
http://[USERNAME]:[PASSWORD]@ipv4.tunnelbroker.net/nic/update?hostname=[DOMAIN]&myip=[IP]"
Hostname=Tunnel ID number (get this by logging into tunnelbroker.net, then click the tunnel, Look on the IPv6 Tunnel tab, near the top)
Username = tunnelbroker.net username
Password=the update password listed in the tunnel's Advanced tab on tunnelbroker.net or if none is listed, your tunnelbroker.net password (less secure).
...The rest I left with the defaults.
To verify that it worked, you can use the following command after ssh'ing into the A+:
sh /usr/lib/ddns/dynamic_dns_updater.sh Tunnelbroker
(I named mine "Tunnelbroker" but you would type whatever you named the service when you clicked Add)
It should report Update Status with "good" and your current IP.