WRT54GL - DDNS Problem [Solved]

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
Murrkf
DD-WRT Guru


Joined: 22 Sep 2008
Posts: 11200

PostPosted: Sun Aug 02, 2009 14:45    Post subject: Reply with quote
This seems important to me. We have had a lot of DDNS issues lately. Does this solve those?

Perhaps this information can be added to the wiki or a bug report filed in trac?

_________________
SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor. So See this:
http://i31.tinypic.com/24mz3ms.png

LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Sponsor
wabe
DD-WRT User


Joined: 17 Jun 2006
Posts: 380

PostPosted: Sun Aug 02, 2009 14:59    Post subject: Reply with quote
The mentioned "fix" does not help with latest Eko release. The DDNS log gets filled with error messages. My current ip is correct at dyndns however.
Glorymajor
DD-WRT Novice


Joined: 17 Jun 2009
Posts: 11

PostPosted: Sun Aug 02, 2009 23:04    Post subject: Reply with quote
Murrkf wrote:
This seems important to me. We have had a lot of DDNS issues lately. Does this solve those?

Perhaps this information can be added to the wiki or a bug report filed in trac?


Perhaps... But we need more ppl to test it.
I´ll be happy to forward this.

wabe wrote:
The mentioned "fix" does not help with latest Eko release. The DDNS log gets filled with error messages. My current ip is correct at dyndns however.


Maybe your problem is not quite mine.

I did got some error messages before, but after I configured NTP server and left domain name in blank, I got no more errors.

If you have a post with the details in it, I could try to help you out.
wabe
DD-WRT User


Joined: 17 Jun 2006
Posts: 380

PostPosted: Mon Aug 03, 2009 11:19    Post subject: Reply with quote
Here's a (small) selection of what appears in the DDNS log.
I'm using the proposed custom setup of Dyndns mentioned by one of the 'gurus´.

Mon Aug 3 06:49:26 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 06:49:26 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 487)
Mon Aug 3 07:58:30 2009: INADYN:IP: Error 0x91 in recv()
Mon Aug 3 07:58:30 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 07:58:30 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 492)
Mon Aug 3 09:25:53 2009: INADYN:IP: Error 0x83 in recv()
Mon Aug 3 09:25:53 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 09:25:53 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 500)
Mon Aug 3 11:47:41 2009: INADYN:IP: Error 0x83 in recv()
Mon Aug 3 11:47:41 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 11:47:41 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 514)
Glorymajor
DD-WRT Novice


Joined: 17 Jun 2009
Posts: 11

PostPosted: Tue Aug 04, 2009 2:07    Post subject: Reply with quote
wabe wrote:
Here's a (small) selection of what appears in the DDNS log.
I'm using the proposed custom setup of Dyndns mentioned by one of the 'gurus´.

Mon Aug 3 06:49:26 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 06:49:26 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 487)
Mon Aug 3 07:58:30 2009: INADYN:IP: Error 0x91 in recv()
Mon Aug 3 07:58:30 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 07:58:30 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 492)
Mon Aug 3 09:25:53 2009: INADYN:IP: Error 0x83 in recv()
Mon Aug 3 09:25:53 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 09:25:53 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 500)
Mon Aug 3 11:47:41 2009: INADYN:IP: Error 0x83 in recv()
Mon Aug 3 11:47:41 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 11:47:41 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 514)


Thats odd...
Yesterday I didnt got those messages... Today, I got the same errors messages too.. Argh! Shocked

Thu Jan 1 00:02:28 1970: I:INADYN: Alias 'alias.domain.net' to IP 'ip.here' updated successfully.
Mon Aug 3 19:25:26 2009: INADYN:IP: Error 0x83 in recv()
Mon Aug 3 19:25:26 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 19:25:26 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 46)
Mon Aug 3 20:52:03 2009: INADYN:IP: Error 0x91 in recv()
Mon Aug 3 20:52:03 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mon Aug 3 20:52:03 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 57)
Mon Aug 3 21:46:50 2009: INADYN:IP: Error 0x83 in recv()

Anyway, the DDNS service is up and running. I released my IP Address and renew it... DDNS was able to update it...

If your IP <> DNS can get along, nevermind to those msgs... Confused Probably will get fixed on later releases.
wjwj
DD-WRT User


Joined: 20 Sep 2008
Posts: 125

PostPosted: Tue Aug 04, 2009 17:29    Post subject: Reply with quote
Same problem here. I changed the password to something simpler (no special chars), now it works again.
_________________
1 x TP-Link WDR-4300 v1.1 (primary router running OpenWRT Attitude Adjustment)
1 x TP-Link WDR-3600 v1.4 (backup/testing router running latest OpenWRT bleeding edge)
wabe
DD-WRT User


Joined: 17 Jun 2006
Posts: 380

PostPosted: Tue Aug 04, 2009 22:04    Post subject: Reply with quote
I use a fairly simple password but no luck
phuque99
DD-WRT User


Joined: 20 Oct 2008
Posts: 446

