Re: [pfSense Support] DynDns scheduling issues
Yep, it should. On 12/20/05, Kevin Wolf <[EMAIL PROTECTED]> wrote: > Alright. So doing a full install with the latest ISO should probably > fix this then, right? I was going to do that anyway within the next few > days. > > Scott Ullrich wrote: > > >This is the old version. The newer version has more debugging information. > > > >Scott > > > > > >On 12/20/05, Kevin Wolf <[EMAIL PROTECTED]> wrote: > > > > > >>You all sure this is solved? I'm using 0.96.2 and I see a lot of this > >>in my log: > >> > >>Dec 19 01:01:02 php: : phpDynDNS: (Success) No Change In IP Address > >>Dec 19 01:01:02 php: : DynDns: Current Service: dyndns > >>Dec 19 01:01:02 php: : DynDns: DynDns _checkStatus() starting. > >>Dec 19 01:01:01 php: : DynDns: DynDns _update() starting. > >>Dec 19 01:01:01 php: : DynDns: More than 28 days. Updating. > >>Dec 19 01:01:01 php: : DynDns: cacheIP != wan_ip. Updating. > >>Dec 19 01:01:01 php: : DynDns: Cached IP: > >>Dec 19 01:01:01 php: : DynDns: Current WAN IP: 68.7.149.### > >>Dec 19 01:01:01 php: : DynDns: _detectChange() starting. > >>Dec 19 01:01:01 php: : DynDns: updatedns() starting > >>Dec 19 01:01:01 php: : DynDns: Running updatedns() > >>Dec 19 00:01:21 php: : phpDynDNS: (Success) No Change In IP Address > >>Dec 19 00:01:21 php: : DynDns: Current Service: dyndns > >>Dec 19 00:01:21 php: : DynDns: DynDns _checkStatus() starting. > >>Dec 19 00:01:01 php: : DynDns: DynDns _update() starting. > >>Dec 19 00:01:01 php: : DynDns: More than 28 days. Updating. > >>Dec 19 00:01:01 php: : DynDns: cacheIP != wan_ip. Updating. > >>Dec 19 00:01:01 php: : DynDns: Cached IP: > >>Dec 19 00:01:01 php: : DynDns: Current WAN IP: 68.7.149.### > >>Dec 19 00:01:01 php: : DynDns: _detectChange() starting. > >>Dec 19 00:01:01 php: : DynDns: updatedns() starting > >>Dec 19 00:01:01 php: : DynDns: Running updatedns() > >> > >> > >>And I just got my dyndns account blocked for this. > >> > >>Dear Valued Customer: > >> > >>The hostname, ###.mine.nu, in account , has been blocked for > >>abuse. This action has been taken due to the receipt of multiple updates > >>originating from the same IP address. > >> > >> > >>Unless this was fixed after 0.96.2? > >> > >>Damien Dupertuis wrote: > >> > >> > >> > >>>No problem :-) > >>> > >>>Believe me!!! we are also wery happy you finally > >>>killed the nasty bug!!! > >>> > >>>Thank you very much!!! > >>> > >>>Regards > >>> > >>>Damien > >>> > >>> > >>>--- Scott Ullrich <[EMAIL PROTECTED]> a écrit : > >>> > >>> > >>> > >>> > >>> > Thanks for the replies. > > I have to say that I am really glad this problem is > solved. I've lost > many hair to grey due to these bugs. > > Scott > > On 12/10/05, Ispánovits Imre > <[EMAIL PROTECTED]> wrote: > > > > > >On Sat, 10 Dec 2005 18:22:55 +0100 (CET) > >Damien Dupertuis <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > >>Hello, > >> > >>It has been working for two days and a half now > >> > >> > >> > >> > and > > > > > >>I'm not banned , my adress is upgraded correctly > >> > >> > >> > >> > so I > > > > > >>assume the bug is killed... > >> > >>Thank you!!! > >> > >>Damien > >> > >> > >> > >> > >> > >Hi, > > > >I can confirm as well. In v95.4 works fine. My ISP > > > > > > > > > just now changed my ip > > > > > >address and this event triggered DynDns-update > > > > > > > > > correctly. > > > > > >THX > > > >Imre > > > > > >-- > >This is Linux Land. > >In silent nights you can hear the windows machines > > > > > > > > > rebooting > > > > > > > > > > > > > >>>- > >>> > >>> > >>> > >>> > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > >>> > >>> > >>> > >>> > >>> > >>>___ > >>>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] > >>> > >>> > >>> > >>> > >>> > >>> > >>- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] DynDns scheduling issues
Alright. So doing a full install with the latest ISO should probably fix this then, right? I was going to do that anyway within the next few days. Scott Ullrich wrote: This is the old version. The newer version has more debugging information. Scott On 12/20/05, Kevin Wolf <[EMAIL PROTECTED]> wrote: You all sure this is solved? I'm using 0.96.2 and I see a lot of this in my log: Dec 19 01:01:02 php: : phpDynDNS: (Success) No Change In IP Address Dec 19 01:01:02 php: : DynDns: Current Service: dyndns Dec 19 01:01:02 php: : DynDns: DynDns _checkStatus() starting. Dec 19 01:01:01 php: : DynDns: DynDns _update() starting. Dec 19 01:01:01 php: : DynDns: More than 28 days. Updating. Dec 19 01:01:01 php: : DynDns: cacheIP != wan_ip. Updating. Dec 19 01:01:01 php: : DynDns: Cached IP: Dec 19 01:01:01 php: : DynDns: Current WAN IP: 68.7.149.### Dec 19 01:01:01 php: : DynDns: _detectChange() starting. Dec 19 01:01:01 php: : DynDns: updatedns() starting Dec 19 01:01:01 php: : DynDns: Running updatedns() Dec 19 00:01:21 php: : phpDynDNS: (Success) No Change In IP Address Dec 19 00:01:21 php: : DynDns: Current Service: dyndns Dec 19 00:01:21 php: : DynDns: DynDns _checkStatus() starting. Dec 19 00:01:01 php: : DynDns: DynDns _update() starting. Dec 19 00:01:01 php: : DynDns: More than 28 days. Updating. Dec 19 00:01:01 php: : DynDns: cacheIP != wan_ip. Updating. Dec 19 00:01:01 php: : DynDns: Cached IP: Dec 19 00:01:01 php: : DynDns: Current WAN IP: 68.7.149.### Dec 19 00:01:01 php: : DynDns: _detectChange() starting. Dec 19 00:01:01 php: : DynDns: updatedns() starting Dec 19 00:01:01 php: : DynDns: Running updatedns() And I just got my dyndns account blocked for this. Dear Valued Customer: The hostname, ###.mine.nu, in account , has been blocked for abuse. This action has been taken due to the receipt of multiple updates originating from the same IP address. Unless this was fixed after 0.96.2? Damien Dupertuis wrote: No problem :-) Believe me!!! we are also wery happy you finally killed the nasty bug!!! Thank you very much!!! Regards Damien --- Scott Ullrich <[EMAIL PROTECTED]> a écrit : Thanks for the replies. I have to say that I am really glad this problem is solved. I've lost many hair to grey due to these bugs. Scott On 12/10/05, Ispánovits Imre <[EMAIL PROTECTED]> wrote: On Sat, 10 Dec 2005 18:22:55 +0100 (CET) Damien Dupertuis <[EMAIL PROTECTED]> wrote: Hello, It has been working for two days and a half now and I'm not banned , my adress is upgraded correctly so I assume the bug is killed... Thank you!!! Damien Hi, I can confirm as well. In v95.4 works fine. My ISP just now changed my ip address and this event triggered DynDns-update correctly. THX Imre -- This is Linux Land. In silent nights you can hear the windows machines rebooting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] DynDns scheduling issues
This is the old version. The newer version has more debugging information. Scott On 12/20/05, Kevin Wolf <[EMAIL PROTECTED]> wrote: > You all sure this is solved? I'm using 0.96.2 and I see a lot of this > in my log: > > Dec 19 01:01:02 php: : phpDynDNS: (Success) No Change In IP Address > Dec 19 01:01:02 php: : DynDns: Current Service: dyndns > Dec 19 01:01:02 php: : DynDns: DynDns _checkStatus() starting. > Dec 19 01:01:01 php: : DynDns: DynDns _update() starting. > Dec 19 01:01:01 php: : DynDns: More than 28 days. Updating. > Dec 19 01:01:01 php: : DynDns: cacheIP != wan_ip. Updating. > Dec 19 01:01:01 php: : DynDns: Cached IP: > Dec 19 01:01:01 php: : DynDns: Current WAN IP: 68.7.149.### > Dec 19 01:01:01 php: : DynDns: _detectChange() starting. > Dec 19 01:01:01 php: : DynDns: updatedns() starting > Dec 19 01:01:01 php: : DynDns: Running updatedns() > Dec 19 00:01:21 php: : phpDynDNS: (Success) No Change In IP Address > Dec 19 00:01:21 php: : DynDns: Current Service: dyndns > Dec 19 00:01:21 php: : DynDns: DynDns _checkStatus() starting. > Dec 19 00:01:01 php: : DynDns: DynDns _update() starting. > Dec 19 00:01:01 php: : DynDns: More than 28 days. Updating. > Dec 19 00:01:01 php: : DynDns: cacheIP != wan_ip. Updating. > Dec 19 00:01:01 php: : DynDns: Cached IP: > Dec 19 00:01:01 php: : DynDns: Current WAN IP: 68.7.149.### > Dec 19 00:01:01 php: : DynDns: _detectChange() starting. > Dec 19 00:01:01 php: : DynDns: updatedns() starting > Dec 19 00:01:01 php: : DynDns: Running updatedns() > > > And I just got my dyndns account blocked for this. > > Dear Valued Customer: > > The hostname, ###.mine.nu, in account , has been blocked for > abuse. This action has been taken due to the receipt of multiple updates > originating from the same IP address. > > > Unless this was fixed after 0.96.2? > > Damien Dupertuis wrote: > > >No problem :-) > > > >Believe me!!! we are also wery happy you finally > >killed the nasty bug!!! > > > >Thank you very much!!! > > > >Regards > > > >Damien > > > > > >--- Scott Ullrich <[EMAIL PROTECTED]> a écrit : > > > > > > > >>Thanks for the replies. > >> > >>I have to say that I am really glad this problem is > >>solved. I've lost > >>many hair to grey due to these bugs. > >> > >>Scott > >> > >>On 12/10/05, Ispánovits Imre > >><[EMAIL PROTECTED]> wrote: > >> > >> > >>>On Sat, 10 Dec 2005 18:22:55 +0100 (CET) > >>>Damien Dupertuis <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > Hello, > > It has been working for two days and a half now > > > >>and > >> > >> > I'm not banned , my adress is upgraded correctly > > > >>so I > >> > >> > assume the bug is killed... > > Thank you!!! > > Damien > > > > >>>Hi, > >>> > >>>I can confirm as well. In v95.4 works fine. My ISP > >>> > >>> > >>just now changed my ip > >> > >> > >>>address and this event triggered DynDns-update > >>> > >>> > >>correctly. > >> > >> > >>>THX > >>> > >>>Imre > >>> > >>> > >>>-- > >>>This is Linux Land. > >>>In silent nights you can hear the windows machines > >>> > >>> > >>rebooting > >> > >> > >>> > >>> > >>> > >> > >> > >- > > > > > >>To unsubscribe, e-mail: > >>[EMAIL PROTECTED] > >>For additional commands, e-mail: > >>[EMAIL PROTECTED] > >> > >> > >> > >> > > > > > > > > > > > > > > > >___ > >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] > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] DynDns scheduling issues
That first file only has the character ':' in it. # cat /cf/conf/dyndns.cache : I dunno if cat is the right command to use though. I'm a noob to *BSD =) The second file has a lot of stuff in it. # cat /var/etc/dyndns.debug 10-31-05 06:01:01 - (1183040) - [dyndns] - 68.7.144.105/113080406511-01-05 02:34:10 - (1915049) - [dyndns] - 68.7.144.105/113080406511-01-05 02:24:22 - (5922829) - [dyndns] - 68.7.144.105/113080406511-01-05 02:24:22 - (5922829) - [dyndns] - 11-01-05 02:24:25 - (5363598) - [dyndns] - /113088386211-01-05 02:24:27 - (2477868) - [dyndns] - 68.7.144.105/113088386511-01-05 10:45:32 - (2547618) - [dyndns] - 68.7.144.105/113088386511-02-05 02:01:01 - (3776986) - [dyndns] - 68.7.144.105/113088386511-02-05 02:24:25 - (1386654) - [dyndns] - 68.7.144.105/113088386511-02-05 02:24:26 - (9178116) - [dyndns] - 68.7.144.105/113088386511-03-05 02:01:01 - (3310732) - [dyndns] - 68.7.144.105/113088386511-03-05 02:24:31 - (1839092) - [dyndns] - 68.7.144.105/113088386511-03-05 02:24:31 - (2522099) - [dyndns] - 68.7.144.105/113088386511-04-05 02:01:01 - (7738642) - [dyndns] - 68.7.144.105/113088386511-04-05 02:24:31 - (2489136) - [dyndns] - 68.7.144.105/113088386511-04-05 02:24:31 - (9317122) - [dyndns] - 68.7.144.105/113088386511-05-05 02:01:02 - (5925666) - [dyndns] - 68.7.144.105/113088386511-05-05 02:24:31 - (4277080) - [dyndns] - 68.7.144.105/113088386511-05-05 02:24:32 - (8138097) - [dyndns] - 68.7.144.105/113088386511-06-05 02:01:01 - (2079140) - [dyndns] - 68.7.144.105/113088386511-06-05 02:24:31 - (6845703) - [dyndns] - 68.7.144.105/113088386511-06-05 02:24:32 - (5878052) - [dyndns] - 68.7.144.105/113088386511-07-05 02:01:01 - (7372718) - [dyndns] - 68.7.144.105/113088386511-07-05 02:24:32 - (5382649) - [dyndns] - 68.7.144.105/113088386511-07-05 02:24:31 - (3361652) - [dyndns] - 68.7.144.105/113088386511-08-05 02:01:01 - (1564964) - [dyndns] - 68.7.144.105/113088386511-08-05 02:24:31 - (6718998) - [dyndns] - 68.7.144.105/113088386511-08-05 02:24:31 - (1034768) - [dyndns] - 68.7.144.105/113088386511-09-05 02:01:01 - (3679236) - [dyndns] - 68.7.144.105/113088386511-09-05 02:24:31 - (1186567) - [dyndns] - 68.7.144.105/113088386511-09-05 02:24:31 - (7668874) - [dyndns] - 68.7.144.105/113088386511-09-05 04:20:27 - (1235418) - [dyndns] - 68.7.144.105/113088386511-09-05 04:20:27 - (1235418) - [dyndns] - 11-09-05 04:20:30 - (5533725) - [dyndns] - /113158202711-09-05 04:20:32 - (5775489) - [dyndns] - 68.7.144.105/113158203011-10-05 02:01:01 - (7014313) - [dyndns] - 68.7.144.105/113158203011-10-05 04:20:30 - (5721145) - [dyndns] - 68.7.144.105/113158203011-10-05 04:20:30 - (8630482) - [dyndns] - 68.7.144.105/113158203011-11-05 02:01:02 - (9104353) - [dyndns] - 68.7.144.105/113158203011-11-05 04:20:30 - (9291472) - [dyndns] - 68.7.144.105/113158203011-11-05 04:20:30 - (2590529) - [dyndns] - 68.7.144.105/113158203011-12-05 02:01:01 - (2581370) - [dyndns] - 68.7.144.105/113158203011-12-05 04:20:31 - (4314200) - [dyndns] - 68.7.144.105/113158203011-12-05 04:20:31 - (7425997) - [dyndns] - 68.7.144.105/113158203011-13-05 02:01:01 - (5311004) - [dyndns] - 68.7.144.105/113158203011-13-05 04:20:33 - (7060990) - [dyndns] - 68.7.144.105/113158203011-13-05 04:20:32 - (9809862) - [dyndns] - 68.7.144.105/113158203011-14-05 02:01:01 - (2144299) - [dyndns] - 68.7.144.105/113158203011-14-05 04:20:32 - (3194939) - [dyndns] - 68.7.144.105/113158203011-14-05 04:20:32 - (1224284) - [dyndns] - 68.7.144.105/113158203011-15-05 02:01:01 - (5144641) - [dyndns] - 68.7.144.105/113158203011-15-05 04:20:33 - (4951948) - [dyndns] - 68.7.144.105/113158203011-15-05 04:20:32 - (2814391) - [dyndns] - 68.7.144.105/113158203011-15-05 09:48:05 - (2289063) - [dyndns] - 68.7.144.105/113158203011-15-05 09:48:05 - (2289063) - [dyndns] - 11-15-05 09:48:08 - (5915158) - [dyndns] - /113212008511-15-05 09:48:10 - (1829785) - [dyndns] - 68.7.144.105/113212008811-15-05 10:06:22 - (5992229) - [dyndns] - 68.7.144.105/113212008811-15-05 10:06:22 - (5992229) - [dyndns] - 11-15-05 10:06:25 - (6225438) - [dyndns] - /113212118211-15-05 10:06:27 - (8535958) - [dyndns] - 68.7.144.105/113212118511-16-05 02:01:01 - (4669273) - [dyndns] - 68.7.144.105/113212118511-16-05 10:06:26 - (8870098) - [dyndns] - 68.7.144.105/113212118511-16-05 10:06:26 - (1852873) - [dyndns] - 68.7.144.105/113212118511-17-05 02:01:01 - (1425757) - [dyndns] - 68.7.144.105/113212118511-17-05 10:06:34 - (9750604) - [dyndns] - 68.7.144.105/113212118511-17-05 10:06:33 - (4837984) - [dyndns] - 68.7.144.105/113212118511-18-05 02:01:01 - (8472018) - [dyndns] - 68.7.144.105/113212118511-18-05 10:06:34 - (1502684) - [dyndns] - 68.7.144.105/113212118511-18-05 10:06:34 - (9543019) - [dyndns] - 68.7.144.105/113212118511-19-05 02:01:01 - (1192021) - [dyndns] - 68.7.144.105/113212118511-19-05 10:06:38 - (5834699) - [dyndns] - 68.7.144.105/113212118511-19-05 01:07:48 - (7035542) - [dyndns] - 68.7.144.105/1132434467\n11-19-05 01:07:49 -
Re: [pfSense Support] DynDns scheduling issues
What are the contents of /cf/conf/dyndns.cache and /var/etc/dyndns.debug? -Erik --Original Message-- > You all sure this is solved? I'm using 0.96.2 and I see a lot of this > in my log: > > Dec 19 01:01:02 php: : phpDynDNS: (Success) No Change In IP Address > Dec 19 01:01:02 php: : DynDns: Current Service: dyndns > Dec 19 01:01:02 php: : DynDns: DynDns _checkStatus() starting. > Dec 19 01:01:01 php: : DynDns: DynDns _update() starting. > Dec 19 01:01:01 php: : DynDns: More than 28 days. Updating. > Dec 19 01:01:01 php: : DynDns: cacheIP != wan_ip. Updating. > Dec 19 01:01:01 php: : DynDns: Cached IP: > Dec 19 01:01:01 php: : DynDns: Current WAN IP: 68.7.149.### > Dec 19 01:01:01 php: : DynDns: _detectChange() starting. > Dec 19 01:01:01 php: : DynDns: updatedns() starting > Dec 19 01:01:01 php: : DynDns: Running updatedns() > Dec 19 00:01:21 php: : phpDynDNS: (Success) No Change In IP Address > Dec 19 00:01:21 php: : DynDns: Current Service: dyndns > Dec 19 00:01:21 php: : DynDns: DynDns _checkStatus() starting. > Dec 19 00:01:01 php: : DynDns: DynDns _update() starting. > Dec 19 00:01:01 php: : DynDns: More than 28 days. Updating. > Dec 19 00:01:01 php: : DynDns: cacheIP != wan_ip. Updating. > Dec 19 00:01:01 php: : DynDns: Cached IP: > Dec 19 00:01:01 php: : DynDns: Current WAN IP: 68.7.149.### > Dec 19 00:01:01 php: : DynDns: _detectChange() starting. > Dec 19 00:01:01 php: : DynDns: updatedns() starting > Dec 19 00:01:01 php: : DynDns: Running updatedns() > > > And I just got my dyndns account blocked for this. > > Dear Valued Customer: > > The hostname, ###.mine.nu, in account , has been blocked for > abuse. This action has been taken due to the receipt of multiple updates > originating from the same IP address. > > > Unless this was fixed after 0.96.2? > > Damien Dupertuis wrote: > > >No problem :-) > > > >Believe me!!! we are also wery happy you finally > >killed the nasty bug!!! > > > >Thank you very much!!! > > > >Regards > > > >Damien > > > > > >--- Scott Ullrich <[EMAIL PROTECTED]> a écrit : > > > > > > > >>Thanks for the replies. > >> > >>I have to say that I am really glad this problem is > >>solved. I've lost > >>many hair to grey due to these bugs. > >> > >>Scott > >> > >>On 12/10/05, Ispánovits Imre > >><[EMAIL PROTECTED]> wrote: > >> > >> > >>>On Sat, 10 Dec 2005 18:22:55 +0100 (CET) > >>>Damien Dupertuis <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > Hello, > > It has been working for two days and a half now > > > >>and > >> > >> > I'm not banned , my adress is upgraded correctly > > > >>so I > >> > >> > assume the bug is killed... > > Thank you!!! > > Damien > > > > >>>Hi, > >>> > >>>I can confirm as well. In v95.4 works fine. My ISP > >>> > >>> > >>just now changed my ip > >> > >> > >>>address and this event triggered DynDns-update > >>> > >>> > >>correctly. > >> > >> > >>>THX > >>> > >>>Imre > >>> > >>> > >>>-- > >>>This is Linux Land. > >>>In silent nights you can hear the windows machines > >>> > >>> > >>rebooting > >> > >> > >>> > >>> > >>> > >> > >> > >- > > > > > >>To unsubscribe, e-mail: > >>[EMAIL PROTECTED] > >>For additional commands, e-mail: > >>[EMAIL PROTECTED] > >> > >> > >> > >> > > > > > > > > > > > > > > > >___ > >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] > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] DynDns scheduling issues
You all sure this is solved? I'm using 0.96.2 and I see a lot of this in my log: Dec 19 01:01:02 php: : phpDynDNS: (Success) No Change In IP Address Dec 19 01:01:02 php: : DynDns: Current Service: dyndns Dec 19 01:01:02 php: : DynDns: DynDns _checkStatus() starting. Dec 19 01:01:01 php: : DynDns: DynDns _update() starting. Dec 19 01:01:01 php: : DynDns: More than 28 days. Updating. Dec 19 01:01:01 php: : DynDns: cacheIP != wan_ip. Updating. Dec 19 01:01:01 php: : DynDns: Cached IP: Dec 19 01:01:01 php: : DynDns: Current WAN IP: 68.7.149.### Dec 19 01:01:01 php: : DynDns: _detectChange() starting. Dec 19 01:01:01 php: : DynDns: updatedns() starting Dec 19 01:01:01 php: : DynDns: Running updatedns() Dec 19 00:01:21 php: : phpDynDNS: (Success) No Change In IP Address Dec 19 00:01:21 php: : DynDns: Current Service: dyndns Dec 19 00:01:21 php: : DynDns: DynDns _checkStatus() starting. Dec 19 00:01:01 php: : DynDns: DynDns _update() starting. Dec 19 00:01:01 php: : DynDns: More than 28 days. Updating. Dec 19 00:01:01 php: : DynDns: cacheIP != wan_ip. Updating. Dec 19 00:01:01 php: : DynDns: Cached IP: Dec 19 00:01:01 php: : DynDns: Current WAN IP: 68.7.149.### Dec 19 00:01:01 php: : DynDns: _detectChange() starting. Dec 19 00:01:01 php: : DynDns: updatedns() starting Dec 19 00:01:01 php: : DynDns: Running updatedns() And I just got my dyndns account blocked for this. Dear Valued Customer: The hostname, ###.mine.nu, in account , has been blocked for abuse. This action has been taken due to the receipt of multiple updates originating from the same IP address. Unless this was fixed after 0.96.2? Damien Dupertuis wrote: No problem :-) Believe me!!! we are also wery happy you finally killed the nasty bug!!! Thank you very much!!! Regards Damien --- Scott Ullrich <[EMAIL PROTECTED]> a écrit : Thanks for the replies. I have to say that I am really glad this problem is solved. I've lost many hair to grey due to these bugs. Scott On 12/10/05, Ispánovits Imre <[EMAIL PROTECTED]> wrote: On Sat, 10 Dec 2005 18:22:55 +0100 (CET) Damien Dupertuis <[EMAIL PROTECTED]> wrote: Hello, It has been working for two days and a half now and I'm not banned , my adress is upgraded correctly so I assume the bug is killed... Thank you!!! Damien Hi, I can confirm as well. In v95.4 works fine. My ISP just now changed my ip address and this event triggered DynDns-update correctly. THX Imre -- This is Linux Land. In silent nights you can hear the windows machines rebooting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] DynDns scheduling issues
No problem :-) Believe me!!! we are also wery happy you finally killed the nasty bug!!! Thank you very much!!! Regards Damien --- Scott Ullrich <[EMAIL PROTECTED]> a écrit : > Thanks for the replies. > > I have to say that I am really glad this problem is > solved. I've lost > many hair to grey due to these bugs. > > Scott > > On 12/10/05, Ispánovits Imre > <[EMAIL PROTECTED]> wrote: > > On Sat, 10 Dec 2005 18:22:55 +0100 (CET) > > Damien Dupertuis <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > > > It has been working for two days and a half now > and > > > I'm not banned , my adress is upgraded correctly > so I > > > assume the bug is killed... > > > > > > Thank you!!! > > > > > > Damien > > > > > Hi, > > > > I can confirm as well. In v95.4 works fine. My ISP > just now changed my ip > > address and this event triggered DynDns-update > correctly. > > > > THX > > > > Imre > > > > > > -- > > This is Linux Land. > > In silent nights you can hear the windows machines > rebooting > > > > > > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ___ 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]
Re: [pfSense Support] DynDns scheduling issues
Thanks for the replies. I have to say that I am really glad this problem is solved. I've lost many hair to grey due to these bugs. Scott On 12/10/05, Ispánovits Imre <[EMAIL PROTECTED]> wrote: > On Sat, 10 Dec 2005 18:22:55 +0100 (CET) > Damien Dupertuis <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > It has been working for two days and a half now and > > I'm not banned , my adress is upgraded correctly so I > > assume the bug is killed... > > > > Thank you!!! > > > > Damien > > > Hi, > > I can confirm as well. In v95.4 works fine. My ISP just now changed my ip > address and this event triggered DynDns-update correctly. > > THX > > Imre > > > -- > This is Linux Land. > In silent nights you can hear the windows machines rebooting > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] DynDns scheduling issues
On Sat, 10 Dec 2005 18:22:55 +0100 (CET) Damien Dupertuis <[EMAIL PROTECTED]> wrote: > Hello, > > It has been working for two days and a half now and > I'm not banned , my adress is upgraded correctly so I > assume the bug is killed... > > Thank you!!! > > Damien > Hi, I can confirm as well. In v95.4 works fine. My ISP just now changed my ip address and this event triggered DynDns-update correctly. THX Imre -- This is Linux Land. In silent nights you can hear the windows machines rebooting signature.asc Description: PGP signature
RE: [pfSense Support] DynDns scheduling issues
Hello, It has been working for two days and a half now and I'm not banned , my adress is upgraded correctly so I assume the bug is killed... Thank you!!! Damien --- alan walters <[EMAIL PROTECTED]> a écrit : > Yep should be fine. Check > > http://cvstrac.pfsense.com/timeline > > And see if the file is updated in releng branch if > it is the update for you is fine. > > -Original Message- > From: Damien Dupertuis [mailto:[EMAIL PROTECTED] > Sent: 08 December 2005 15:52 > To: support@pfsense.com > Subject: RE: [pfSense Support] DynDns scheduling > issues > > Okay, > > to be honest I don't know what to answer to you... > I'm not good enough!!! that's it! > let me explain my problem again: > > I experienced dyndns issues because the client was > trying to upgrade too often, a guy told me to do: " > Update_file.sh /etc/crontab and reboot" (on version > 95a) I done it and it works... > Now I installed 95.4 and I just want to know if It's > gonna work straight "from the upgrade" or not... > > anyway I'm currently testing it...so I'll keep you > informed... > okay? > > Thanks and regards > > Damien > > > > > > > > ___ > 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] > > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ___ 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]
RE: [pfSense Support] DynDns scheduling issues
Yep should be fine. Check http://cvstrac.pfsense.com/timeline And see if the file is updated in releng branch if it is the update for you is fine. -Original Message- From: Damien Dupertuis [mailto:[EMAIL PROTECTED] Sent: 08 December 2005 15:52 To: support@pfsense.com Subject: RE: [pfSense Support] DynDns scheduling issues Okay, to be honest I don't know what to answer to you... I'm not good enough!!! that's it! let me explain my problem again: I experienced dyndns issues because the client was trying to upgrade too often, a guy told me to do: " Update_file.sh /etc/crontab and reboot" (on version 95a) I done it and it works... Now I installed 95.4 and I just want to know if It's gonna work straight "from the upgrade" or not... anyway I'm currently testing it...so I'll keep you informed... okay? Thanks and regards Damien ___ 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] DynDns scheduling issues
Okay, to be honest I don't know what to answer to you... I'm not good enough!!! that's it! let me explain my problem again: I experienced dyndns issues because the client was trying to upgrade too often, a guy told me to do: " Update_file.sh /etc/crontab and reboot" (on version 95a) I done it and it works... Now I installed 95.4 and I just want to know if It's gonna work straight "from the upgrade" or not... anyway I'm currently testing it...so I'll keep you informed... okay? Thanks and regards Damien ___ 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]
RE: [pfSense Support] DynDns scheduling issues
I have a script in my conf directory that I run's after update now to add back in my edits. But this could break stuff as well. -Original Message- From: Bill Marquette [mailto:[EMAIL PROTECTED] Sent: 08 December 2005 15:03 To: support@pfsense.com Subject: Re: [pfSense Support] DynDns scheduling issues FYI, update_file.sh pulls from HEAD which has some changes that can possibly bite you. As such, until it's modified to pull from RELENG_1, it's been pulled from the RELENG_1 tree. At this time there's no way to delete files during the update process, so be aware that update_file.sh may actually break your box - be prepared to fix it (especially if you do an update_file.sh -all). --Bill On 12/8/05, Damien Dupertuis <[EMAIL PROTECTED]> wrote: > Okay, > > I'm trying without the Update_file.sh /etc/crontab then... > > I'll keep you informed... > > Thanks > > > --- alan walters <[EMAIL PROTECTED]> a écrit : > > > I can confirm if you are using full updates crontab is being > > updated. Well it is being replaced on my system. I have some checks > > that I have to keep reinstalling in there due to changes > > > > -Original Message- > > From: Frimmel, Ivan (ISS South Africa) [mailto:[EMAIL PROTECTED] > > Sent: 08 December 2005 12:31 > > To: support@pfsense.com > > Subject: RE: [pfSense Support] DynDns scheduling issues > > > > As far as I know Crontab is one of the files that is not touched > > during upgrades.. That's why you have to do it manually with > > update_file.sh. > > > > So no you don't have to do it after the upgrade. > > > > Ivan. > > > > > > -----Original Message- > > From: Damien Dupertuis [mailto:[EMAIL PROTECTED] > > Sent: Thursday, December 08, 2005 11:16 AM > > To: support@pfsense.com > > Subject: RE: [pfSense Support] DynDns scheduling issues > > > > Hello again :-) > > > > I upgraded to 95.4 > > > > Do I have to do the "Update_file.sh /etc/crontab and reboot" > > or is it included with the upgrade??? > > > > regards > > > > Damien > > > > > > > > --- Damien Dupertuis <[EMAIL PROTECTED]> a écrit : > > > > > Hello, > > > > > > Okay it works for me > > > > > > Thank you... > > > > > > > > > > > > > > > > > > --- "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: support@pfsense.com > > > > 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 > > > > > &g
Re: [pfSense Support] DynDns scheduling issues
FYI, update_file.sh pulls from HEAD which has some changes that can possibly bite you. As such, until it's modified to pull from RELENG_1, it's been pulled from the RELENG_1 tree. At this time there's no way to delete files during the update process, so be aware that update_file.sh may actually break your box - be prepared to fix it (especially if you do an update_file.sh -all). --Bill On 12/8/05, Damien Dupertuis <[EMAIL PROTECTED]> wrote: > Okay, > > I'm trying without the Update_file.sh /etc/crontab > then... > > I'll keep you informed... > > Thanks > > > --- alan walters <[EMAIL PROTECTED]> a écrit : > > > I can confirm if you are using full updates crontab > > is being updated. Well it is being replaced on my > > system. I have some checks that I have to keep > > reinstalling in there due to changes > > > > -Original Message- > > From: Frimmel, Ivan (ISS South Africa) > > [mailto:[EMAIL PROTECTED] > > Sent: 08 December 2005 12:31 > > To: support@pfsense.com > > Subject: RE: [pfSense Support] DynDns scheduling > > issues > > > > As far as I know Crontab is one of the files that is > > not touched during upgrades.. That's why you have to > > do it manually with update_file.sh. > > > > So no you don't have to do it after the upgrade. > > > > Ivan. > > > > > > -Original Message- > > From: Damien Dupertuis [mailto:[EMAIL PROTECTED] > > Sent: Thursday, December 08, 2005 11:16 AM > > To: support@pfsense.com > > Subject: RE: [pfSense Support] DynDns scheduling > > issues > > > > Hello again :-) > > > > I upgraded to 95.4 > > > > Do I have to do the "Update_file.sh /etc/crontab and > > reboot" > > or is it included with the upgrade??? > > > > regards > > > > Damien > > > > > > > > --- Damien Dupertuis <[EMAIL PROTECTED]> a écrit : > > > > > Hello, > > > > > > Okay it works for me > > > > > > Thank you... > > > > > > > > > > > > > > > > > > --- "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: support@pfsense.com > > > > 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
RE: [pfSense Support] DynDns scheduling issues
Okay, I'm trying without the Update_file.sh /etc/crontab then... I'll keep you informed... Thanks --- alan walters <[EMAIL PROTECTED]> a écrit : > I can confirm if you are using full updates crontab > is being updated. Well it is being replaced on my > system. I have some checks that I have to keep > reinstalling in there due to changes > > -Original Message- > From: Frimmel, Ivan (ISS South Africa) > [mailto:[EMAIL PROTECTED] > Sent: 08 December 2005 12:31 > To: support@pfsense.com > Subject: RE: [pfSense Support] DynDns scheduling > issues > > As far as I know Crontab is one of the files that is > not touched during upgrades.. That's why you have to > do it manually with update_file.sh. > > So no you don't have to do it after the upgrade. > > Ivan. > > > -Original Message- > From: Damien Dupertuis [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 08, 2005 11:16 AM > To: support@pfsense.com > Subject: RE: [pfSense Support] DynDns scheduling > issues > > Hello again :-) > > I upgraded to 95.4 > > Do I have to do the "Update_file.sh /etc/crontab and > reboot" > or is it included with the upgrade??? > > regards > > Damien > > > > --- Damien Dupertuis <[EMAIL PROTECTED]> a écrit : > > > Hello, > > > > Okay it works for me > > > > Thank you... > > > > > > > > > > > > --- "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: support@pfsense.com > > > 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
RE: [pfSense Support] DynDns scheduling issues
I can confirm if you are using full updates crontab is being updated. Well it is being replaced on my system. I have some checks that I have to keep reinstalling in there due to changes -Original Message- From: Frimmel, Ivan (ISS South Africa) [mailto:[EMAIL PROTECTED] Sent: 08 December 2005 12:31 To: support@pfsense.com Subject: RE: [pfSense Support] DynDns scheduling issues As far as I know Crontab is one of the files that is not touched during upgrades.. That's why you have to do it manually with update_file.sh. So no you don't have to do it after the upgrade. Ivan. -Original Message- From: Damien Dupertuis [mailto:[EMAIL PROTECTED] Sent: Thursday, December 08, 2005 11:16 AM To: support@pfsense.com Subject: RE: [pfSense Support] DynDns scheduling issues Hello again :-) I upgraded to 95.4 Do I have to do the "Update_file.sh /etc/crontab and reboot" or is it included with the upgrade??? regards Damien --- Damien Dupertuis <[EMAIL PROTECTED]> a écrit : > Hello, > > Okay it works for me > > Thank you... > > > > > > --- "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: support@pfsense.com > > 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 >
RE: [pfSense Support] DynDns scheduling issues
As far as I know Crontab is one of the files that is not touched during upgrades.. That's why you have to do it manually with update_file.sh. So no you don't have to do it after the upgrade. Ivan. -Original Message- From: Damien Dupertuis [mailto:[EMAIL PROTECTED] Sent: Thursday, December 08, 2005 11:16 AM To: support@pfsense.com Subject: RE: [pfSense Support] DynDns scheduling issues Hello again :-) I upgraded to 95.4 Do I have to do the "Update_file.sh /etc/crontab and reboot" or is it included with the upgrade??? regards Damien --- Damien Dupertuis <[EMAIL PROTECTED]> a écrit : > Hello, > > Okay it works for me > > Thank you... > > > > > > --- "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: support@pfsense.com > > 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 > > &g
RE: [pfSense Support] DynDns scheduling issues
Hello again :-) I upgraded to 95.4 Do I have to do the "Update_file.sh /etc/crontab and reboot" or is it included with the upgrade??? regards Damien --- Damien Dupertuis <[EMAIL PROTECTED]> a écrit : > Hello, > > Okay it works for me > > Thank you... > > > > > > --- "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: support@pfsense.com > > 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 ''/'' specifies skips > of > > > the > > > > number's value through the > > > > > range. For example, ''0-23/2'' > > can > > > > be used in the hours field to > > > > >
RE: [pfSense Support] DynDns scheduling issues
Hello, Okay it works for me Thank you... --- "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: support@pfsense.com > 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 ''/'' 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 > > >
RE: [pfSense Support] DynDns scheduling issues
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: support@pfsense.com > 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 ''/'' 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 > > >
RE: [pfSense Support] DynDns scheduling issues
Update_file.sh /etc/crontab and reboot -Original Message- From: Damien Dupertuis [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 7:03 AM To: support@pfsense.com 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 ''/'' 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
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 ''/'' 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: > > _detectChange() starting. > > > Nov 30 00:49:01 booji php: : DynDns: Current WAN > > IP: xx.xx.xx.xx > > > Nov 30 00:49:01 booji php: : DynDns: Cached IP: > > > Nov 30 00:49:01 booji php: : DynDns: cacheIP != > > wan_ip. Updating. > > > Nov 30 00:49:01 booji php: : DynDns: More than > 28 > > days. Updating. > > > Nov
Re: [pfSense Support] DynDns scheduling issues
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 ''/'' 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: _detectChange() starting. > Nov 30 00:49:01 booji php: : DynDns: Current WAN IP: xx.xx.xx.xx > Nov 30 00:49:01 booji php: : DynDns: Cached IP: > Nov 30 00:49:01 booji php: : DynDns: cacheIP != wan_ip. Updating. > Nov 30 00:49:01 booji php: : DynDns: More than 28 days. Updating. > Nov 30 00:49:01 booji php: : DynDns: DynDns _update() starting. > Nov 30 00:49:02 booji php: : DynDns: DynDns _checkStatus() starting. > Nov 30 00:49:02 booji php: : DynDns: Current Service: dyndns > Nov 30 00:49:02 booji php: : phpDynDNS: PAYLOAD: abuse > Nov 30 00:49:02 booji php: : phpDynDNS: (Unknown Response) > Nov 30 00:50:01 booji php: : DynDns: Running updatedns() > Nov 30 00:50:01 booji php: : DynDns: updatedns() starting > Nov 30 00:50:01 booji php: : DynDns: _detectChange() starting. > Nov 30 00:50:01 booji php: : DynDns: Current WAN IP: xx.xx.xx.xx > Nov 30 00:50:01 booji php: : DynDns: Cached IP: > Nov 30 00:50:01 booji php: : DynDns: cacheIP != wan_ip. Updating. > Nov 30 00:50:01 booji php: : DynDns: More than 28 days. Updating. > Nov 30 00:50:01 booji php: : DynDns: DynDns _update() starting. > Nov 30 00:50:02 booji php: : DynDns: DynDns _checkStatus() starting. > Nov 30 00:50:02 booji php: : DynDns: Current Service: dyndns > Nov 30 00:50:02 booji php: : phpDynDNS: PAYLOAD: abuse > Nov 30 00:50:02 booji php: : phpDynDNS: (Unknow
