DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP

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


Joined: 27 Jul 2009
Posts: 69

PostPosted: Sat Aug 01, 2009 0:44    Post subject: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP Reply with quote
hit
i tried everything i found here. but i cant fix it. it keeps saying that error.
i have wrt150n v. 1.1 with dd-wrt firmware

any help?
Sponsor
rcblackwell
DD-WRT Novice


Joined: 18 Jun 2009
Posts: 40

PostPosted: Sat Aug 01, 2009 12:06    Post subject: Re: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to Reply with quote
eleze14 wrote:
hit
i tried everything i found here. but i cant fix it. it keeps saying that error.
i have wrt150n v. 1.1 with dd-wrt firmware

any help?


Build: 12533
WRT150N v1

I'm having the same issue and have tried all settings mentioned in threads found at;

http://www.dd-wrt.com/phpBB2/viewtopic.php?p=273200#273200

http://www.dd-wrt.com/forum/viewtopic.php?p=177392&sid=4cc6410c469d5895e1357e3876230ea2

as well as a few others. I don't recall seeing this issue with build 12188 which was replaced with 12533 about a week ago.

DDNS is configured as follows;

DDNS Service - Custom
DYNDNS Server - updates.dnsomatic.com
User Name - <username>
Password - <password>
Host Name - hostname1.com -a hostename2.com
URL - /nic/update?&wildcard=ON&mx=NOCHG&backmx=NOCHG&hostname=



I'm using ntp with time.nrc.ca. INADYN is successful upon router restart however it fails a few hours later then continues to do so until the router is restarted.

Update: I've added my concern to TRAC incident 1145. I'd encourage others to do the same. (Refer to http://svn.dd-wrt.com:8000/dd-wrt/ticket/1145)

Bob Blackwell
Pickering, ON


Last edited by rcblackwell on Sun Aug 02, 2009 0:22; edited 3 times in total
Z0r0b
DD-WRT Novice


Joined: 10 Jul 2009
Posts: 24

PostPosted: Sat Aug 01, 2009 12:17    Post subject: Reply with quote
I'm having the same issue on 12307M VINT Eko. Think it started about a week ago.
dellsweig
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 1476
Location: New York, USA

PostPosted: Sat Aug 01, 2009 15:26    Post subject: Re: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to Reply with quote
eleze14 wrote:
hit
i tried everything i found here. but i cant fix it. it keeps saying that error.
i have wrt150n v. 1.1 with dd-wrt firmware

any help?


Yep - I can concur - this problem is BACK with 12548

It was fixed for a few builds but now its back....
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2026
Location: Sol System > Earth > USA > Arkansas

PostPosted: Sat Aug 01, 2009 19:56    Post subject: Reply with quote
Yes, it does seem that the DDNS update problems have come back with the 'default' router settings for the service. While I realize the problem may not be "high" priority, I really wish it could be fixed soon. My log goes as follows:

Quote:
DDNS Status
Mon Jul 27 12:51:13 2009: INADYN: Started 'INADYN Advanced version 1.96-ADV' - dynamic DNS updater.
Mon Jul 27 12:51:13 2009: INADYN: IP read from cache file is '69.xx.xx.xx'. No update required.
Tue Jul 28 07:04:46 2009: INADYN:IP: Error 0x83 in recv()
Tue Jul 28 07:04:46 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Tue Jul 28 07:04:46 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 108)
Tue Jul 28 11:03:15 2009: INADYN:IP: Error 0x91 in recv()
Tue Jul 28 11:03:15 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Tue Jul 28 11:03:15 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 130)
Tue Jul 28 12:20:04 2009: INADYN:IP: Error 0x91 in recv()
Tue Jul 28 12:20:04 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Tue Jul 28 12:20:04 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 136)
Tue Jul 28 17:59:37 2009: INADYN:IP: Error 0x91 in recv()
Tue Jul 28 17:59:37 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Tue Jul 28 17:59:37 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 168)
Tue Jul 28 18:29:56 2009: I:INADYN: IP address for alias 'someplace.xxx.com' needs update to '69.xx.xx.xx'
Tue Jul 28 18:29:56 2009: I:INADYN: Alias 'someplace.xxx.com' to IP '69.xx.xx.xx' updated successfully.
Tue Jul 28 19:06:22 2009: INADYN:IP: Error 0x91 in recv()
Tue Jul 28 19:06:22 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Tue Jul 28 19:06:22 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 173)
Tue Jul 28 21:03:37 2009: INADYN:IP: Error 0x91 in recv()
Tue Jul 28 21:03:37 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Tue Jul 28 21:03:37 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 183)
Wed Jul 29 08:16:51 2009: INADYN:IP: Error 0x91 in recv()
Wed Jul 29 08:16:51 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Jul 29 08:16:51 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 248)
Wed Jul 29 09:23:34 2009: INADYN:IP: Error 0x91 in recv()
Wed Jul 29 09:23:34 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Jul 29 09:23:34 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 253)
Wed Jul 29 12:05:13 2009: INADYN:IP: Error 0x83 in recv()
Wed Jul 29 12:05:13 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Jul 29 12:05:13 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 269)
Wed Jul 29 14:46:52 2009: INADYN:IP: Error 0x83 in recv()
Wed Jul 29 14:46:52 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Jul 29 14:46:52 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 285)
Wed Jul 29 15:53:35 2009: INADYN:IP: Error 0x91 in recv()
Wed Jul 29 15:53:35 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Jul 29 15:53:35 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 290)
Wed Jul 29 21:37:20 2009: INADYN:IP: Error 0x83 in recv()
Wed Jul 29 21:37:20 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Jul 29 21:37:20 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 324)
Wed Jul 29 23:04:16 2009: INADYN:IP: Error 0x91 in recv()
Wed Jul 29 23:04:16 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Wed Jul 29 23:04:16 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 331)
Thu Jul 30 12:24:13 2009: INADYN:IP: Error 0x83 in recv()
Thu Jul 30 12:24:13 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jul 30 12:24:13 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 410)
Thu Jul 30 14:11:26 2009: INADYN:IP: Error 0x91 in recv()
Thu Jul 30 14:11:26 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jul 30 14:11:26 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 419)
Thu Jul 30 18:06:57 2009: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Thu Jul 30 18:06:57 2009: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 442)
Thu Jul 30 18:57:29 2009: INADYN:IP: Error 0x83 in recv()
Thu Jul 30 18:57:29 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jul 30 18:57:29 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 447)
Thu Jul 30 19:07:35 2009: INADYN:IP: Error 0x83 in recv()
Thu Jul 30 19:07:35 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jul 30 19:07:35 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 448)
Thu Jul 30 19:27:49 2009: INADYN:IP: Error 0x83 in recv()
Thu Jul 30 19:27:49 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jul 30 19:27:49 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 450)
Thu Jul 30 23:31:52 2009: INADYN:IP: Error 0x83 in recv()
Thu Jul 30 23:31:52 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jul 30 23:31:52 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 474)
Thu Jul 30 23:52:04 2009: I:INADYN: IP address for alias 'someplace.xxx.com' needs update to '69.xx.xx.xx'
Thu Jul 30 23:52:04 2009: I:INADYN: Alias 'someplace.xxx.com' to IP '69.xx.xx.xx' updated successfully.
Fri Jul 31 02:43:57 2009: INADYN:IP: Error 0x83 in recv()
Fri Jul 31 02:43:57 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jul 31 02:43:57 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 492)
Fri Jul 31 03:04:09 2009: INADYN:IP: Error 0x83 in recv()
Fri Jul 31 03:04:09 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jul 31 03:04:09 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 494)
Fri Jul 31 09:53:55 2009: INADYN:IP: Error 0x83 in recv()
Fri Jul 31 09:53:55 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jul 31 09:53:55 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 533)
Fri Jul 31 18:04:57 2009: INADYN:IP: Error 0x91 in recv()
Fri Jul 31 18:04:57 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jul 31 18:04:57 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 580)
Fri Jul 31 19:11:44 2009: INADYN:IP: Error 0x91 in recv()
Fri Jul 31 19:11:44 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jul 31 19:11:44 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 585)
Fri Jul 31 19:31:57 2009: INADYN:IP: Error 0x83 in recv()
Fri Jul 31 19:31:57 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jul 31 19:31:57 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 587)
Fri Jul 31 21:53:23 2009: INADYN:IP: Error 0x83 in recv()
Fri Jul 31 21:53:23 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Fri Jul 31 21:53:23 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 601)
Sat Aug 1 00:25:12 2009: INADYN:IP: Error 0x83 in recv()
Sat Aug 1 00:25:12 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sat Aug 1 00:25:12 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 616)
Sat Aug 1 02:40:43 2009: INADYN:IP: Error 0x83 in recv()
Sat Aug 1 02:40:43 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sat Aug 1 02:40:43 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 628)
Sat Aug 1 14:07:41 2009: INADYN:IP: Error 0x83 in recv()
Sat Aug 1 14:07:41 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sat Aug 1 14:07:41 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 696)
Sat Aug 1 21:12:01 2009: INADYN:IP: Error 0x83 in recv()
Sat Aug 1 21:12:01 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sat Aug 1 21:12:01 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 738)
Sat Aug 1 22:03:04 2009: INADYN:IP: Error 0x83 in recv()
Sat Aug 1 22:03:04 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sat Aug 1 22:03:04 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 743)
Sat Aug 1 23:23:55 2009: INADYN:IP: Error 0x83 in recv()
Sat Aug 1 23:23:55 2009: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Sat Aug 1 23:23:55 2009: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 751)

_________________
E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]

Try Dropbox for syncing files - get 2.5gb online for free by signing up.

Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
eleze14
DD-WRT User


Joined: 27 Jul 2009
Posts: 69

PostPosted: Sun Aug 02, 2009 2:45    Post subject: Re: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to Reply with quote
dellsweig wrote:
eleze14 wrote:
hit
i tried everything i found here. but i cant fix it. it keeps saying that error.
i have wrt150n v. 1.1 with dd-wrt firmware

any help?


Yep - I can concur - this problem is BACK with 12548

It was fixed for a few builds but now its back....


so there is no way to fix it??
wpinegar
DD-WRT User


Joined: 09 Jul 2006
Posts: 55

PostPosted: Sat Aug 08, 2009 0:29    Post subject: Reply with quote
This isn't a problem with INADYN on DD-WRT. It's an issue with http://checkip.dyndns.com/. This is the default site that INADYN connects to determine if your IP address has changed. The site doesn't respond several times a day or simply closes the connection before returning the IP address. It looks like these server simply cannot keep up with the traffic. You can get more details on what INADYN is doing by adding '--verbose 5' to the additional DDNS options.

It might be a good time to look for other checkip services and use the '--ip_server_name' DDNS option to change the server to use as an address checker. You could also slow INADYN down so that it doesn't check quite so often using the option '--update_period_sec 1800' (this check every 30 seconds).

You can also simply ignore the errors. The errors are just letting you know that occasionally INADYN cannot resolve your IP address. On the next iteration it try again and it generally succeeds. Not a big deal either way.
phuque99
DD-WRT User


Joined: 20 Oct 2008
Posts: 446

PostPosted: Sat Aug 08, 2009 0:46    Post subject: Reply with quote
You can try the workaround I posted here:

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=53539&postdays=0&postorder=asc&highlight=ddns&start=30
wpinegar
DD-WRT User


Joined: 09 Jul 2006
Posts: 55

PostPosted: Sat Aug 08, 2009 20:14    Post subject: Reply with quote
Here are the DDNS options that I am using and I don't have any errors with INADYN. My IP address doesn't change very often so I only check the IP address every 30 minutes. Try to keep the traffic lite so we don't have to find yet another IP address checking web site... Wink
    --update_period_sec 1800 --ip_server_name checkip.two-dns.de:80 /
Something that I'm wondering. Why isn't there an option to have INADYN simply check the IP address assigned to the WAN interface? I know this wouldn't work for everyone but it would sure work for most people.
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2026
Location: Sol System > Earth > USA > Arkansas

PostPosted: Sat Aug 08, 2009 22:07    Post subject: Reply with quote
wpinegar wrote:
Why isn't there an option to have INADYN simply check the IP address assigned to the WAN interface? I know this wouldn't work for everyone but it would sure work for most people.


Honestly, I myself did not realize that is what was done. Maybe we should petition for an "enhancement" that would check the WAN IP address instead of bugging other websites about it. Use it as a 'checkmarkable' item. A. Checked - use the WAN IP address B. Unchecked - use standard website method.

_________________
E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]

Try Dropbox for syncing files - get 2.5gb online for free by signing up.

Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
phuque99
DD-WRT User


Joined: 20 Oct 2008
Posts: 446

PostPosted: Sun Aug 09, 2009 2:24    Post subject: Reply with quote
if you're wondering, inadyn is not a dd-wrt-only tool. it is a regular open source tool that you can run off unix machines that will not have a "WAN IP" to check. thus it is using the generic way of reaching out somewhere on the Internet to get a public IP response.

i don't think it is so serious that requires a code change on the inadyn tool, since one could simply ignore the errors or use the workaround.
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2026
Location: Sol System > Earth > USA > Arkansas

PostPosted: Sun Aug 09, 2009 7:05    Post subject: Reply with quote
Can you not run a command inside of a command? By that, linux (and other unix variants) have the capacity for running a command (such as 'date') which will return information to the command line to be used *for* the rest of the command line. In many instances, that allows something like a backup program (for the 'date' instance) to make unique files per file date.

Does the command line of DD-WRT have something like that which would return the WAN IP address when it is called? If so, that could *easily* be implemented into the DDNS command line. Assuming that option is wanted, then there could be a checkmark for using the IP address that the router sees, or if it is unchecked, then use the original external IP checking.

_________________
E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]

Try Dropbox for syncing files - get 2.5gb online for free by signing up.

Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
phuque99
DD-WRT User


Joined: 20 Oct 2008
Posts: 446

PostPosted: Sun Aug 09, 2009 7:21    Post subject: Reply with quote
crashfly wrote:
Can you not run a command inside of a command? By that, linux (and other unix variants) have the capacity for running a command (such as 'date') which will return information to the command line to be used *for* the rest of the command line. In many instances, that allows something like a backup program (for the 'date' instance) to make unique files per file date.

Does the command line of DD-WRT have something like that which would return the WAN IP address when it is called? If so, that could *easily* be implemented into the DDNS command line. Assuming that option is wanted, then there could be a checkmark for using the IP address that the router sees, or if it is unchecked, then use the original external IP checking.


yes you can simply awk the WAN IP from nvram show, but inadyn does not seem to support using an IP from the command line. unless i missed something, i don't see it on the man pages.

inadyn is a public open source tool. i believe dd-wrt is just using the tool as-is without modifying anything, just to avoid re-inventing the wheel and also making things modular. i doubt this small little cosmetic issue and intermittent problem that has nothing to do with dd-wrt code would warrant the dev's time to actually modify an open source tool to fix a problem that is not even their issue.
wpinegar
DD-WRT User


Joined: 09 Jul 2006
Posts: 55

PostPosted: Sun Aug 09, 2009 20:47    Post subject: Reply with quote
I agree. This really isn't a major change. It would be quite easy to modify the IP addressing checking code in INADYN to simply look in nvram for the WAN IP address. It seems a bit wasteful to ping an external web site for information that in most instances the router already has...

Quote:
crashfly wrote:
Can you not run a command inside of a command? By that, linux (and other unix variants) have the capacity for running a command (such as 'date') which will return information to the command line to be used *for* the rest of the command line. In many instances, that allows something like a backup program (for the 'date' instance) to make unique files per file date.

Does the command line of DD-WRT have something like that which would return the WAN IP address when it is called? If so, that could *easily* be implemented into the DDNS command line. Assuming that option is wanted, then there could be a checkmark for using the IP address that the router sees, or if it is unchecked, then use the original external IP checking.
rcblackwell
DD-WRT Novice


Joined: 18 Jun 2009
Posts: 40

PostPosted: Mon Aug 10, 2009 0:19    Post subject: Reply with quote
wpinegar wrote:
Here are the DDNS options that I am using and I don't have any errors with INADYN.
    --update_period_sec 1800 --ip_server_name checkip.two-dns.de:80 /

I tried your suggestion with a different ip_server_name (To keep the load spread out amongst providers Wink ). This suggestion seems to be working well thus far.

Thank you.

Bob
Pickering, ON
Goto page 1, 2, 3, 4  Next Display posts from previous:    Page 1 of 4
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