Page 1 of 1
Feature and DynDNS BUG
Posted: Thu Oct 06, 2011 11:15 am
by nickba
Hello and thanks for this wonderful work.
I have a TL-WR1043ND and I am using the latest 1.4.2 firmware.
First I'd like to suggest a feature that is a manual entry in GUI for DSL modem access when in bridge. I know there is a automatic recognition of the modem IP address in bridge when the modem has a DHCP in bridge mode, but almost all modems I tested doens't have DHCP mode in bridge and I have to edit the /etc/ppp/ip-up.d/modemaccess.sh to make it work.
Now the bug: I was running the latest firmware fine for about 9 days when it stopped to update the DNS with DynDNS. Even forcing the update using GUI, it wouldn't update. After a router reboot, it updated it.
This was happening on the 1.3.16 too.(this was the previous firmware before I installed the 1.4.2).
Again, thanks for your great work!
Re: Feature and DynDNS BUG
Posted: Wed Oct 19, 2011 1:15 am
by nickba
Bump
Re: Feature and DynDNS BUG
Posted: Wed Nov 23, 2011 11:03 pm
by nickba
Hi again,
Just to report that the problem with updating with DynDNS still happening in 1.5.0 the same way it was happening on previous versions on the TL-WR1043ND.
After about 9 or 10 days the router stops updating throught DynDNS and even the Force Updade option does not work. The only solution is a reboot. After a reboot, it works updating throught DynDNS for about 9 days again and stops.
Maybe my configuration helps:
I am using the router with a ADSL modem in bridge mode and I configured the modemaccess.sh to enable the access to the modem configuration page.
Keep the great work!!!
Re: Feature and DynDNS BUG
Posted: Mon Dec 05, 2011 2:17 pm
by Eric
Can you please try either 1.4.4 or 1.5.1? I've added some new fixes for dynamic dns that should fix this problem.
Re: Feature and DynDNS BUG
Posted: Tue Dec 06, 2011 2:47 am
by airguy
I have been unable to set up Freedns.afraid.org. I know I am putting all the info in correctly (other routers with DD-WRT is the same), but it always fails. Frustrating that it then deletes all the info, and you have to start all over again if it's unsuccessful on the update.
Running Gargoyle 1.5 on the WNDR3700.
Haven't tried DynDNS yet. Have that set up on another host on the network.
Re: Feature and DynDNS BUG
Posted: Tue Dec 06, 2011 11:25 am
by Eric
First, you say you're running 1.5 -- is that 1.5.0 or 1.5.1? There was a fix introduced in 1.5.1 and 1.4.4 for a known defect with freedns.afraid.org in 1.5.0 on the WNDR3700 (as well as all other ar71xx routers).
Second, make sure you are entering the username and password that you would use to login to the freedns.afraid.org site, not the "key" other update clients require. Gargoyle obtains the necessary key automatically from your freedns.afraid.org username/password/hostname.
Re: Feature and DynDNS BUG
Posted: Tue Dec 06, 2011 1:04 pm
by airguy
Sorry, I am running 1.5.0. Didn't know about 1.5.1. Just downloaded. Will try it again.
Thanks so much!!
***EDIT***
1.51 fixed it! Works great. Thanks again for all your hard work!
Re: Feature and DynDNS BUG
Posted: Sun Dec 11, 2011 5:41 am
by poldi1969
Eric wrote:Can you please try either 1.4.4 or 1.5.1? I've added some new fixes for dynamic dns that should fix this problem.
I have the same problem as @nickba
I've installed in the router gargoyle_1.5.1-ar71xx-tl-wr1043nd-v1-squashfs-factory.bin
Over several hours working ok. later I
Code: Select all
Dec 11 09:09:01 Gargoyle cron.err crond[2508]: USER root pid 4909 cmd /bin/3gtester
Dec 11 09:09:25 Gargoyle daemon.info hostapd: wlan0: STA 00:11:f5:xx:xx:xx WPA: group key handshake completed (RSN)
Dec 11 08:09:58 Gargoyle daemon.info ddns_gargoyle[1747]: Checking whether update needed:
Dec 11 08:09:58 Gargoyle daemon.info ddns_gargoyle[1747]: service provider=dyndns.com
Dec 11 08:09:58 Gargoyle daemon.info ddns_gargoyle[1747]: domain=xxxxx.xx.com
Dec 11 08:09:58 Gargoyle daemon.info ddns_gargoyle[1747]: local IP cannot be determined
Dec 11 08:09:58 Gargoyle daemon.info ddns_gargoyle[1747]: remote IP = 178.37.XXX.XXX
Dec 11 08:09:58 Gargoyle daemon.info ddns_gargoyle[1747]: Update failed
I noticed that the logs ddns time is switched