On Mon, 2006-02-20 at 16:21 -0600, Steven J Lamb wrote: > I am trying to configure dhcpd3 to allocate two pools of addresses based on > the requesting router's ip. I have a Cisco router with two interfaces that I > would like to give different ip blocks to each group depending on what > interface they are connected on. I have things set up so that my log files > say connecting via 192.168.0.254 or connecting via 192.168.1.254 depending > on the router the dhcp request comes from. however it hands all of the ip's > out of the same pool. I could do this with two different servers but I don't > want to set up a new instance of dhcp. any suggestions. It'd help if you posted your dhcpd.conf file. But I've done something similar, you need to play with subnet options in it. You could see what I've done in mine (below) as an example (NB: it's full of experiments, you don't need most of what's there). cat /etc/dhcpd.conf # common parts: authoritative; allow client-updates; include "/etc/rndc.key"; # (same key used by BIND, needed to update DNS records) ddns-domainname "example.com."; ddns-rev-domainname "in-addr.arpa."; ddns-update-style interim; ddns-updates on; default-lease-time 21600; # 2 hours max-lease-time 43200; # 24 hours min-lease-time 30; # 30 seconds (might allow renewing experiments) option domain-name "example.com."; option nntp-server news.example.com; option pop-server pop3.example.com; option smtp-server smtp.example.com; option wpad-curl code 252 = text; #option wpad-curl "http://proxy.example.com/wpad.dat"; option www-server example.com; option ntp-servers time.example.com; option time-offset 34200; # Australian Central Standard Time #option time-offset 37800; # Central Australia Daylight Time # Seem to be stupidly stuck with manually setting this! # Daylight savings: 2am last Sun of Oct - 3am first Sun of Apr option ip-forwarding off; # tell clients not to act as gateways (?) shared-network example.com { option wpad-curl "http://proxy.example.com/wpad.dat"; subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.100 192.168.1.200; option routers 192.168.1.2; # default gateway option subnet-mask 255.255.255.0; option broadcast-address 192.168.1.255; option domain-name-servers 192.168.1.2; option netbios-dd-server 192.168.1.2; option netbios-name-servers 192.168.1.2; # WINS option netbios-node-type 8; option netbios-scope ""; option finger-server finger.example.com; zone 1.168.192.in-addr.arpa. { primary 192.168.1.2; key rndckey; } zone example.com. { primary 192.168.1.2; key rndckey; } # we want the nameserver to appear at a fixed address # (Any terminal saying it's ns.example.com will be # assigned this IP.) host ns { #next-server ns.example.com; fixed-address 192.168.1.2; } host fixed { fixed-address 192.168.1.99; } host fixme { fixed-address 192.168.1.150; } #host flakey { # hardware ethernet 00:00:21:25:92:fb; # fixed-address 192.168.1.180; # option host-name "deadmeat"; # update-static-leases on; #} # host rover { # hardware ethernet 00:48:54:8e:8c:0c; # fixed-address 192.168.1.18; # # set ddns-rev-name = "101.1.168.192.in-addr.arpa."; # fixed-address rover.example.com; # option host-name "rover"; # } } subnet 192.168.2.0 netmask 255.255.255.0 { range 192.168.2.100 192.168.2.200; option routers 192.168.2.2; # default gateway option subnet-mask 255.255.255.0; option broadcast-address 192.168.2.255; option domain-name-servers 192.168.2.2; option netbios-dd-server 192.168.2.2; option netbios-name-servers 192.168.2.2; # WINS option netbios-node-type 8; option netbios-scope ""; option finger-server finger.example.com; zone 1.168.192.in-addr.arpa. { primary 192.168.2.2; key rndckey; } zone example.com. { primary 192.168.2.2; key rndckey; } host ns { #next-server ns.example.com; fixed-address 192.168.2.2; } host fixed { fixed-address 192.168.2.99; } } } # ------------------ end of it all --------------------------------------- -- Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.