Is there any protection mechanism for a spamming dhcp client?

[Jürgen Dietl]

Hello Alfred,

thanx a lot. But I also have another problem. Even if the client get only 1
lease but this lease he got 590.000 times - he write a lot of lines in the
log. So the log got very big.

What I look for is that the server sees "ah this is the same mac and the
client has already an IPAdress that I gaive him 0.1 sec before, so I ignore
him". So a kind of intelligence :-)

have a nice day,
cheers,


2011/2/3 Alfred Nagl <nagl at wu.ac.at>

> On Thursday 03 February 2011, Jürgen Dietl wrote:
> > Hello,
> >
> > I am new to this mailing list. So I see a big "Hello World" and I hope to
> > meet interesting people here.
> >
> > I have the following question:
> >
> > I am running ISC DHCP and BIND latest Version and I have a printer that
> > even if it owns an IP-Address it makes thousands of DHCP-Requests per
> > seconds. Till somebody powered off the printer the dhcp server got
> 590.000
> > dhcp requests. Of course the pool was empty. I know I can prevent such
> > things with enabling dhcp snooping on network equipment but is there any
> > mechanism that I can do some protection on the server. For example if the
> > server would notice that it is always the same client that asked for an
> > address it should say NO and ignore the client, or put him in a database
> > to refuse any action etc. Is there a way to implement this? Is there any
> > mechanisem?
>
>
> Maybe  these 2 options
>
> deny duplicates;                #       only one lease per MAC
> one-lease-per-client on;        #       force only one lease per client
>
> would help giving out only one lease.
>
>
>                regards
>                                --alfred
>
>
> --
> Alfred Nagl
> IT-Services / Network Administration
>
> WU
> Wirtschaftsuniversität Wien
> Vienna University of Economics and Business
> Augasse 2-6, A-1090 Vienna, Austria
>
> Phone: +43 1 313 36 / 4811
> Fax:   +43 1 313 36 / 904811
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20110203/e04c84c9/attachment.html>