<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 11/23/10 9:01 AM, Jeremy Falling wrote:
<blockquote
cite="mid:alpine.BSF.2.00.1011230940430.48806@boston.g4.net"
type="cite">We currently assign both static and dynamic leases
based on the remote-id sent to us by our DSLAMS.
<br>
Our problem is when a customer changes the equipment that is
getting the lease, DHCP will not reissue the lease due to the MAC
address changing.
<br>
This causes us to desire DHCP to issue and track leases by the
remote-id instead of the MAC address.
<br>
</blockquote>
My first reaction is that DHCP uses the MAC address to 'track'
leases. But you can play around with classes to make it work.<br>
<br>
<a>Miquel van Smoorenburg has a writeup on his site that refers to
several patches. Ref: <</a><a class="moz-txt-link-freetext" href="http://www.miquels.cistron.nl/isc-dhcpd/">http://www.miquels.cistron.nl/isc-dhcpd/</a>><br>
<br>
exerpts:<br>
<pre> stash-agent-options true;
class "static-1" {
spawn with option agent.circuit-id;
}
shared-network "networkname" {
subnet 192.168.0.0 netmask 255.255.255.0 {
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
# A customer.
pool {
allow members of "static-1" "dslam42.port22";
range 192.168.0.2;
}
# And yet another one.
pool {
allow members of "static-1" "dslam42.port29";
range 192.168.0.5;
}
}
}
</pre>
<br>
<pre> class "static-1" {
spawn with concat(option agent.remote-id,0,6), "_", agent.circuit-id);
}
[....]
pool {
allow members of "static-1" "dslam2_port29";
}
}
</pre>
<br>
Regards,<br>
Tim Peiffer<br>
<pre class="moz-signature" cols="72">--
Tim Peiffer
Network Support Engineer
Office of Information Technology
University of Minnesota/NorthernLights GigaPOP
+1 612 626-7884 (desk)
</pre>
</body>
</html>