Value of leased-address while processing DISCOVER

Jerimiah Cole jcole at tbtc.net
Mon Dec 10 19:54:13 UTC 2007



This config:

if binary-to-ascii(10,8,".",substring(option agent.remote-id,4,4)) = "72.0.47.192" {
  log ( info, concat( "PVC for ", binary-to-ascii(10,8,".",leased-address), " (", binary-to-ascii(16,8,":",hardware), ") (gw.tul) is:  ", binary-to-ascii(10,8,"",substring(option agent.remote-id,9,1)), "/",   binary-to-ascii(10,16,"",suffix(option agent.remote-id,2)) ) );
}

Dec  9 07:54:39 2007 dhcpd: PVC for 192.168.167.88 (1:0:30:65:b7:ff:ff) (gw.site) is:  1/77
Dec  9 07:54:39 2007 dhcpd: DHCPDISCOVER from 00:30:65:b7:ff:ff via 192.168.167.65
Dec  9 07:54:40 2007 dhcpd: DHCPOFFER on 66.18.167.88 to 00:30:65:b7:ff:ff via 192.168.167.65
Dec  9 07:54:44 2007 dhcpd: PVC for 192.168.167.87 (1:0:30:65:b7:ff:ff) (gw.tul) is:  1/77
Dec  9 07:54:44 2007 dhcpd: DHCPDISCOVER from 00:30:65:b7:61:26 via 192.168.167.65: no available billing

What is the value of leased-address indicating?  Has the server already "allocated" the first address and is denying the second request based on the class lease-limit?





More information about the dhcp-users mailing list