Packages wishlist?
-
@Admins
I know that this is the time to settle down and hunt critters to reach 1.0 with reliability.
But I'd like to start this topic for the long run future.@all
Hi guys,
I was wondering, wish packages would you like to see in pfSense besides the ones that we already have?
Post your thoughts.Cheers
-
I think that after "a reliable version" pfSense should enable interaction with other free/commercial products, or at least stablish an API in order to communicate other products with pfsense in a structured manner ;)
Hope this helps and likes ;)
Regards!
jonathan
-
Go ahead, This thread is now stickied.
Maybe later we can add polls based on what's in this and other whislists.
Please do NOT crosspost or post duplicates.
-
Just judging from the comments on the mailing list I think the following packages are probably likely to show up on the wishlist:
HAVP (especially if it can be integrated cleanly with squid)
Dansguardian (probability of licensing issues for commercial users)
p3scan (will require either dspam or spamassassin)I'd be interested to see what other spam/virus filtering solutions people would like to see packaged up. For a firewall, there isn't a single pre-packaged solution to do the job. I think after the new package infrastructure is in place there will be a real influx of very interesting packages. At least I hope so.
-
It depends on what the focus of pfsense is? and what the developers define as a successful project.
Distrowatch has hundreds of distros and projects each with a focus that is successful or not so. If a definition of success is the sheer number of users and the size of the community, then features are critical in the development of a distro. There are a number of projects in the firewall space each with their own advantages, however if pfsense is to become a hugely successful community then looking at firewall project features that are popular is important as this will attract interest to develop a community.
For example IPCop is sucessful in that it has had 2.5 million downloads for the 1.4 series, however I do not think the project developers are aware just how much the addons with features such as content filtering and client side friendly VPN projects such as OpenVPN popularize the project.
Given this, how does a development team decide what will be a successful feature?
-
If this forum was to incorporate a feature where users could submit packages for consideration to a poll or vote, then the development team would get information to help them decide as to the potential success of a package or feature.
This poll/vote could be held over weeks or months and could be further developed to allow users to make an optional donation alongside their vote to help with development. -
A successful feature is a feature that fits the need of a user. As this is the package section and we are not speaking of standard basefeatures of pfSense it's pretty up to the user to decide if he needs it or not. I'm sure there will be some packages that are not meant to be used at the firewall itself and that might not make sense on a firewall at all. Think more abstract here. Think of a "NAS-pfSense" for example utilizing samba configured by a nice webGUI interfacing with an external Radiusserver? Or think of a "VoIP-pfSense"? Just like the ftp-server package (which is marked with "use it NOT at your firewall, use it as seperate server") which is the first package of that kind. The packagesystem is kept very "open" and once it hit's a final state and gets some documentation I hope we'll see a lot of nice applications, covering firewalling and other topics.
-
I would just love to see a package with LCDproc so i can output used bandwidth, Memory and CPU usage, States and so on.
-
-
The two packages I most want are xsupplicant, and bind.
-
The two packages I most want are xsupplicant, and bind.
Hmmm, what are you trying to do with xsupplicant?
–Bill
-
I would like to see MRTG/RRDTOOL integrated, to show graphs on latency, wan/lan/wifi/dmz traffic, cpu/disk usage, etc…
Keep up the good work.
Greetings EriSan
-
I would like to see MRTG/RRDTOOL integrated, to show graphs on latency, wan/lan/wifi/dmz traffic, cpu/disk usage, etc…
Keep up the good work.
Greetings EriSan
Most of this is supported now in the pfstat package
-
I'd really love to see snort added to the packages. Squidguard would also be a nice addition.
-
I'd really love to see snort added to the packages. Squidguard would also be a nice addition.
I've already got plans on a squidGuard package once I've gotten Squid to a stable release.
Mike
-
For example IPCop is sucessful in that it has had 2.5 million downloads for the 1.4 series, however I do not think the project developers are aware just how much the addons with features such as content filtering and client side friendly VPN projects such as OpenVPN popularize the project.
To define how important /popular certain features are over other features, a whole new firewall distro endian has been developed from IPCop. Here is what it states about the features it has on the home page.
The features include a stateful packet inspection firewall, application-level proxies for variuos protocols (HTTP, POP3, SMTP) with antivirus support, virus and spamfiltering for email traffic (POP and SMTP), content filtering of Web traffic and a "hassle free" VPN solution (based on OpenVPN).
-
I'd really love to see snort added to the packages. Squidguard would also be a nice addition.
I've already got plans on a squidGuard package once I've gotten Squid to a stable release.
Mike
Mike,
I am really looking forward to that!! Great work so far I love Pfsense, such a great idea!!! ;D
-
I'm really looking forward to the squidGuard package too, once squid is stable
- 15 days later
-
I don't know if you guys know hamachi (http://www.hamachi.cc) I have a virtual network card for it in my linux box and I love it, I can always "call home" from anywere I am.
Having a virtual Hamachi interface on a pfSense box would be totally great! -
This looks interesting, I'll have a look at it. Seems it's for linux though, so it might need some porting.