Keeping dhcpd on a particular interface

[dunkirk]

I can't seem to keep dhcpd stuck to one and only one interface. My DHCP server is running on my firewall machine, which has an interface for my broadband connection. The way the configuration is working right now, I'm handing out IP addresses to misdirected client requests coming through over my broadband interface. (I have lots of strange machine names in my /var/lib/dhcp/dhcpd.leases file.)

I have the option in /etc/conf.d/dhcpd:

DHCPD_IFACE="eth2"

And when I run the service, I see that it's translating all the way through the init process:

5 S dhcp 14100 1 0 84 0 - 686 - 09:46 ? 00:00:00 /usr/sbin/dhcpd -q -pf /var/run/dhcp/dhcpd.pid -cf /etc/dhcp/dhcpd.conf -user dhcp -group dhcp eth2

But when I look:

reliant init.d # netstat -anp|grep dhcp
udp 0 0 0.0.0.0:67 0.0.0.0:* 14100/dhcpd
raw 0 0 0.0.0.0:1 0.0.0.0:* 7 14100/dhcpd

So it's listening on all interfaces. I expect this to be more like "192.168.0.254:67". Where am I going wrong?
_________________
Acts 17:28, "For in Him we live, and move, and have our being."

[pilla]

Strange. I have a similar configuration, but I guess my firewall is keeping outside machines from connecting to my dhcpd daemon.

Maybe you could filter UDP/67 on the broadband interface, just as a temporary solution (leaking dhcpd servers are annoying).
_________________
"I'm just very selective about the reality I choose to accept." -- Calvin

[dunkirk]

I have a "dumb" modem, with no firewall capability. This is what I wanted, as I wanted to handle all of this with Linux.

Maybe there's still a way to filter this with Shorewall, but, of course, I already block almost all traffic at my firewall. This is still getting through. I'm guessing that this is because it's broadcast traffic. A cursory Google on the problem reveals this:

http://openvpn.net/archive/openvpn-users/2003-09/msg00060.html

Which basically says that it's NOT because it's broadcast traffic, but that it's socket traffic that happens before the firewall rules kick in. So I guess I can't use a firewall to block the packets, if I'm serving DHCP from the firewall itself.

So I still need to isolate which interface(s) that the DHCP server is listening on.
_________________
Acts 17:28, "For in Him we live, and move, and have our being."