Packages wishlist?
-
-
+1 for privoxy
-
+1 for ntopng
-
ZFS by default
-
Package to setup mounted USB disk as a ZFS device, copy / backup the current system across so you can reboot from it, then back that up to your internal drive (i.e. simple UFS -> conversion!)
-
Wireless AC 1300 drivers would be amazing but I know thats a big ask
-
Ability to serve simple static webpages from an archive or git checkout using nginx (useful for internal bookmarks for staff etc…)
-
A page that shows your detected hardware and highlights any items that may have potential problems
-
Much better traffic shaping wizard (badly needed, not really a package though)
-
Proper vim package (that supports backspace etc…)
-
htop package
-
fail2ban
-
ipsec wizard package
-
BareOS
-
-
I would like to have arpwatch back. Is there anyone who could convert it to bootstrap?
-
My request is that add in the available packages samba 4 or which is newest version.
I think many people will be glad if this package can install and configurate via webgui. -
I would like to see a package for installing UniFi controller like in this project https://github.com/gozoinks/unifi-pfsense
I don’t know what the project owner is planning, maybe he needs some help and support, but I’m not able to do so. I wrote a little feedback with some ideas
I used your script to install unifi 5.0.8 into my pfSense 2.3.1_p5. Had to modify the download URL. It would be nice to see a pfSense package. I think it would be a good idea to separate the install script from the unifi software so it can be used whenever unifi changes the software.
What do you think about having your script integrated in the pfSense GUI maybe under the Service menu? From this UniFi Service menu it would be possible to install or update the controller software with all its dependencies as the script does now. But it will not download the controller software by itself. The user has to download it first from the UBNT site to his local computer. Then he choose the downloaded zip file to upload it to the pfSense. Also within the Service menu it will be possible to start or stop the controller, of course its status will be shown on the dashboard of pfSense.and get this answer
Thank you for the feedback.
A proper pfSense package was the original intention of the project, but I struggled with the requirement that the package include all binaries. Since this project requires software from Ubiquiti that we can't redistribute ourselves, I stalled on that.
At least, that was the case with <2.2. Now that 2.3 and later are using a different approach to packaging, that restriction may no longer be present. However, I have not dug into it all to figure out how best to proceed.
Consider bringing this up as an issue on the repository. I'd love to continue the discussion there, in case someone else sees an easier path forward. Feel free to contribute yourself as well!
Maybe someone here is willing to help this project going on.
-
The restriction is still the same: that software can't be redistributed as a package.
-
With my idea the package does not have to redistribute the software. The package would only install the dependencies and and gives a GUI to enter the URL of the software. I don’t think that would be a problem. Or am I wrong?
-
@ Admin?
Is there anyway to bring back MailScanner?
and is there a way to use 3rd party AV with pfsense?
-
Filebeat - https://www.elastic.co/products/beats/filebeat.
Anyone working on this?
-
bacula-client so I can back up my configuration
We once had it.
-
SAMBA!!
-
Oauth2 proxy for Captive Portal:
A reverse proxy that provides authentication with Google, Github or other provider
https://github.com/bitly/oauth2_proxy
-
Please, add allow or deny MAC Address on pfSense+Proxy Server.
Thank you.
-
I miss BandwidthD :'(
-
Updated Postfix please :)
-
-
Samba.
-
Oauth2 proxy for Captive Portal:
A reverse proxy that provides authentication with Google, Github or other provider
https://github.com/bitly/oauth2_proxy
+1
-
-
An updated postfix package isn't going to happen. That was announced on GitHub.
What I resorted to was creating a new FreeBSD VM and installing postfix on that - as suggested in the postfix thread.
When that was working I put fail2ban on there as well. I'd often thought about using those two together. fail2ban updated a local pf table to block the spammers but I wasn't happy with the spammers getting past pfSense to the postfix/fail2ban server.
Then I found that I could have fail2ban call OpenBGPD to update an alias table on pfSense. A feedback loop. Who knows why the authors of OpenBGPD put that feature in but I'm sure glad they did.
In the end it's a better solution than postfix on pfSense but it was far from a trivial exercise for me ;)
-
Would love to have DNSCrypt.
Thanks!!!!!
