On Sunday 23 March 2003 17:30, Michael Jinks wrote: > I'm not sure what you're asking. Do you mean that you want dhcpd to > notice your NIC's address, and use that address as the basis for > determining which addresses to hand out to clients? I think that would > be counter to the spirit of dhcpd's design. You might be able to > replace the init script with something that writes or selects a > dhcpd.conf based on your inside NIC's current address each time it's > about to start the daemon, but I don't think that dhcpd itself is going > to provide a way to do this on its own.
Normaly the adress of a dhcpd should be static. So hardcoding the local adress and the adress range it gives leases from is no problem at all. > > On the other hand, if your inside NIC doesn't change addresses very > often, it's simple to list a range of addresses in the config file. If > you have multiple NIC's which you want to serve dhcp requests, you could > run multiple dhcpd's each bound to a different interface (see the > synopsis at the top of the dhcpd manpage). And if you must run dhcpd on > your border system, you'll want to be sure to bind it to the right NIC > anyhow so that you aren't serving 10.* addresses out to the outside > world. ;) It is very easy to configure dhcpd to bind to only eth1 and eth2 (or whichever network devices). It is also possible (necesarry) to have different ranges for each device. There is no need at all to start multiple dhcpd's. A feature I like is to assign fixed adresses based on mac-address. That way certain computers allways get the same adress. Paul -- Paul de Vrieze Researcher Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net
pgp00000.pgp
Description: signature
