Packages wishlist?
-
PassiveDNS
Something like this: https://github.com/gamelinux/passivedns
I find the idea so simple, the potential quite big.
-
ZNC for 2.4.X
-
Been mentioned before - some time ago I believe - Webdav package. - Great for IoT devices.
-
Package for CUDA installation and compile Suricata with support CUDA.
This will allow even an inexpensive video card to increase the performance without increasing processor power -
- bacula client
- icinga2 client (yes I know there is nrpe)
Bacula / If you install a soft mirror of two SSDs as RAID1 and one disk is failing you could easy swap it over
and rebuild the system, and during that phasis the second or slave unit from your pfSense HA cluster will do
the entire job within.Incinga2/ Is a monitoring software and works great together with MySQL on FreeBSD and yes Netgate is
also offering little small computer units such the MinnowTrurbot that you are able to run it there with ease!
Alternately I can say a small unit with CACTI & MRTG will do this job well too! Or did you hear about ELK?
ELK, ElasticSearch, Logstash & Kibana It is more to you to write code to get flavor working sensors on
your Incinga2 platform then a packet in pfSense.it would be great to get Ufdbguard as a package for Pfsense.
Is there a way I can contribute / facilate with that request?Please have a look at their pricing list and ask them to do this job it self, based on the commercial
concern it should be in their interest first! Price listPassiveDNS
Would be nice to see how it works on a firewall.
ZNC for 2.4.X
This is not an IRC bouncer or?
Been mentioned before - some time ago I believe - Webdav package. - Great for IoT devices.
Is this not more for NAS devices available as a packet?
Package for CUDA installation and compile Suricata with support CUDA.
Would be Intel Xeon Phi, Intels QuickAssist or DPDK matching better to snort or suricata?
Or a small miniPCIe or PCIe card with an ASIC or FPGA likes the Xilinx Spartan 6 on it? -
I have seen some post about Samba and NTLM for Squid, but I would also like to see Samba included for ntlm_auth in FreeRADIUS 3.x for PEAP authentication against Active Directory.
http://wiki.freeradius.org/guide/freeradius-active-directory-integration-howto
-
+1 for privoxy
-
My wish is very simple . . . fail2ban or equivalent. Where I could setup arguments to scan the logs and modify firewall rules based off those.
Currently running fail2ban on many downstream devices paired with IPtables and it works great. It would be nice to have the package scan remote logs as well; for instance, scan Apache logs and make changes at the firewall when an attack is happening.
+1 for this as well I think this is a really good idea.
-
Updated Postfix please :)
- 1 for this
- 1 for this too
+1 for this as well as instructions for a backup MX
-
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 ;)
Could you share how you did this because I currently run fail2ban on my sme server, but am interested in setting up a backup mx and thought I could do it with pfsense, but your way doesn't seem too bad especially being you are passing the rules to pfsense.
-
I would like to see an MQTT broker like https://mosquitto.org/ (sonething that handles local MQTT) available in pfSense.
Reason is that there are many scenarios where IOT devices need to be run locally and not in the cloud.
I am currently working on such a product.
Currently we need the consumer to buy a Micro Appliance device running pfSense and then a separate hub to manage MQTT. But MQTT is all about packets, security and network management so putting this on the pfSense device means one less device to manage and better packaging and safety for the consumer.
-
The big ones for me are:
privoxy - a configurable http proxy - ad blocker
tor - needs no expl.
dante - a SOCKS proxy
I have compiled this on a ubuntu box with proxHTTPS proxy
This means it can filter https sites, and use onion network
But there is a but :)
As firefox can use it`s own proxy it is easy to point to the box,but for the whole network to redirect traffic to that box (80,443) i can not figure out (eighter by NAT or by squid (external) -
Hi all,
I don't know if it was already mentioned before, but I just realized something is missing.
This should be a package, or be build into pfSense :
-
Do nothing (the default).
-
Notify in the GUI and/or by mail the presence of an upgrade of an installed package.
-
Or, why not : a notification a not-installed package has been upgraded.
-
And while where at it : a notification a new package is made available - or a package was removed.
Probably some support on the other side will be needed - the presence of a xml file with the current state of all package, maintained by the "pfSense build engine".
The first two possibilities could be handled by pfSense right now, as it actually already does : the Packages widget does a good job although not very visible (the yellow marker). -
-
Hi,
+1 for mqtt broker
and:
For kvm virtualised pfSenselike we have in Open-VM-Tools for VmWare: (debian package Name): qemu-guest-agent
Markus
-
@tdi:
Filebeat - https://www.elastic.co/products/beats/filebeat.
Anyone working on this?
@tdi:
Filebeat - https://www.elastic.co/products/beats/filebeat.
Anyone working on this?
I though at one time that I wanted this too.
Just now getting back to working on my Elk stack, and I'm not really sure what it would do for us that syslog-ng won't do already, as syslog-ng answers the issues of udp transport by offering tcp.
We still have to parse the log entries to put them into a form we find useful.
Was there some other factor I'm now forgetting?
Another vote for Filebeat.
Need it to ship the Snort log file to my ELK machine..
I would like to see filebeat as well. There is a FreeBSD package for filebeat that can be installed however having an approved package with GUI configuration options would be superior and could be backed up using the built-in backup feature.
For integrating with ELK filebeat is suprior to trying to make syslog properly output to logstash and filter everything. Additionally using TCP and monitoring specified files we know that everything is properly captured and shipped to our collector.
-
ClamAV is on 0.99.2 there is already 0.99.4 and 1.00 that seems a whole lot better. shouldn't upgrading the engine be a priority security update?
-
I'd like to see this as well.
-
Hi all!
Security: I wish to see way less bruteforce attacks on my systems.
Automatic blacklisting of IP's hitting on an expressely opened set of standard ports that are really not belonging to our protected systems rather are specifical bait to the standard port scanners.
I believe this is the concept of Honeypot and Guerrilla package seems to do that just fine just it isn't integrated in pfSense.
Any implementation of such a smart system on pfSense (of course automatically freeing up ports present in rules)?
Best
-
WireGuard VPN
It was freshly ported to FreeBSD in may 2018.
Better performance than OpenVPN and easy to configure.
https://www.wireguard.com/
https://www.freshports.org/net/wireguard/
https://lists.freebsd.org/pipermail/freebsd-ports/2018-May/113434.html -
@juppin said in Packages wishlist?:
WireGuard VPN
It was freshly ported to FreeBSD in may 2018.
Better performance than OpenVPN and easy to configure.
This does not inspire confidence:
About The Project
Work in ProgressWireGuard is not yet complete. You should not rely on this code. It has not undergone proper degrees of security auditing and the protocol is still subject to change. We're working toward a stable 1.0 release, but that time has not yet come. There are experimental snapshots tagged with "0.0.YYYYMMDD", but these should not be considered real releases and they may contain security vulnerabilities (which would not be eligible for CVEs, since this is pre-release snapshot software). If you are packaging WireGuard, you must keep up to date with the snapshots.
However, if you're interested in helping out, we could really use your help and we readily welcome any form of feedback and review. There's currently quite a bit of work to do on the project todo list, and the more folks testing this out, the better.
So maybe in the future when it's stable and proven to be secure. Performance means very little if it is insecure.
