Assigning leases based on option 82

[Tim Peiffer]

On 11/23/10 9:01 AM, Jeremy Falling wrote:
> We currently assign both static and dynamic leases based on the 
> remote-id sent to us by our DSLAMS.
> 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.
> This causes us to desire DHCP to issue and track leases by the 
> remote-id instead of the MAC address.
My first reaction is that DHCP uses the MAC address to 'track' leases.  
But you can play around with classes to make it work.

Miquel van Smoorenburg has a writeup on his site that refers to several 
patches.  Ref: <http://www.miquels.cistron.nl/isc-dhcpd/>

exerpts:

	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;
			}
		}
	}


	class "static-1" {
		spawn with concat(option agent.remote-id,0,6), "_", agent.circuit-id);
	}
	[....]
		pool {
			allow members of "static-1" "dslam2_port29";
		}
	}


Regards,
Tim Peiffer

-- 
Tim Peiffer
Network Support Engineer
Office of Information Technology
University of Minnesota/NorthernLights GigaPOP

+1 612 626-7884 (desk)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20101123/e8d15583/attachment.html>