r38 - 20 Dec 2009 - 16:52:15 - JamesMcQuaidYou are here: TWiki >  Main Web > AllProjects > SnortConfSamples > HoneywallSamples

Honeywall and Smoothwall Configuration Samples

UnderstandingDNSBlackHoleInHomeDefense.jpg

Smoothwall Express 3.0: be certain to apply the available update patch packages.

  • hosts: Protect your home from 300,413 bad domains for Smoothwall 3; placed in /var/smoothwall/hosts/. Note: with this many objects in BlackHole, you must use local loopback (blacklisted domains must resolve to 127.0.0.1). Modify line 2 to match your local network. You can use an open source program, such as Notepad++, to edit these files. Note: If you believe that your domain should not be listed, please let us know and we will review it for delisting. Updated 12-20-2009.

  • dedupe.pl.txt: Rename to dedupe.pl. Sorts and removes duplicate entries in Smoothwall's /var/smoothwall/hosts/config file; populates configNew file (which you then rename to config). With slight modification, you can also use this to dedupe IP address lists.

  • snort_smoothwall3.conf: Snort.conf for Smoothwall. This configuration uses Stream5 and a large number of rules, but runs on a machine with 1 GB of RAM.

  • config-ipblock_Smoothwall3: IP blocks for Smoothwall 3: includes Russian Business Network IP addresses. This file can only handle 720 IP ranges, after which the batch file will no longer be processed. The config file in the var/ipblock folder is processed as a batch file. After the config file attains a certain size, the following error is logged in the var/log/messages file: "smoothd ipbatch buffer size exceeded". This error may also be observed in the web interface in logs.cgi under SmoothD?. If you wish to block larger numbers of malicious IP addresses, you must use another firewall. Updated 7-13-2008.

DNS Bind:

  • bindzone: Experimental. Do not use this bind zone file in a production environment unless you have tested it. A viable alternative to corporate whitelisting. Contains 300,413 domains and objects. Updated 12-20-2009.

Honeywall Roo 1.4: Honeywall 1.4 has emerged from beta. 'Out of the box' it functions with a reduced Snort Inline ruleset. To use the Emerging Threats rules, you must: 1) copy the Emerging Threats rules into the Snort-inline folder, and 2) log in as root (su -) at the console, run /user/sbin/menu, and Generate IPS Rules. The strategy in this topology is to leverage Snort Inline to protect Smoothwall and the workstations. You can use Snort arrays to spread the load and eliminate a single point of failure.

Honeywall Gateway: Honeywall 1.2 . This configuration will utilize over 900 MB of RAM.

  • snort_inline.conf: Most rules are set to drop; do not use Honeywall's autogenerated replace rules. Will Metcalf, the current maintainer of snort_inline, does not recommend blindly converting as many rules as possible to use replace. Will has said to not use replace in rules that contain the keyword flowbits:noalert because they are used in protocol identification/behavior, and are later checked in separate rules that alert/drop.

  • blacklist.txt: The /etc/blacklist.txt file specifies incoming traffic to be blocked based upon source IP address. Based upon the Bleeding All Firewall rules.

  • fencelist.txt: The /etc/fencelist.txt file specifies outgoing traffic to be blocked based upon destination IP address. Updated 4-12-2008.

  • crontab: crontab file for Honeywall which schedules reboot.pl and clean.pl

  • clean.pl.txt: Clean out Honeywall's logging directories on a schedule if you have limited hard disk space.

-- JamesMcQuaid - 13 July 2008

Topic attachments
I Attachment Action Size Date Who Comment
elseEXT bindzone manage 24351.4 K 20 Dec 2009 - 16:39 JamesMcQuaid  
elseEXT config-hosts manage 9682.8 K 20 Dec 2009 - 16:45 JamesMcQuaid  
elseEXT hosts manage 8509.4 K 20 Dec 2009 - 16:48 JamesMcQuaid  
elseconf snort_smoothwall3.conf manage 35.0 K 10 Dec 2009 - 03:10 JamesMcQuaid  
Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r38 < r37 < r36 < r35 < r34 | More topic actions
 
Emerging Threats
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback