Packages wishlist?
-
I would like to see one package to SARG (Squid Analysis Report Generator).
I'm starting to use pfsense 1.0-RC2 4 days ago. Great work! How can I build one SARG package?
Thanks,
fricardo
-
There is not much documentation on how to create a package, however some pointers can be found where to start at the forum. Please search.
-
I would like to see ipfm + scr_ipfm integrated
Keep up the good work.
Greetings Darek
-
the good service to addon pfsense…apcupsd for APC UPS...
-
It would also be nice to have a lightweight (relative to sendmail/postfix anyway) SMTP reverse proxy capable of scanning email for junk and virus signatures. This would be a transparent reverse proxy for SMTP (& SMTPS?), preventing junk mail and virus emails from ever making it to the mail servers inside. (Check out ASSP and DspamPD if you're looking to get a better idea of the concept.
ASSP doesn't support AV scanning and DspamPD hasn't been actively developed for over a year.
-
I liked the idea of a 'voting system' for package suggestions. I would really like to see something out there to enforce corporate content-filtering policies. Right now, the squid package somewhat addresses the web side. The SMTP part is a bit less interesting unless you are putting the firewall in your production environment (as opposed to office) where it can behave as a server-side proxy. I have successfully used transparent POP3 proxying in the past. However, I dont think its a very clean way of doing email filtering.
The one still missing from most distros is instant messaging proxying/filtering for the main clients (MSN/Yahoo/AOL/Google). This would allow for a complete content-filtering solution. (Web + IM, while mail is imparted). Note that some suggested antivirus support for the web proxy, this is fairly difficult to implement, and very unefficient. (Because the proxy cant really know if its a virus until the download is .. well.. done).
As for SMTP filtering (SpamAssassin and such) - I do think that spam filtering without a proper quarantaine solution is a bit wreckless. As such, I would be tempted to leave the spam filtering to a dedicated solution. However, blocking malicious code and extensions as well as defanging potentially dangerous dynamic content are all very feasible tasks. I myself would tend to focus on these features.
Someone proposed bind as a package. I find the mention of bind running on a firewall a little disturbing =P I frankly don't really see the point of running DNS off a firewall. It seems somewhat off-focus.
Just my 2 cents -
-
Congrats on the gold release! I've been impressed with pfsense from the beginning when I discovered it from a m0n0wall source.
My 2 cents on the packages wishlist:
-FakeAP(http://www.blackalchemy.to/project/fakeap/)
-Linblock (http://www.dessent.net/linblock/) this is really just a script but I have no clue how to implement it on BSD
-A package allowing you to provide a one-time (expiring) link to a file download from the local freeNAS raid volumes (scawf if you want…)These were already talked about but I 2nd the request for these:
snort
nagios
asterisk
tftp/pxe capabilities
dansguardian
cupsI saw these in the list pre 1.0 so I'm hoping they'll get re-added:
freeradius
freeNASThanks for listening!
-
Snort is already included. The TFTP/PXE proxy is in HEAD and should make its way to a future version.
-
I would like to see a content filter package using Dansguardian.
-
I'd like to see no-ip.com client as package for pfsense so I don't have to remember my ip address all the time, which isn't static anyway.
-
I'd like to see no-ip.com client as package for pfsense so I don't have to remember my ip address all the time, which isn't static anyway.
It's already there: services>Dynamic DNS.
-
-
I would like to see spam filtering ie:spamassassin
Content filtering ie: squidguard, dansguardianThanks
-
This :
http://www.imspector.org/
Would be a very valuable addition. It's basically a Instant Messenging proxy, which means that it can be used to provide logging facilities that are mandatory for most security certifications.
It could also be used to block IM file transfers and eventually provide antivirus/extension-based blocking. Its a great addition to pfSense because this way it could provide application-layer filtering for the three main point of entry for viruses/malware: web, email and im.
-
I would love to have a monitoring/net management package that is suitable even for an embeded edition and yet capable of monitoring via SMTP, IMAP, POP3, HTTP,TCP,UDP, NNTP, and PING tests and posting results in html or terminal.
http://www.sysmon.org/config.html
Rrealtime accounting and monitoring would be nice to have as well:
pktstat (FreeBSD port exists)
->listens to the network and shows the bandwidth being consumed by packets of various kinds in realtime. It understands some protocols (including FTP, HTTP, and X11) and adds a descriptive name next to the entry (e.g., 'RETR cd8.iso', 'GET http://slashdot.org/' or 'xclock -fg blue').iftop (FreeBSD port exists)
->listens to network traffic on a named interface, or on the first interface it can find which looks like an external interface if none is specified, and displays a table of current bandwidth usage by pairs of hosts.monit (compiles under FreeBSD); http://www.tildeslash.com/monit/
->monit is a utility for managing and monitoring, processes, files, directories and devices on a UNIX system. Monit conducts automatic maintenance and repair and can execute meaningful causal actions in error situations.my 2c…
regards,
mr-s -
A LPR/LPD package to support using pfSense as a print (printer) server would be nice. Preferably with SAMBA support.
-
FreeRADIUS additions/modifications…
I've configured FreeRADIUS to add eap_tls and eap_ttls to authenticate my access point for WPA2-CCM on my pfsense box. What would be nifty is a the ability to integrate the CA similarly to how it is done for IPSEC VPN's to manage certificates for both the CA and users. This would give users the option to utilize either eap_tls or eap_ttls (for the more lazy). If you think about it, possibly just a centralized CA that was separated per duty might be sufficient (e.g., one for IPSEC another for OpenVPN, another for WPA, however utilizing the same openssl.cnf, etc and just splitting off different directories per usage type). Sorry for rambling... but I think this might provide a nice feature and pull together any loose ends that utilize certs for a auth method.
-
OSPF and RIP I + II would be on the top of the list.
Newer nVidia chipsets.. 4+
64 bit support would be nice too. -
OSPF and RIP I + II would be on the top of the list.
routed: RIP v1 and v2 daemon
Already available as package. -
I'd like to second the request for TorrentFlux. This couldn't be too hard to implement, TorrentFlux itself is just a PHP controlled implementation of BitTornado as far as I understand.
