• config: 82,977 organized crime, RBN affiliates, malware hosts, and bad actor domains blacklisted for Smoothwall 3. Leave last line blank. Use open source software such as WinSCP? or Filezilla to transfer the config file into /var/smoothwall/hosts/. Updated 7-11-2010.

• hosts: Protect your family and home network from 82,977 of "the baddest of the bad" domains blacklisted for Smoothwall 3; shield your small business from liability. Place hosts in /var/smoothwall/hosts/. Blacklisted domains resolve to 127.0.0.1. Modify line 2 to match your local area network CIDR (i.e. 192.168.1.0/24, 10.0.0.0/24, etc. ). 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 de-listing. Updated 7-11-2010.

• 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.

• http://sourceforge.net/projects/smoothiemods/ Smoothwall Homebrew Mods at sourceforge

Be certain to apply Smoothwall's available update patch packages.

If you are using Bind, David Glosser's DNS BlackHole http://www.malwaredomains.com/ provides the best available Malware Domain Blocklist.

• http://doc.emergingthreats.net/bin/view/Main/SuricataUbuntuSetup Simple Suricata Installation on an Ubuntu laptop
• http://doc.emergingthreats.net/pub/Main/SuricataUbuntuSetup/Suricata_Ubuntu_Laptop_Setup.txt This text file will make it easy for you to copy and paste your way to a successful Suricata installation.

• InstallAndConfigureHoneywall.pdf: InstallAndConfigureHoneywall?.pdf

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.

• UsingHoneywall.pdf: UsingHoneywall?.pdf (as presented at Berkman Center, Harvard Law School, May 16th, 2008)

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

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

• A_Novices_Guide_to_Using_Multiple_Layers_of_Snort_to_Defend_the_Home_Network.doc: Bleeding topology for the home: Honeywall Roo 1.1 and 1.2

• A_Novices_Guide_to_Using_Multiple_Layers_of_Snort_to_Defend_the_Home_Network.pdf: Bleeding topology for the home: Honeywall Roo 1.1 and 1.2

• 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.

• reboot.pl.txt: Reboot Honeywall on a schedule.