- #CONFIGURE DNS O MATIC WITH UNTANGLE FIREWALL INSTALL#
- #CONFIGURE DNS O MATIC WITH UNTANGLE FIREWALL PRO#
I set the firewall PC up on my test bench, and used the disc I had burned earlier to boot the PC and do the install.
I used red (external) and green (internal) dot stickers to mark the interfaces on the physical machine, to make them easy to identify when installing or servicing the firewall.
#CONFIGURE DNS O MATIC WITH UNTANGLE FIREWALL PRO#
I wound up getting better than minimum, which is always nice! The PC I used is an HP Compaq 6000 Pro Microtower (P/N VS931UT#ABA), with a Pentium E6700 Dual Core 64-bit 3.2 GHz processor, 8 GB (2 GB X 4) PC3-10600 RAM (4 slots, expandable to 16 GB max), a 250 GB Western Digital 7200 RPM SATA 6.0 Gbps Caviar Blue hard drive, integrated gigabit ethernet NIC, and a Broadcom PCI Express add-in NIC.īefore starting the install, I made sure I had documented as much as I could for the NICs, and chose which NIC would be the external (WAN) interface and which the internal (LAN). As a minimum, I specified a Pentium 4 or better processor, 1 GB RAM, 80 GB HDD, and no O/S (as the hard drive would be wiped when I installed Untangle). The system requirements were important, as I was requesting hardware for donation, and I wanted to be as specific as possible.
#CONFIGURE DNS O MATIC WITH UNTANGLE FIREWALL INSTALL#
I started by reviewing the documentation, downloading the software (v12.0.1, 32-bit rather than 64-bit, as recommended on the forums), and burning an install disc. I did not want to spend a lot of time setting the firewall up and learning the interface, so this was key.
I decided to go with Untangle, based on a few factors:ġ) I didn't need any advanced bridging / routing (apparently PFSense is better at this).ģ) From what I read, the Untangle GUI was somewhat better and easier to navigate than PFsense. They both looked like great products, and I hadn't worked with either one before. I quickly narrowed the list down to Untangle and PFSense. The Spiceworks forums were a great resource for research, as usual, particularly this post. Other primary considerations were a lack of IT budget, and my desire to have a reliable, stable device with minimal maintenance requirements. As they had previously had numerous malware issues, I wanted to provide them with something more robust, that would preferably include Intrusion Detection / Protection functionality and virus scanning. When I first did the site evaluation, my client (a small non-profit) was using a TP-Link home class router as their primary edge device.