Subject: Re: DHCP and multiple NICS
From: Arthur Corliss (arthur@corlissfamily.org)
Date: Wed Mar 27 2002 - 11:53:42 AKST
> ok I did some more reading(old posts) and I think this should work.
> Do any of you see any problems with my dhcpd.conf file?do I need a
> shared-network entry? from what I read I just need to start dhcpd
> -q eth1 eth2
>
> thanks
> jeremy
>
> # eth1 ip 192.168.1.254 3com10/100
> subnet 192.168.1.0 netmask 255.255.255.0 {
> range 192.168.1.11 192.168.1.254;
> option routers 192.168.1.254; # gateway
> option domain-name-servers 192.168.1.254, 12.6.42.1;
> default-lease-time 3600;
> max-lease-time 7200;
> }
> # eth2 ip 192.168.3.254 3com10
> subnet 192.168.3.0 netmask 255.255.255.0 {
> range dynamic-bootp 196.168.3.100 192.168.3.199;
> option routers 192.168.1.254;
> option domain-name-servers 192.168.1.254, 12.6.42.1;
> default-lease-time 3600;
> max-lease-time 7200;
> }
I assume you're wrapping both of those sections in a 'shared-network LAN { ...
}' section? Also, look at your router assigned for the .3 subnet -- there's
no route to the gateway. ;-)
A final bit of advice: if you're doing name services on that same box, you
might as well tell that subnet to send request directly to the .3 interface
for the .3 subnet, instead of routing that traffic through your firewall
rules. It would work either way, of course, but why make this harder than it
has to be? It'll bite you in the rear-end if you start isolating the segments
completely.
----Arthur Corliss Bolverk's Lair -- http://arthur.corlissfamily.org/ Digital Mages -- http://www.digitalmages.com/ "Live Free or Die, the Only Way to Live" -- NH State Motto
This archive was generated by hypermail 2a23 : Thu Mar 28 2002 - 04:45:13 AKST