PostPosted: Wed Aug 05, 2009 8:21    Post subject: Reply with quote
Just reviving this thread for discussion. The recent ddns issue we see on the log files appears to be actual dyndns server issue, not dd-wrt. I see the exact same inadyn errors in my Linux box that runs inadyn as a cron to update other hostnames.

I'm making an educated guess that the error happens when inadyn is unable to check for the actual public IP. I know that inadyn frequently to check if the public IP had changed by comparing with the one on cache. The default server used by inadyn is "checkip.dyndns.org:80"

The Dynamic DNS dd-wrt wiki page (http://www.dd-wrt.com/wiki/index.php/DDNS_-_How_to_setup_Custom_DDNS_settings_using_embedded_inadyn_-_HOWTO#DynDNS) suggested that custom settings can be used for dyndns.org, by using the custom "--ip_server_name checkip.dyndns.org:8245". This can be used on environments where a transparent proxy can mess up actual IP detection on port 80.

What I'm trying out today is to use the same custom ddns option above. But I've changed the ip_server_name option to

"--ip_server_name whatismyip.org:80"

This is working so far so I'll feedback if this eliminates the issue. If you're adventurous, please try this out. I'm not sure if "whatismyip.org:80" would be reliable enough. However if anyone know of other public IP checking URL, please share them.
rcblackwell
DD-WRT Novice


Joined: 18 Jun 2009
Posts: 40

PostPosted: Wed Aug 05, 2009 11:38    Post subject: Reply with quote
phuque99 wrote:
..... The recent ddns issue we see on the log files appears to be actual dyndns server issue, not dd-wrt. I see the exact same inadyn errors in my Linux box that runs inadyn as a cron to update other hostnames.


I'm not sure this is the case. I use OpenDNS (DNS-O-Matic) rather dyndns and see similar errors.


phuque99 wrote:
.....I'm making an educated guess that the error happens when inadyn is unable to check for the actual public IP. ........

What I'm trying out today is to use the same custom ddns option above. But I've changed the ip_server_name option to

"--ip_server_name whatismyip.org:80"

This is working so far so I'll feedback if this eliminates the issue.


I'd be very interested in your findings. If your results are good, I'll update my Router to the latest firmware and give this s try (with OpenDNS).
phuque99
DD-WRT User


Joined: 20 Oct 2008
Posts: 446

PostPosted: Wed Aug 05, 2009 12:08    Post subject: Reply with quote
rcblackwell wrote:
phuque99 wrote:
..... The recent ddns issue we see on the log files appears to be actual dyndns server issue, not dd-wrt. I see the exact same inadyn errors in my Linux box that runs inadyn as a cron to update other hostnames.


I'm not sure this is the case. I use OpenDNS (DNS-O-Matic) rather dyndns and see similar errors.


phuque99 wrote:
.....I'm making an educated guess that the error happens when inadyn is unable to check for the actual public IP. ........

What I'm trying out today is to use the same custom ddns option above. But I've changed the ip_server_name option to

"--ip_server_name whatismyip.org:80"

This is working so far so I'll feedback if this eliminates the issue.


I'd be very interested in your findings. If your results are good, I'll update my Router to the latest firmware and give this s try (with OpenDNS).


I think regardless what you choose as your dynamic DNS provider, dd-wrt will still use inadyn tool to check and update your IP with the site of your choice. The inadyn tool will use "checkip.dyndns.org:80" by default to check your public IP on certain intervals. This is what I believe is causing the errors that you see. That is the reason why I proposed testing an alternative IP lookup server.

Just keeping my fingers crossed, 4 hours so far and no errors on the ddns.log.
rcblackwell
DD-WRT Novice


Joined: 18 Jun 2009
Posts: 40

PostPosted: Wed Aug 05, 2009 14:03    Post subject: Reply with quote
phuque99 wrote:
I think regardless what you choose as your dynamic DNS provider, dd-wrt will still use inadyn tool to check and update your IP with the site of your choice. The inadyn tool will use "checkip.dyndns.org:80" by default to check your public IP on certain intervals. This is what I believe is causing the errors that you see. That is the reason why I proposed testing an alternative IP lookup server.

Just keeping my fingers crossed, 4 hours so far and no errors on the ddns.log.


Now I understand; I missed the fact that inadyn uses checkip.dyndns.org to determine your IP before updating the DNS service provider. I'd be interested in knowing why versions of DD-WRT subsequent to build 12533 (I think this is the correct build number) present errors when 12533 doesn't?

I hope your results are favourable as I'd like to move to the latest version of DD-WRT.
phuque99
DD-WRT User


Joined: 20 Oct 2008
Posts: 446

PostPosted: Wed Aug 05, 2009 14:16    Post subject: Reply with quote
rcblackwell wrote:

Now I understand; I missed the fact that inadyn uses checkip.dyndns.org to determine your IP before updating the DNS service provider. I'd be interested in knowing why versions of DD-WRT subsequent to build 12533 (I think this is the correct build number) present errors when 12533 doesn't?

I hope your results are favourable as I'd like to move to the latest version of DD-WRT.


I'm not going to re-load 12533 to check but if you're still running it, can you telnet / ssh into your router and share the default config for inadyn? Run the following (remember to censor your user name, password, hostname):

Code:

# cat /tmp/ddns/inadyn.conf
--background --dyndns_system custom@http_svr_basic_auth -u user -p password -a hostname.homeip.net --update_period_sec 600 --forced_update_period 864000 --log_file /tmp/ddns/ddns.log --cache_dir /tmp/ddns --exec ddns_success --dyndns_server_name members.dyndns.org --dyndns_server_url /nic/update? --dyndns_system dyndns@dyndns.org --ip_server_name whatismyip.org:80 /
rcblackwell
DD-WRT Novice


Joined: 18 Jun 2009
Posts: 40

PostPosted: Wed Aug 05, 2009 16:31    Post subject: Reply with quote
phuque99 wrote:
I'm not going to re-load 12533 to check but if you're still running it, can you telnet / ssh into your router and share the default config for inadyn?


Here ya go!

Code:
cat /tmp/ddns/inadyn.conf

--background --dyndns_system custom@http_svr_basic_auth -u user -p password hostname1.com -a hostname2 --update_period_sec 360 --forced_update_period 864000 --log_file /tmp/ddns/ddns.log --cache_dir /tmp/ddns --exec ddns_success --dyndns_server_name updates.dnsomatic.com --dyndns_server_url https://updates.opendns.com/nic/update?hostname=


Bob Blackwell
Pickering, ON


Last edited by rcblackwell on Wed Aug 05, 2009 21:06; edited 2 times in total
interconnect
DD-WRT User


Joined: 12 Jan 2007
Posts: 85

PostPosted: Wed Aug 05, 2009 16:38    Post subject: Reply with quote
this same thing is happening on my two WHR-G125's. I haven't made any changes in months and was updating correctly until recently. here is a snippet of my log:

Code:
Wed Aug 5 01:24:27 2009: INADYN:IP: Error 0x83 in recv()
Wed Aug 5 01:24:27 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Aug 5 01:24:27 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 6196)
Wed Aug 5 03:01:45 2009: INADYN:IP: Error 0x83 in recv()
Wed Aug 5 03:01:45 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Aug 5 03:01:45 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 6212)
Wed Aug 5 03:19:57 2009: INADYN:IP: Error 0x83 in recv()
Wed Aug 5 03:19:57 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Aug 5 03:19:57 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 6215)
Wed Aug 5 04:49:11 2009: INADYN:IP: Error 0x91 in recv()
Wed Aug 5 04:49:11 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Aug 5 04:49:11 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 6227)
Wed Aug 5 05:31:38 2009: INADYN:IP: Error 0x83 in recv()
Wed Aug 5 05:31:38 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Aug 5 05:31:38 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 6234)
Wed Aug 5 06:50:31 2009: INADYN:IP: Error 0x83 in recv()
Wed Aug 5 06:50:31 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Aug 5 06:50:31 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 6247)


