noip2 drives me crazy...

[Stickan]

Hi!

I've tried and tried virtually everything to get noip2 to periodically update to keep my no-ip account active but never succeed. I've just started to use Debian so my source of knowledge is definitely depleted by now...

What I've done so far is:
- build the executable
- installed it (so I have the bash script /etc/init.d/noip2)
- added it to startup as /etc/rc2.d/S95noip2 -> ../init.d/noip2
- added it to shutdown as /etc/rc2.d/K05noip2 -> ../init.d/noip2
- configured it for 5 minutes update interval by running noip2 -C
- started it. ps -A gives:
...
1168 tty6 00:00:00 getty
28379 pts/0 00:00:00 bash
28532 ? 00:00:00 noip2
...

and after starting it I get one entry in daemon.log
localhost noip2[28532]: v2.1.7 daemon started with NAT enabled
localhost noip2[28532]: xxx.no-ip.org was already set to xxx.xxx.xxx.xxx.

but that's it (unless I restart the machine)...

I never get any new log entries and of course no-ip is bugging me over and over that I have to manually confirm that my account still is active or it would be deleted.

Please, have anybody a clue on what have I missed?

[athlon_crazy]

1) Did you check when your IP changed & noip will update it too? No log entries meaning there is no new ip for update!

2) As long u r running 'noip2 -C" with correct username & password as per your account in noip.com, it shouldn't be happened (account active)

[Stickan]

Are you sure athlon? Why is no-ip sending me those activation mails if the service is kept active by noip2?

My ip very rarely change so I can't use that to detect noip2 activity.

[athlon_crazy]

Yes for sure if no update transaction been made, I suspect you hav outgoing communication problem with no-ip. Please look into noip update client port 8245, maybe your firewall block the port.

[vk4akp]

I came across this problem also.

The reason for the problem is when you reboot your system or re run the update No-IP only allows polling once every so many minutes so the updater borks and resets the IP to 0.0.0.0


I am running Sabayon Linux (Enhanced Gentoo) so things will be a little different for your flavour of Linux.

You will need to update to the latest No-IP Updater (2.1.9)

Then remark out some of the script lines.

Don't forget to add to runlevels.

The following is from my notes when I ran into the same problem.


---
No-IP - 0.0.0.0 fix. ;; Latest version gets around vulnerabilities.

mkdir /usr/src/noip

wget h t t p : / / w w w . no-ip.com/client/linux/noip-duc-linux.tar.gz

tar xvf noip-duc-linux.tar.gz

make

make install

;; copy over old in /usr/sbin/noip2

;; Edit out all the 0.0.0.0 crap in the /etc/init.d/noip from the old portage version.

#! ebegin "Setting noip addresses to 0.0.0.0"
#! noip2 -c /etc/no-ip2.conf -i 0.0.0.0 >& /dev/null
#! eend $? "Failed to set noip addresses to 0.0.0.0, error $?"


;; ~ FIXED!! ~

noip2 -Sd ;; Shows Status.
---

I still get messages from No-IP saying I haven't updated at times within the past 60 days but I do wonder if it's their system as the date they send me for the last known update is less then 60 days. LOLz.

Hope this helps. If anyone can help further I too wold like to hear more on this.


~Ken~
.-.-.