Why did the Packet Protector project stop?

[John Fields]

So..... http://packetprotector.org/

"PacketProtector.Org is an example of all the things that are good about open source and free software." ~Linux.com

The project ran for 4 yrs and then came to an orderly stop.  Did it fork? I don't know, but that would be comforting if it did.  Forking is a natural part of many projects evolution, as they change their DNA to stay relevant to the problems they mean to solve.  At any rate, since it is very similar in goals to HFR I think it would be instructive to look at WHY the project tapered out.

Here's what you get-

• a stateful firewall (iptables)
• WPA/WPA2 Enterprise wireless (802.1X and PEAP with FreeRADIUS)
• intrusion prevention (Snort-inline)
• remote access VPN (OpenVPN)
• content filtering/parental controls (DansGuardian)
• web antivirus (DG + ClamAV)
• a local certificate authority (OpenSSL)
• secure management interfaces (SSH and HTTPS)
• advanced firewall scripts for blocking IM and P2P apps
• IP spoofing prevention (Linux rp_filter)
• basic protocol anomaly detection (ipt_unclean)
• anti-phishing (OpenDNS)
• automatic signature/rule updates

Each of these services is automatically bootstrapped and configured with sensible defaults. A secure web interface makes common configuration tasks as simple as a point and click.

Sounds good to me!

[John Fields]

From a 2008 post on https://isc.sans.edu/forums/diary/Tools+for+the+Home+User/3815/

The prerequisite for this 'unified threat management device' is a Linksys WRTSL54GS or ASUS WL-500g, which I priced as high as $150 and as low as $80-ish for both makes and models. While the concept is nice, I don't need another router and this firmware appears exclusive to only those two models...I certainly can't experiment with this unless I make a point of purchasing one of those routers.