and

Code:
Tue Jul 14 01:25:22 2009: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Tue Jul 14 01:25:22 2009: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 1077)
Tue Jul 14 01:34:34 2009: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Tue Jul 14 01:34:34 2009: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 1078)
Tue Jul 14 01:43:47 2009: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Tue Jul 14 01:43:47 2009: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 1079)
Tue Jul 14 01:53:00 2009: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Tue Jul 14 01:53:00 2009: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 1080)
Tue Jul 14 02:02:12 2009: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Tue Jul 14 02:02:12 2009: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 1081)
Tue Jul 14 02:11:25 2009: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Tue Jul 14 02:11:25 2009: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 1082)
Tue Jul 14 02:20:37 2009: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Tue Jul 14 02:20:37 2009: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 1083)


this goes back all the way to July 14th. Oddly though in between then and now it did do a successful update once or twice.

Code:
Thu Jul 30 02:41:40 2009: I:INADYN: IP address for alias 'xxxxxx.gotdns.com' needs update to 'xx.xxx.xxx.xxx'
Thu Jul 30 02:41:41 2009: I:INADYN: Alias 'xxxxxx.gotdns.com' to IP 'xx.xxx.xxx.xxx' updated successfully.
rcblackwell
DD-WRT Novice


Joined: 18 Jun 2009
Posts: 40

PostPosted: Wed Aug 05, 2009 23:14    Post subject: Reply with quote
rcblackwell wrote:
I'd be interested in knowing why versions of DD-WRT subsequent to build 12533 (I think this is the correct build number) present errors when 12533 doesn't?


Oh, oh! I spoke to soon! Not only did I get the build version wrong a recent check of the logs reveals it's full of errors Shocked .

The build I currently have loaded is 12188. When DDNS was configured on Sunday all was fine. Subsequent checks a few hours apart led me to believe all was well however early Monday morning the errors returned.

Looks as though the build has little if anything to do with this problem.
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum