Profile Details

Toggle Sidebar
Recent updates
  • Glad it is working now.

    The forum is making a mess of my egrep rule. It should start "single quote" then "colon" then "open bracket", but it looks like the "colon" then "open bracket" is being dropped by the forum (a smilie?). This may show better and achieve the same thing:

  • Nick Howitt
    Nick Howitt's reply was accepted as an answer

    Re: Dhcp server not serving ip addresses to clients

    The netstat command should have been:
    I can pick out what I needed from yours.

    The problem appears to be the firewall. It is only open to DHCP when ClearOS is toying to get its connection by DHCP. You will need a custom firewall rule as an incoming rule uses your WAN IP and initial packets are broadcast to 255.255.255.255 and not directed to the WAN interface, so, at the command line try:
    If that works, change the "iptables" to "$IPTABLES" and put it into the custom firewall module.

    BTW, you will need to get quite involved with your firewall if you are firewalling ClearOS from your LAN. If you want it to act as your DNS server you'll need to open udp:53 and tcp:53. If you want it as a file server you'll need more for Samba and so on. Normally Standalone with Firewall is meant for a standalone internet facing device.

  • The netstat command should have been:
    I can pick out what I needed from yours.

    The problem appears to be the firewall. It is only open to DHCP when ClearOS is toying to get its connection by DHCP. You will need a custom firewall rule as an incoming rule uses your WAN IP and initial packets are broadcast to 255.255.255.255 and not directed to the WAN interface, so, at the command line try:
    If that works, change the "iptables" to "$IPTABLES" and put it into the custom firewall module.

    BTW, you will need to get quite involved with your firewall if you are firewalling ClearOS from your LAN. If you want it to act as your DNS server you'll need to open udp:53 and tcp:53. If you want it as a file server you'll need more for Samba and so on.

  • Nick Howitt
    Nick Howitt replied to a discussion, RPM build / drivers for ClearOS

    Check that your build set up brought in the kernel headers, then


    • Upload your source file into /home/{build_username}/rpmbuild/SOURCES
    • From the command prompt log on as your build_username with a:
    • navigate to the SOURCES folder:

    • and build it:

    • rpm will be in ../RPMS/x86_64

  • I guess this calls for more intense troubleshooting. I know you're running a desktop on ClearOS, but can I suggest some remote access with PuTTy and WinSCP. With PuTTy (a terminal) you can copy text just by selecting it. Then you can paste it straight into the forum.

    Can you check dnsmasq is running with a:
    and that it is running as expected:
    You can paste into PuTTy just by right-clicking.

  • They should not be related. The file you probably edited was /etc/resolv.conf. I suggest you change it back then in the Webconfig, in IP settings set a manual DNS server of 192.168.13.1. If you have to change a file, edit /etc/resolv-peerdns.conf instead but using the Webconfig is preferable.

    The use of a GUI in ClearOS is not recommended. Have you tried using kimchi instead. I've never tried it so it is not a recommendation.

    I still can't think why DHCP is not working unless the GUI came with its own network management utilities (especially NetworkManager) which are interfering with ClearOS

  • Nick Howitt
    Nick Howitt replied to a discussion, Sentinel RMS -

    ClearOS does not support 32-bit. From a documentation link I found it looks like Red Hat Enterprise Linux 7.x support is 64-bit only anyway. I did not see any installation instructions so I don't know what is going wrong.

  • I can't do pictures either. I just attach files, but then I can't control where they go in the post.

    Your network should work but I would put the DNS servers the other way round. That does not affect DHCP leases.

    I assume you've given ClearOS a Static IP? I'd normally give it a low one or high one but it should work with .28 as long as it is fixed. With your router on .1 I'd normally give it .2 or .254 (and adjust the DHCP scope).

    If your client PC is Windows, it may detect a new network, in which case it needs to be configured and trusted.

    I can't think of any obvious reason why it is not working. You may need to run tcpdump on ports 67 and 68 to sniff what is happening.

  • Is ClearOS in Gateway or Standalone mode?

    If you're disabling DHCP in the router but still using it as your gateway, I'd expect ClearOS to be in Standalone mode. If it is replacing your router as the gateway it should be in Gateway mode.

    Can you make a diagram or describe your set up (with IP addresses as well)?

    Also, what is the contents of /etc/clearos/network.conf and the result of the command

  • Nick Howitt
    Nick Howitt replied to a discussion, Talos Blacklist Script

    Hi Gary,
    Many thanks for this contribution. Can I suggest you use "code" tags for your code. I've edited one line to stop the link from breaking when clicked on.

    If you're just tagging these onto a country list (is it one I scripted?), you can add them to the existing ipset set with the "-exist" switch which will avoid them being duplicated. This should simplify your script.

    Also, rather than flushing the talos-list then reloading it, which temporarily leaves the set empty, you can just load everything into an talos-list-temp list then swap the lists over with an "ipset swap talos-list talos-list-temp". Then you can destroy your talos-list-temp ready to start again.