Perry, DHCP requests are broadcasts that only go out on the interface that requires DHCP service. If eth0 requires DHCP configuration, but eth1 does not, then DHCP requests will only go out on eth0. IOW, eth0 will only talk to the cable modem for DHCP and eth1 will only talk to your internal DHCP server (if not statically configured). UNLESS you have dhcp forwarding configured somewhere, which you shouldn't. Hope that helps, Bruce Broecker Network Engineer The Toro Company bruce.broecker at toro.com >>> tclug-list-request at mn-linux.org 03/26/02 08:24AM >>> Message: 9 Date: Mon, 25 Mar 2002 21:56:21 -0600 From: "Perry Hoekstra" <dutchman at uswest.net> To: tclug-list at mn-linux.org Subject: Re: [TCLUG] DHCP Question Reply-To: tclug-list at mn-linux.org Chris Feist wrote: > On Sat, Mar 23, 2002 at 09:00:26PM -0600, Perry Hoekstra wrote: > > My question is, what would prevent my firewall box from > > grabbing an IP address from my internal DHCP server versus the cable > > modem? > > Just make sure that your dhcp server only listens/responds to the interface > that is not connected to your cable modem. > > Assuming that your cable modem is on eth0 and your network is on eth1 you would > run dhcpd like this: 'dhcpd eth1'. This may differ depending on what dhcp > server you are running. Actually, it is the dhcp client (in this case pump) that I am worried about. I want it to look to the cable modem on eth0 for the DHCP server rather than eth1 which is the internal network where a second DHCP server resides for my laptop and other sundry boxes. -- Perry Hoekstra E-Commerce Architect Talent Software Services perry.hoekstra at talentemail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://shadowknight.real-time.com/pipermail/tclug-list/attachments/20020326/964d51a1/attachment.html