As the topic says, I was blocked because of abuse:
"The abuse system automatically blocks any hostname that repeatedly
tries to update a hostname from the same IP. This is done to conserve
bandwidth and prevent computers from updating every 5 minutes,
regardless of whether or not their IP address
There is a file with a .cache extension on /etc. This should contain the
current IP address, and stop ez-ipupd from posting the current IP over
and over again.
Somewhere in the docs lies the answer.
Livio
cpu memhd wrote:
As the topic says, I was blocked because of abuse:
"The abuse system autom
expert in writing scripts but this works and
works well on quite a few bering installed firewalls.
I'm always open for input...
Bruce
> Date: Sat, 4 Dec 2004 21:59:02 -0800 (PST)
> From: cpu memhd <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [leaf-user] EZ-IPUP
Am Sonntag, 5. Dezember 2004 06:59 schrieb cpu memhd:
> As the topic says, I was blocked because of abuse:
>
> "The abuse system automatically blocks any hostname that repeatedly
> tries to update a hostname from the same IP. This is done to
> conserve bandwidth and prevent computers from updating
Hi!
> -Original Message-
> From: K.-P. Kirchdörfer [mailto:[EMAIL PROTECTED]
> > Does EZ-IPUPD attempt to update DynDNS at regular intervals or
> > every reboot? What should I do to prevent it from causing this
> > problem? My account will be "automatically deleted" if this
> > continues.
Thanks everyone for the help, I appreciate it very much.
I think the reason it was updating too frequently is logically because
ez-ipupd is saving to the RAM disk, which gets recreated upon every
reboot. This of course means that EZ-IPUPD will update DynDNS every
time I reboot.
So, I created a se
Am Montag, 6. Dezember 2004 10:58 schrieb cpu memhd:
> Thanks everyone for the help, I appreciate it very much.
>
> I think the reason it was updating too frequently is logically
> because ez-ipupd is saving to the RAM disk, which gets recreated
> upon every reboot. This of course means that EZ-IPU
That's easy to answer: so many packages/so little time. The box is not
yet in production.
K.-P. Kirchdörfer wrote:
>Am Montag, 6. Dezember 2004 10:58 schrieb cpu memhd:
>
>>Thanks everyone for the help, I appreciate it very much.
>>
>>I think the reason it was updating too frequently is logically
