ClearFoundation

Just set the dhcp server to run on 127.0.0.1. That way it doesn't answer anyone. DNSMasq integrated dhcp and its a nice neat new package for most. Or you could uninstall dnsmasq, or do a "chkconfig dnsmasq off" and then install bind, configure, create zones, chroot, etc.

V/r,

Matt

You should be able to just turn off the DHCP server by interface as I posted earlier. Have you tried that?

You can remove the 'front ends' easily and these all begin with app-xxx. The app-xxx-core packages provide libraries to other apps, but not the front end - they typically go hand in hand. The DHCP service is provided by dnsmasq as pointed out earlier... which also provides the local DNS so if you remove it it removes both

The easiest way is just to delete the DHCP range in the webconfig?? this has the effect of disabling DHCP server. Nothing else is required...as Nick points out you probably need DHCP for your WAN

If you want to get under the skin...just run 'service dnsmasq stop' and the following will prevent it from starting automatically 'chkconfig dnsmasq off'

For firewall rules, if you want to manually edit them as a last resort - have a look in /etc/clearos/firewall.conf. Then run 'service firewall restart'

Nick -

I was playing around with some other things so I hadn't tired your approach until now. I deleted both of the subnets I had listed (LAN and WAN) and when I rebooted my desktop it still recieved an address from the ClearOS DHCP service. The configuration file in the directory /etc/dhcp was cleared out when I deleted the subnet, but the file /etc/dnsmasq.conf was not cleaned up and it contains the dhcp-host directive for assigning IPs to names, along with a few other dhcp configuration parameters. I had to take Tim's approach and run a 'service dnsmasq stop', followed by a 'chkconfig dnsmasq off'. My conclusion here is that there needs to be a simple way in the interface to stop a service (feature request #1). And also if you uninstall an app it should run a service stop and a chkconfig off (feature request #2).

Jeff

Tim's approach is far more wide-reaching as it stops you, for example, using ClearOS as a standalone DNS server. It also stops your WAN from obtaining an address by DHCP. If what you are saying is correct then you have hit a bug. The file which contains the LAN side DHCP information is /etc/dnsmasq.d/dhcp.conf and for me deleting the interface from the webconfig dhcp server clears out the file (just leaving the line "read-ethers") which is what I would expect. I don't think the file /etc/dnsmasq.conf matters as they are general defaults and not the interface specific settings.

When you deleted the DHCP server set up for the interface, on your LAN desktop, did you do an "ipconfig /release" and "ipconfig /renew" in a command prompt or reboot the machine?

After I deleted the DHCP server setup for the interface I did an ipconfig /release and /renew, then did a ipconfig /all to see the complete listing. It was clear that I was getting the ip adress from the ClearOS box because I had not turned back on my other CentOS VM that I had previously been using for the DNSmasq server. Knowing Windows can be stubborn sometimes I then rebooted the LAN desktop box and it came up with the same thing. That is when I issued the commands from Tim's suggestion.

I realize that doing a 'service dnsmasq stop' and 'chkconfig dnsmasq off' would be a sledgehammer approach, but I wanted to make sure that I had everything stopped. After this I did an ipconfig /release and /renew and got the expected result (garbage), until I restarted my CentOS VM that is running DNSmasq.

I think it is interesting that even with DNSmasq shut off, you can't really tell from the web GUI. The DNS server still shows all the IP / Hostname mapping. And even more confusing, the DHCP web interface still lists two client leases, even though one of them is my desktop box and I am certain its lease is from my CentOS VM.

I think I may do a yum remove dhcp and also remove the ClearOS app, then re-install fresh to make sure I have a clean base, because I think I want to use the DNS service on the ClearOS box still (still thinking through my setup).

Jeff

A little late now I suppose but just went through the same DHCP issue. I found removing the app did indeed not stop the IP's being handed out.
However after a restart of the Clear box it has stopped handing out IP's.

Some times rebooting the firewall isn't an option. Deleting the scope in the web interface and running the 'service dnsmasq restart' at the command line resolves the issue without having to restart the firewall.