root@DD-WRT:/tmp/ddns# nslookup dyna.dnsever.com
Segmentation fault
root@DD-WRT:/tmp/ddns# inadyn -u ***** -p ****** --verbose 5 --dyndns_system c
ustom@http_svr_basic_auth -a [home.namuk.com] --dyndns_server_name dyna.dnsever.
com --dyndns_server_url /update.php
Fri Apr 15 13:45:00 2011: INADYN: Started 'INADYN Advanced version 1.96-ADV' - d
ynamic DNS updater.
Fri Apr 15 13:45:00 2011: W: DYNDNS: My IP address: 110.12.76.49
Fri Apr 15 13:45:00 2011: I:INADYN: IP address for alias '[home.namuk.com]' need
s update to '110.12.76.49'
Segmentation fault
root@DD-WRT:/tmp/ddns#
As you can see, "Segmentation fault" occurs again and again.
root@DD-WRT:/tmp/ddns# nslookup dyna.dnsever.com
Segmentation fault
root@DD-WRT:/tmp/ddns# inadyn -u ***** -p ****** --verbose 5 --dyndns_system c
ustom@http_svr_basic_auth -a [home.namuk.com] --dyndns_server_name dyna.dnsever.
com --dyndns_server_url /update.php
Fri Apr 15 13:45:00 2011: INADYN: Started 'INADYN Advanced version 1.96-ADV' - d
ynamic DNS updater.
Fri Apr 15 13:45:00 2011: W: DYNDNS: My IP address: 110.12.76.49
Fri Apr 15 13:45:00 2011: I:INADYN: IP address for alias '[home.namuk.com]' need
s update to '110.12.76.49'
Segmentation fault
root@DD-WRT:/tmp/ddns#
As you can see, "Segmentation fault" occurs again and again.
Who knows the solution?
When I use either '/lib/libc.so.0' or '/usr/sbin/inadyn' of r16454 and later, the "Segmantation fault" error occurs with inadyn.
The "Segmentation fault" error occurs when inadyn has to update the IP. If no update is required, inadyn just print the results well, but when update is excuted, the error occurs.
So I extract both '/lib/libc.so.0' and '/usr/sbin/inadyn' from lastest working version 'r16214', and it works fine.
Note that if you want to use the library which you extracted, you have to change the LD_LIBRARY_PATH variable with that path of extracted one. (so the simple script that changes the LD_LIBRARY path with the extracted one and then runs inadyn, is needed)
start_ddns
Code:
#!/bin/sh
export LD_LIBRARY_PATH=/jffs/sbin/inadyn/lib:$LD_LIBRARY_PATH
if [ ! -e '/tmp/ddns' ] ; then
mkdir /tmp/ddns
fi
killall -q inadyn
/jffs/sbin/inadyn/inadyn --input_file /jffs/sbin/inadyn/inadyn.conf
stop_ddns
Code:
#!/bin/sh
killall -q inadyn
I stored the libc.so.0 of r16214 to /jffs/sbin/inadyn/lib and
inadyn of r16214 to /jffs/sbin/inadyn.
"Segmentation fault" seems both the Inadyn itself(compile option problem?) and library's problem,
but anyway, if you extract the last working version from r16214, it works ^^
But I just focus on 'inadyn' problem, so
when I apply the '/lib/libc.so.0' of r16214 to the nslookup, another error occurs
nslookup: can't resolve symbol '__res_state' in lib 'nslookup'.
It seems the Library Problem which causes the "Segmentation fault" with several binaries on r16454+,
So I want DD-WRT Developers to find out the reason and fix it.
root@DD-WRT:/tmp/ddns# nslookup dyna.dnsever.com
Segmentation fault
root@DD-WRT:/tmp/ddns# inadyn -u ***** -p ****** --verbose 5 --dyndns_system c
ustom@http_svr_basic_auth -a [home.namuk.com] --dyndns_server_name dyna.dnsever.
com --dyndns_server_url /update.php
Fri Apr 15 13:45:00 2011: INADYN: Started 'INADYN Advanced version 1.96-ADV' - d
ynamic DNS updater.
Fri Apr 15 13:45:00 2011: W: DYNDNS: My IP address: 110.12.76.49
Fri Apr 15 13:45:00 2011: I:INADYN: IP address for alias '[home.namuk.com]' need
s update to '110.12.76.49'
Segmentation fault
root@DD-WRT:/tmp/ddns#
As you can see, "Segmentation fault" occurs again and again.
Who knows the solution?
When I use either '/lib/libc.so.0' or '/usr/sbin/inadyn' of r16454 and later, the "Segmantation fault" error occurs with inadyn.
The "Segmentation fault" error occurs when inadyn has to update the IP. If no update is required, inadyn just print the results well, but when update is excuted, the error occurs.
So I extract both '/lib/libc.so.0' and '/usr/sbin/inadyn' from lastest working version 'r16214', and it works fine.
Note that if you want to use the library which you extracted, you have to change the LD_LIBRARY_PATH variable with that path of extracted one. (so the simple script that changes the LD_LIBRARY path with the extracted one and then runs inadyn, is needed)
start_ddns
Code:
#!/bin/sh
export LD_LIBRARY_PATH=/jffs/sbin/inadyn/lib:$LD_LIBRARY_PATH
if [ ! -e '/tmp/ddns' ] ; then
mkdir /tmp/ddns
fi
killall -q inadyn
/jffs/sbin/inadyn/inadyn --input_file /jffs/sbin/inadyn/inadyn.conf
stop_ddns
Code:
#!/bin/sh
killall -q inadyn
I stored the libc.so.0 of r16214 to /jffs/sbin/inadyn/lib and
inadyn of r16214 to /jffs/sbin/inadyn.
"Segmentation fault" seems both the Inadyn itself(compile option problem?) and library's problem,
but anyway, if you extract the last working version from r16214, it works ^^
But I just focus on 'inadyn' problem, so
when I apply the '/lib/libc.so.0' of r16214 to the nslookup, another error occurs
nslookup: can't resolve symbol '__res_state' in lib 'nslookup'.
It seems the Library Problem which causes the "Segmentation fault" with several binaries on r16454+,
So I want DD-WRT Developers to find out the reason and fix it.
Thanks.
Thanks for your reply.
As you told, I think there's a problem w/ new F/W.
I posted this problem @ bugtracker. I hope it'd be fixed soon.
I can see you live in Seoul, Korea. I'm Korean, too.
I doubt there're some hardware difference between sold in Korea and internationally.
i can confirm this bug. well, first update went right, then i got the seg-fault. _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
if [ "${OLD_IP}" != "${NOW_IP}" ]; then
echo "Old IP ${OLD_IP} does not match new IP of ${NOW_IP}"
/usr/bin/wget -O /dev/null http://rodney:3z1PvQZmBDI7pZ8IKpNIQpRXwHk8tF@members.dyndns.org/nic/update?hostname=${DYNDNS_ALIAS}
fi
if [ "${OLD_IP}" != "${NOW_IP}" ]; then
echo "Old IP ${OLD_IP} does not match new IP of ${NOW_IP}"
/usr/bin/wget -O /dev/null http://rodney:3z1PvQZmBDI7pZ8IKpNIQpRXwHk8tF@members.dyndns.org/nic/update?hostname=${DYNDNS_ALIAS}
fi
I have to use nkoriyama's version on my Asus RT-N16 running DD-WRT build 17201, your version relies on nslookup which has a "Segmentation fault" on run.
Since DynDNS went commercial and is no longer free I had to switch to no-ip, which offers up to 3 free host name records. To get the script to work with no-ip, just changed the wget statement to this (replace username, password and mydnsalias.myhost.com to values that are valid for your no-ip account):
Since DynDNS went commercial and is no longer free I had to switch to no-ip, which offers up to 3 free host name records. To get the script to work with no-ip, just changed the wget statement to this (replace username, password and mydnsalias.myhost.com to values that are valid for your no-ip account):
DynDNS, or DYN.com how it is called today, still offers a free single dynamic hostname service.
The only "problem" is that you first have to trial their pro product for 14, which means registering with your credit card. Once you cancel after the 14 days, you can keep one hostname for free, and loose all the pro features.
Also for anyone who already had an account with DynDNS before, nothing has changed since then.
They still keep their alias, there was only a change in the available free domains to choose from.
Since DynDNS went commercial and is no longer free I had to switch to no-ip, which offers up to 3 free host name records. To get the script to work with no-ip, just changed the wget statement to this (replace username, password and mydnsalias.myhost.com to values that are valid for your no-ip account):
DynDNS, or DYN.com how it is called today, still offers a free single dynamic hostname service.
The only "problem" is that you first have to trial their pro product for 14, which means registering with your credit card. Once you cancel after the 14 days, you can keep one hostname for free, and loose all the pro features.
Also for anyone who already had an account with DynDNS before, nothing has changed since then.
They still keep their alias, there was only a change in the available free domains to choose from.
They used to offer 5 free host names. I was at 5 and later decided to delete one and replace it with another didn't work, so I deleted another. Apparently they changed their policy that they only allowed one free host name but gave no warning when I deleted an existing one as an old grandfathered user and I lost two that way. Then I somehow lost my last remaining one with no email warning why and I couldn't re-create it without giving my credit card info. That's not my definition of free or even a good service, no thanks. No-ip provides up to three free host names under one account and doesn't require you to give them a cc number. I'm recommending all the people I know that use dyndns to switch. That's not how you treat legacy users.
