On 7/6/06, Steve Harman <[EMAIL PROTECTED]> wrote:
Hi Holger. It's a shame if this isn't how pfSense handles static
mapping of DHCP-assigned IPs. IPCop (and DHCPd AFAIK) allows IPs within
the DHCP range to be statically assigned to specific H/W addresses.
Moving an IP out of the DHCP range to provide "static" service would of
course solve the problem, but then we'd lose the benefits of having it
dynamically allocated in the first place! (gateway & DNS details etc)
Steve
You aren't moving it out of the DHCP range, you're moving it out of
the DYNAMIC range. FWIW, I don't think ISC DHCPD (which is what we
use) actually appreciates having static leases in the dynamic range.
given this subnet statement:
subnet 192.168.1.0 netmask 255.255.255.0 {
pool {
range 192.168.1.128 192.168.1.191;
}
option routers 192.168.1.1;
option domain-name-servers 192.168.1.1;
}
and I have three statics at .1.10, .1.11, and .1.15. The file parses
fine and loads w/out errors. If I add a static at .1.129, dhcpd gives
me grief about .1.11 and .1.15 (why not .1.10 I dunno)
dhcpd: lease 192.168.1.15: no subnet.
dhcpd: lease 192.168.1.11: no subnet.
Give us a config that does what you want and ISC DHCPD v3 doesn't
bitch about and we can consider this. Until then, my preliminary
tests make me believe that the daemon won't do it.
--Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
