This is a discussion on SuSEfirewall2 DHCP Issues within the Linux Security forums, part of the System Security and Security Related category; Greetings! I have a bizarre problem that I'm hoping someone here may have answer to. I am running SuSE ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Greetings!
I have a bizarre problem that I'm hoping someone here may have answer to. I am running SuSE 9.1 Pro as a sole file/print server, with DNS, DHCP, Samba, postfix etc. Everything works great, I turn on the firewall through Yast, setup the basic config (the GUI is extremely limited BTW), allowing the apps & ports where applicable. Everything works EXCEPT for DHCP, and I have been unable to determine what I'm doing wrong. So far: I added TCP ports 67 & 68 in the GUI (Yast), and verified they were there in the SuSEfirewall2 config file. FW_SERVICES_EXT_TCP="67 68 ..." I added UDP ports 67 & 68 in the SuSEfirewall config file (as the GUI fails to offer UDP "option") FW_SERVICES_EXT_UDP="67 68 ..." For grins.., I even added the ports to the internal config (FW_SERVICES_INT_UDP="67 68"), even though the server connects to the LAN via an external card only. I also changed the DHCP daemon to yes (FW_SERVICE_DHCPD="yes"), all to no avail. All other services, apps and ports work as they should, but DHCP just will not talk to any client requesting an address, until I disable the firewall. I ran Ethereal on the client, and sure enough, the client requests for DHCP are using ports 67 & 68 like they should. Any suggestions? Thanks in advance! -- Steve Whittlesey | guitrwiz.com System Engineer| Guitarist Erie, Colorado | USA |