I've seen this on a Bering box where eth1 was a PCMCIA device. The problem was that the device was not yet activated at the time that dhcpd was started. Hence it didn't find the IP declared in dhcpd.conf and gave this cryptic error (dhcpd is edited to suit your system I hope?). My solution was to go into the init script (/etc/init.d/dhcpd) and set the RCDLINKS value to a higher number. This caused dhcpd to be started later (I set it to go after shorewall), after the card was activated.
Might be worth a try or might be totally irrelevant! Brock > Message: 7 > From: "steve crowl" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Date: Tue, 30 Apr 2002 11:50:39 -0500 > Subject: [leaf-user] dachstein question > > Hello. I received the following log message attempting to run > dachstein (I have successfully run eigerstein on same configuration): > > firewall dhcpd: No subnet declaration for eth1 (0.0.0.0). > firewall dhcpd: Please write a subnet declaration in your > dhcpd.conf file for the firewall dhcpd: network segment to > which interface eth1 is attached. firewall dhcpd: exiting. > > Suggestions?? Thanks > > Regards, > Steve _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ------------------------------------------------------------------------ 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
