>Hanspeter Roth: > >>>> So what could be the cause? > >Tim: > >>> SELinux? > >Hanspeter Roth: > >> Yes, what should I check or change with about >SELinux? > >Well, you did *just* ask what could be the cause... >;-) > >If you're using the GUI, you could run the "security >level" tool and >look through the SELinux options related to DHCP, and >make adjustments >where you see fit. > >I don't recall having any problems getting my DHCPD >server running. >You're not trying to run the client and the server on >the same PC, are >you? > > I had the same problem myself and I had to tweak SELinux to make it work. Also make sure you open the port 68 for access if you have a functional firewall. But as Roth said and considering your error message it seems to be SELinux related. As a simple diagnostic you can try to turn off all SELinux settings related with dhcpd. Type system-config-securitylevel in a terminal, go to SELinux tab and turn off all the dhcpd settings there. If after you do this your dhcpd works, that means obviously that SELinux is at fault. regards, Val __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com
