Packages wishlist?

[eri--]

Well first that code is wrong there now is get_configured_interface_list() or get_configured_interface_with_descr() as you can see we are pushing 1.3 to have APIs to facilitate most of things.
Form the interface list to the other infos.

Bascially you do not eneed any info about freebsd to create a package just know the application you are packagizing :). But i will try adding some docs for that.

[Perry]

Well first that code is wrong there now is get_configured_interface_list() or get_configured_interface_with_descr() as you can see we are pushing 1.3 to have APIs to facilitate most of things.
Form the interface list to the other infos.

Hehe Then it should be corrected in status_interfaces.php  ;D

[eri--]

Where are you reading this?

[Perry]

ok my mistake, that was 1.2.1 not 1.3 as i thought.

[stechnique]

From a semi-outsider's viewpoint, I do think some developer doc and an up-to-date API would be a HUGE plus for the project.
I've been using pf for over 2 years on several projects, and although I don't have a lot of time on my hands, I happen to be an experienced PHP programmer, and I do think I could contribute to the project with some basic doc like that.
It would take me 2 weeks now to read through the source and figure out the structure you are using, the guidelines you follow, the functions that are available, etc. With some basic how-to and a reference API, I could be up and running in a few hours, and I'd have a quick reference API (which is a must for any project).
If you slow down on the coding and take some time to invest on documentation, you will see coding will pickup by itself afterward with more contributors and more efficient development.

Just my 0.02$.

[vendetta]

@ermal:

Since there are so many request for different things i want just to ask a simple question:

Will detailed docs on making a package bring more patches/packages developed by the requesters?
I might throw some time to making a detailed doc on how to create a package for pfSense if i see some interest from people.

Absolutely.

[thekod]

@vendetta:

@ermal:

Since there are so many request for different things i want just to ask a simple question:

Will detailed docs on making a package bring more patches/packages developed by the requesters?
I might throw some time to making a detailed doc on how to create a package for pfSense if i see some interest from people.

Absolutely.

Again, ditto.  I've been screwing around with some of the inc's and xml's in the packages I've installed, which is cool and all, but the package system is slightly arcane, and I would be far more likely to actually create a package if there were some kind of package docs than currently…turns out, the current situation is likely enough since I'm going to create a package, but that's beside the point.  :)

[hinze57]

Doc(s) on how to build packages would be awesome.  I am REALLY wanting to build the bits for installing Dansguardian on pfsense.

[ToxIcon]

SpamAssassin

PGP encryption

keystroke encryption

bot/mailware/trojan/scanner

keyloger protection

[AudiAddict]

I would love to see a cacti package, it shouldn't be that hard to do.. it's just that I don't have any unix/freebsd knowledge.

The current RDD graphs can only be seen after logging in, I would love to place some graphs on our intranet page for our users to see. Cacti should allow us to do this and also provide more graphing options.

[josey]

Radius server, not radius protocol, radius server  ;D

[thinair]

ntop, again :)

[ToxIcon]

adzapper

[sloan]

Maybe we should start a new thread and ask which packages people would like to run on pfSense in appliance mode.      Since we have the ability to run pfsense with one NIC and no NAT there may be more interesting requests.

Here is the link in case someone would like to read about the variety of appliance uses for pfsense.

http://www.pfsense.org/index.php?option=com_content&task=view&id=71&Itemid=81

Wireless Access Point

VPN Appliance

Sniffer Appliance

DHCP Server Appliance

DNS Server Appliance

Voice over IP (VoIP) Appliance

With the nice package manager and active user base I bet there are more good ideas out there.   I have read in other threads some people mention file sharing.  That was discarded by some saying its a firewall you don't want to run samba on it.

Now it seems pfsense is an appliance also.

[cybrsrfr]

Appliance ideas:

Database Server (with replication)
Web Server
Streaming Music Server
Streaming Video Server
Email Server
Dev Server (options for CVS, SVN, GIT, wiki)
Mirror Client and Server
Session Border Controller

[swmspam]

Some of these Appliance ideas are incorporated into FreeNAS, a related fork of m0n0wall.

I still haven't found the webserver solution I've been looking for. I want an embedded OS to run a webserver, with the /www/doc/ directory on a USB stick (diskless system). FreeNAS will do this just fine, but doesn't have per-directory authentication.

[freebee]

Here we go…
Postfix + Davecot POP server + procmail + blockmail.pl + spam assassin + clamav or other antivirus.
A complete client / server mail.
Connect to a mail server, recieve e-mails, scan for virus, use procmail + blockmail to police what is coming from (copy or not to another e-mail local account) and store in server.
In Lan , users can push the e-mail stored in server.
For send e-mail, listed users that can send and a option to copy to other mail what is sended, scan for virus, block attachments, add to e-mail body the message warning about audit.
I can help with commands or manually configure. A gui for that inside pfsense, would be very very good.

[agent_linux]

How about Nagios? Im looking forward to have it on my pfsense box.

[choup]

First, I would think it would be best to get the core elements 100% stable. Then get add-on packages like Squid Proxy, SquidGuard, IDS… working as stable as possible.

I would definitely like to help out schools that can't afford a lot for technology on pfSense But problems with SquidGuard puts a serious damper on that. See Google SafeSearch bug in the forum. Simple problems liek this can seriously limit utilization of pfSense.

I have two schools right now that need something like pfSense. I have to corporate donated hardware, just can't get the software that works.

Charlie

[tester_02]

1  - Peerguardian style package.  Something to block out those bad ip's ;)  Needs to have peerguardian style auto update blocklists.  To me this is a big priority as there is not much for 64 bit windows support for this style of program.  Having this feature at the router makes the most sense anyways.

2 - email.  it actually would be nice to have an email appliance with webmail.    I'm looking at clarkconnect, but only for the email functionality, as the rest is defiantly lacking compared to pfsense.

It's hard to really ask for much more.