Re: Getting a Dinamic Remote IP
On Fri, May 20, 2005 at 08:49:50AM -0300, Romulo Sousa wrote:
> Hi there,
>
> I installed ddclient using apt-get but there is a error message when I
> run #ddclient -debug:
>
> myhostname:/# ddclient -debug
>
> DEBUG: get_ip: using if, eth0 reports 201.6.77.173
> WARNING: null password specified for host myhostname.homelinux.net.
> yoda:/home/rssousa# ddclient -debug
> DEBUG: get_ip: using if, eth0 reports 201.6.77.173
> WARNING: null password specified for host myhostname.homelinux.net.
> DEBUG:
> DEBUG: nic_dyndns2_update -------------------
> FAILED: updating d4: authorization failed (HTTP/1.1 401 Authorization Required
> FAILED: Date: Fri, 20 May 2005 11:39:49 GMT
> FAILED: Server: Apache/1.3.31 (Unix) mod_perl/1.29
> FAILED: WWW-Authenticate: Basic realm="DynDNS Members NIC"
> FAILED: Content-Type: text/html; charset=iso-8859-1
> FAILED: Connection: close
> FAILED:
> FAILED: badauth)
>
> I tried to edit /etc/ddclient.conf at hand but still the errors
> persist. I tried to run dpkg-reconfigure for default configurations
> take over my previously and it didn't work.
> I checked all the information a lot of times including password
> throughout the file /etc/ddclient:
>
> myhostname:/# cat /etc/ddclient.conf
> # Configuration file for ddclient generated by debconf
> #
> # /etc/ddclient.conf
>
> pid=/var/run/ddclient.pid
> protocol=dyndns2
> use=if, if=eth0
> custom=yes
> server=members.dyndns.org
> login=mylogin
> password=******
> myhostname.homelinux.net
Not sure why your authorization isn't working... but do you really
want "custom=yes"? I think that's if you have a domain other than the
ones offered by dyndns.org (in my config, I _don't_ have custom=yes,
and everything is fine with a *.homelinux.net hostname).
You could try whether a manual login/update works, pointing your
browser at (of course, first edit your parameters):
http://members.dyndns.org/nic/update?system=dyndns&hostname=yourhostname.homelinux.net&myip=1.2.3.4
That's essentially the URL that ddclient uses (not the regular web
interface). The usual HTTP-Basic-Auth popup dialog should appear,
where you can test the login/password combination you've specified in
the config file. Also, the browser should display a single-word error
message ("nohost", "!yours", "nochg", ...) if anything goes wrong with
the update...
Also, you might try to run "ddclient -debug -verbose" to get even more
verbose debugging messages.
Almut
Reply to: