[c-nsp] DHCP Binding Expiration

[Manaf Al Oqlah]

hi all,

thank you for your help.
It seems that all those hosts with infinite expiration time are devices that 
do not have "client identifier" such as D-Link, Cisco Linksys routers or 
Unix systems. does it make sense?

Manaf
--------------------------------------------------
From: <A.L.M.Buxey at lboro.ac.uk>
Sent: Monday, February 09, 2009 10:01 PM
To: "Justin Shore" <justin at justinshore.com>
Cc: <cisco-nsp at puck.nether.net>; "Church, Charles" <cchurc05 at harris.com>
Subject: Re: [c-nsp] DHCP Binding Expiration

> Hi,
>
>> expires.  This would prevent many of the less technical users from
>> trying to run a publicly-accessible server.  Set the lease time to 2
>
> default TCP inbound deny works wonders for this. Or, even crueller, NAT
>
>> I've seen systems do something similar before (or at least I thought
>> they were).  When I first got Cox CATV I could only keep my IP for about
>> a day before it changed.  One way to mitigate the flow of traffic
>> problem would be to grant short lease extensions automatically until the
>> wee hours of the morning and then force the change.  Something to think
>> about.
>
> you can flush/destroy the DHCP binding table - it'll have the same effect
> (good fun - all those PCs set to print to the IP address that the
> pritner got when it was installed then have to be reconfigured etc)
>
>> systems with CNR.  Oh, and finishing my IPv6 deployment.
>
> DHCPv6 or router solicited?
>
> alan
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>