joah -- You should not need to create a dhcpd subnet declaration for eth0. Since that is your external interface, you should not even be considering offering leases on it.

But the default behavior of dhcpd is to listen on all (or, more precisely, all broadcast) interfaces. You change that not in /etc/network/interfaces ... which has nothing whatsoever to do with this problem ... the references to DHCP in it invoke dhcpcd, the client, not dhcpd, the server ... but in whatever script starts the dhcpd daemon. It needs to be invoked as

dhcpd eth1

and not simply as

dhcpd

Since I don't know what you did in adding (or restoring) dhcpd to your router, I cannot tell you exactly how to go about correcting this ... but perhaps this is enough of a hint that you'll be able to track it down now.

At 01:01 AM 2/19/2004 +0000, joah moat wrote:
[details deleted]
Feb 18 17:32:31 firewall dhcpd: No subnet declaration for eth0 (68.148.245.3).
Feb 18 17:32:31 firewall dhcpd: Please write a subnet declaration in your dhcpd.conf file for the
Feb 18 17:32:31 firewall dhcpd: network segment to which interface eth0 is attached.
Feb 18 17:32:31 firewall dhcpd: exiting.



Why should I need to declare dhcpd for eth0? I just want my eth1 to broadcast a private network address to my network.




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html

Reply via email to