Okay, done it... lets wait then...
--- "Frimmel, Ivan (ISS South Africa)" <[EMAIL PROTECTED]> a écrit : > Update_file.sh /etc/crontab and reboot > > > -----Original Message----- > From: Damien Dupertuis [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 01, 2005 7:03 AM > To: [email protected] > Subject: Re: [pfSense Support] DynDns scheduling > issues > > Hello, > > I'm using 95.a and I just got my dyndns account > banned... sorry I don't have time to put the logs > here... I'll do it tomorrow... > > regards > > --- Damien Dupertuis <[EMAIL PROTECTED]> a écrit : > > > Hello, > > > > just for the record, here are my system logs from > 94.12, if ever... It > > is not upgrading the adress properly... > > > > I'll upgrade to 0.95.a and keep you informed... > > > > regards... > > > > Damien > > > > > > > > --- Scott Ullrich <[EMAIL PROTECTED]> a écrit : > > > > > Please upgrade to 0.95.a > > > > > > On 11/29/05, Xtian <[EMAIL PROTECTED]> wrote: > > > > Howdy, > > > > > > > > I'm on .94.12 (fresh install), did the > following > > > as well: > > > > > > > > - update_file.sh /etc/inc/dyndns.class > > > > - Remove the cache file in > /cf/conf/dyndns.cache > > > (was not there, since new > > > > install) > > > > - update_file.sh /etc/crontab > > > > > > > > Dyndns still does bad stuff: > > > > > > > > Date: Tue, 29 Nov 2005 18:24:16 -0500 (EST) > > > > From: DynDNS Support <[EMAIL PROTECTED]> > > > > To: xxx > > > > Subject: Hostname Blocked Due To Abuse > > > > > > > > Dear Valued Customer: > > > > > > > > The hostname, xxx.dyndns.org, in account xxx, > > has > > > been > > > > blocked for abuse. This action has been taken > > due > > > to the receipt > > > > of multiple updates originating from the same > IP > > > address. > > > > > > > > Please note, updates which result in the IP > > > address associated > > > > with a host changing are NOT considered > abusive. > > > Only those > > > > updates which result in no change to the host > > are > > > abusive. > > > > Please take a moment to review our Update > Abuse > > > Policy here: > > > > > > > > http://www.dyndns.com/support/abuse.html > > > > > > > > It is vital that you correct the problem which > > is > > > resulting in > > > > these repeated and unnecessary updates. Once > you > > > have corrected > > > > this problem, you may request the host be > > > unblocked at the > > > > following URL: > > > > > > > > etc. etc. > > > > > > > > > > > > So, I took a look at the crontab for dyndns, > and > > > it was thusly: > > > > > > > > * */20 * * * root /usr/bin/nice > > -n20 > > > /etc/rc.dyndns.update > > > > > > > > According to cron's manpage: > > > > > > > > Step values can be used in conjunction > > > with ranges. Following a range > > > > with ''/<number>'' specifies skips of > > the > > > number's value through the > > > > range. For example, ''0-23/2'' > can > > > be used in the hours field to > > > > specify command execution every other > > hour > > > (the alternative in the V7 > > > > standard is > > > ''0,2,4,6,8,10,12,14,16,18,20,22''). Steps are > > also > > > per- > > > > mitted after an asterisk, so if you > want > > > to say ''every two hours'', > > > > just use ''*/2''. > > > > > > > > So, that'd be right bad to say */20 hours, > > meaning > > > every 20 hours, because > > > > typically, ADSL folks keep their connections > for > > > 24 hours and then get reset. > > > > Well, all of my DSL lines have always done > that. > > > Meaning, there's a good > > > > chance my IP stays stable for 24 hours, and > > every > > > 20 hours I send an update > > > > to DynDNS. Evidently DynDNS doesn't ever ever > > want > > > you to send them the same > > > > IP, ever. > > > > > > > > So, it doesn't make much sense to have any > kind > > of > > > regular DynDNS update, > > > > certainly not in cron. > > > > > > > > What should happen is that when your WAN link > > dies > > > and gets re-established, > > > > and pfSense figures out it has a new WAN IP, > > that > > > it should at that point > > > > send DynDNS its new WAN IP. Not at any other > > time. > > > > > > > > Well, thats one thing. Then looking at the > logs > > > just now before I send this, > > > > I see an entirely different problem: > > > > > > > > Nov 30 00:48:02 booji php: : DynDns: Running > > > updatedns() > > > > Nov 30 00:48:02 booji php: : DynDns: > updatedns() > > > starting > > > > Nov 30 00:48:02 booji php: : DynDns: > > > _detectChange() starting. > > > > Nov 30 00:48:02 booji php: : DynDns: Current > WAN > > > IP: xx.xx.xx.xx > > > > Nov 30 00:48:02 booji php: : DynDns: Cached > IP: > > > > Nov 30 00:48:02 booji php: : DynDns: cacheIP > != > > > wan_ip. Updating. > > > > Nov 30 00:48:02 booji php: : DynDns: More than > > 28 > > > days. Updating. > > > > Nov 30 00:48:02 booji php: : DynDns: DynDns > > > _update() starting. > > > > Nov 30 00:48:03 booji php: : DynDns: DynDns > > > _checkStatus() starting. > > > > Nov 30 00:48:03 booji php: : DynDns: Current > > > Service: dyndns > > > > Nov 30 00:48:03 booji php: : phpDynDNS: > PAYLOAD: > > > abuse > > > > Nov 30 00:48:03 booji php: : phpDynDNS: > (Unknown > > > Response) > > > > Nov 30 00:49:01 booji php: : DynDns: Running > > > updatedns() > > > > Nov 30 00:49:01 booji php: : DynDns: > updatedns() > > > starting > > > > Nov 30 00:49:01 booji php: : DynDns: > === message truncated === ___________________________________________________________________________ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
