1. Home
  2. pfSense Packages

Subcategories

  • Discussions about packages which handle caching and proxy functions such as squid, lightsquid, squidGuard, etc.

    4k Topics
    21k Posts
    JonathanLeeJ
    @firefox I don’t think so, to be honest with you I am on an older version also. Just make sure you do the patch package and install all the system patches.

  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    M
    Hi, I had a problem with my home network today, so I checked pfsense and discovered that suricata had blocked the wan ip. After some tests and triggering some suricata alerts, the wan ip was blocked. I restarted pfsense and ran some more tests, but the problem no longer occurred. I then checked the wan interface settings and indeed the ip list does not include the wan ip, both now that it's working and before, when it was blocked. I'm using pfsense 2.8.0 and suricata 7.0.8_2. I use PPPoE to access the Internet.

  • Discussions about packages that handle bandwidth and network traffic monitoring functions such as bandwidtd, ntopng, etc.

    571 Topics
    3k Posts
    dennypageD
    @Leon-Straathof Data retention settings are handled inside of ntopng. Documentation here. Pay attention to the RRD note. Also, if you've turned on some of the slice and dice time series information (is off by default), I'd suggest turning them back off. These balloon the storage requirements and are of little actual use.

  • Discussions about the pfBlockerNG package

    3k Topics
    20k Posts
    keyserK
    @jrey said in pfBlockerNG syslog logentries to remote SIEM: @keyser I so want to answer this, but then at the same time (no I don't) ... pfblocker using syslog messaging in real time. no tailing of files, no other packages, just code. Huuuh? That seems very very interesting I noticed your name in other posts around the forum where you seemed to be QUITE proficient at coding/developing. Are you by any chance considering involvement in developing and refining the pfBlockerNG package? It would be SO great if you are looking into adding native syslog to the pfBlockerNG package - or an easy workaround that does not require additional packages and “temporary” edits in files that does not survive service restarts or pfSense updates. Here’s that you will fill me/us in on the solution you are using to your Greylog - please, pretty please with sugar on top

  • Discussions about Network UPS Tools and APCUPSD packages for pfSense

    101 Topics
    2k Posts
    dennypageD
    @jhg said in NUT fails to start after 2.7.2 -> 2.8.0 upgrade: Interesting. I would have thought the initial reboot, which occurred as part of the upgrade, would have done the trick, but it took a second reboot, just now, to get things working. Glad you have it sorted. There was no difference in the output of usbconfig show_ifdrv at any point -- before or after unplugging/replugging the USB cable, nor after rebooting. ... Question: What would tell me whether or not a driver was loaded? If there were an attached driver, it should have shown up with the show_ifdrv command. If you use the command and look at the other usb devices, I think they will show attached drivers. I don't expect to see a driver attached to the ups, because there is a quirk that tells the OS to ignore that device (and not attach a driver). Look for idVendor and idProduct in the above output. The Vendor ID for your device is 0764, which corresponds to Cyber Power Systems, and the Product ID for your device is 0601, which is registered as "PR1500LCDRT2U UPS" (don't sweat an exact match for the name). You can see the quirk with the following command: [25.07-RC][root@fw]/root: usbconfig dump_device_quirks | grep 0764 VID=0x0764 PID=0x0005 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_HID_IGNORE VID=0x0764 PID=0x0501 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_HID_IGNORE VID=0x0764 PID=0x0601 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_HID_IGNORE [25.07-RC][root@fw]/root: Your device is third on the list. The HID_IGNORE quirk says to ignore the device and not attach a driver. @jhg said in NUT fails to start after 2.7.2 -> 2.8.0 upgrade: You might consider adding this resolution to the release notes for 2.8. LOL... sorry, I don't have input to the release notes (I don't work here). While I wrote and maintain various packages, including NUT, I'm still just a volunteer. Most packages are actually written by volunteers.

  • Discussions about the ACME / Let’s Encrypt package for pfSense

    496 Topics
    3k Posts
    R
    @provels said in updating to acme 1.0 breaks system beyond repair: need to restore from backup: This same mess happened to me, even w/o Acme, going from 25.07 to *.1. Blew, reinstalled w/ Crowdsec, blew again, reinstalled, clipped all the Crowdsec info from config.xml, restored config, back to normal. Crowdsec is a great concept, but I think I'm out. I never had this issue with Crowdec before the ACME update, even with updating from 2.7 to 2.8 there was no issues. In fact after restoring from a backup after the ACME update, Crowdsec reinstalled just fine, and this was before the recent release a couple days ago that contained a fix.

  • Discussions about the FRR Dynamic Routing package on pfSense

    294 Topics
    1k Posts
    yon 0Y
    said in Please update frr on Pfsense+ to FRR 10.3: https://redmine.pfsense.org/issues/15785 now frr 10.4.1

  • Discussions about the Tailscale package

    90 Topics
    606 Posts
    M
    @yobyot I've SSHed into pfsense and for the sake of testing I've simply run the command: tailscale up --auth-key=tskey-client-kQ_THE_REST_IS_A_SECRET\?preauthorized=true\&ephemeral=false --accept-dns=false --accept-routes --advertise-exit-node --advertise-routes=X.X.X.X/24 --advertise-tags=tag:pfsense Note the preauthorized=true and ephemeral=false I gave this key all permissions (temporarly as I just wanted to verify it's working) of course I had to register the tag used also in the ACL tags pane: https://login.tailscale.com/admin/acls/visual/tags so far so good

  • Discussions about WireGuard

    697 Topics
    4k Posts
    lvrmscL
    I took some days before reporting again... Since then I installed: 25.07.1-RELEASE (amd64) built on Fri Aug 15 20:42:00 CEST 2025, and the issue re-appeared but did not (yet) clear by itself. Wireguard works well, that system has only one tunnel with another site, using interface assigned mode. I depend on it, and it works flawlessly. Yet the wireguard configuration page, its status page as well as the services widget on the dashboard, all report the Wireguard service as stopped, with the usual icon to start it. On the dashboard the gateways widget shows Pending for the IPv4 and IPv6 wireguard gateways. On the other hand, and it is logical as the packets do flow through the tunnel, the Wireguard widget on the dashboard shows the tunnel up with traffic. To be complete, the watchdog service, if wireguard is configured there, spend its life at detecting wireguard stopped and attempting to start it, which does not work. The other side of the tunnel is still on 25.07-RELEASE (amd64). I'm reluctant to upgrade that side too, with fear to loose the wireguard tunnel altogether. Aren't there any logs from that wireguard package? I can't find anything of that kind.
Log in to post
Load new posts
  • J

    Can't install openvpn-client-export on 2.3.1

    3
    0 Votes
    3 Posts
    2k Views
    jimpJ
    "No address record" definitely indicates a lack of working DNS. It could also be a lack of upstream connectivity, but DNS being incorrectly configured is more likely.
  • A

    PfSense-pkg-freeradius2 installation failed! No address record

    4
    0 Votes
    4 Posts
    3k Views
    A
    @cmb: That means your system can't resolve DNS. You were right, after disabling NAT it'S working.
  • X

    [Solved] 2.3.1 upgrade really botched my nagios monitoring config. :-(

    2
    0 Votes
    2 Posts
    1k Views
    X
    Well, since I have backups of everything anyway, I decided to hack at it… I first removed the new "NRPE" package.  My plan was to go in and hand-edit the XML file after that to remove any traces of NRPE/NRPEv2, then restore it, then re-install the new NRPE package, and then if possible copy-paste the relevant part of the config back from my NRPEv2 configuration, and if not, go in and re-enter everything via the gui (ugh.) However, simply removing the NRPE package actually cleared up the broken NRPEv2 menu items. I then backed up and hand-edited the XML file. The only thing related to NRPE that I could still see remaining in the XML file (other than firewall rules I had created) was the orphaned configuration for the NRPEv2 service (exactly the part that I wanted to try to save), specifically: pfsense -> installedpackages -> nrpe2 -> config So I carefully cut the "nrpe2" and below branch out of the XML file and reloaded it. Then I reinstalled the NRPE package using the package manager. Then I backed up the XML file and took a look at it again to see what changes it had made. I discovered that the new NRPE package actually uses the same "nrpe2" stanza in the config file (so I'm not sure why it wasn't working before), specifically, pfsense -> installedpackages -> nrpe2 -> config. So this time I replaced that branch of the XML with the one I had backed up previously, saved and rebooted yet again, and now everything seems to be back to normal. So it must have actually been something else somewhere else in the XML that was gummed up, which installing, removing, and then reinstalling the NRPE package fixed. Sigh. Interestingly, the new NRPE package actually is referred to as "NRPEv2" in the menus and such, so... shrug. I have no idea why all this happened. It seems to me that even if the package were removed and then later reinstalled, that the XML wouldn't get all bungled up like this. Annoying to have to go to this much work to clean up after an update, but at least my router is working again!
  • E

    NRPE v2 for pfSense 2.2 missing on my hardware?

    2
    0 Votes
    2 Posts
    730 Views
    jimpJ
    You have to pass the pfSense package name for that on the command line, so: pfSsh.php playback installpkg "NRPE v2" But your real problem is that you are many versions behind. The package requires a minimum of 2.2.1, and you should be running at least 2.2.6, if not 2.3.1_1.
  • E

    Mailscanner Once 2.3 is out it will work again.

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • J

    How to install a patched version of a pacakge

    1
    0 Votes
    1 Posts
    707 Views
    No one has replied
  • C

    2.3.1 NUT won't start

    3
    0 Votes
    3 Posts
    2k Views
    C
    Thanks man. That worked perfectly. I thought I was looking at currrent docs on this but I must have pulled up some old driver to ups matrix. http://networkupstools.org/stable-hcl.html
  • Z

    Pkg installation failed!

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • C

    Broken packages NUT ,bandwidthd from old version remain on web gui menu

    4
    0 Votes
    4 Posts
    2k Views
    D
    I started my own thread seeking guidance. As I stated here, I didn't want to jack your thread fearing we had separate problems. Anyway, see my thread - I solved my problem myself and possibly this will be a solution for you. https://forum.pfsense.org/index.php?topic=112565.msg626507#msg626507 *NOTE - I took a guess and was successful. My method was via a reinstall after having made backups of the config. You should be able to just upload and restore an edited config file. Another thing . I am not sure if it matters when restoring or how it may/may not affect us and our package problems but I made 4 different types of backups (just in case a different kind was easier or better for solving this problem). 1 with everything, 1 without RRD DATA, 1 without packages and one without anything except bare bones config. These are the possibilities under the BACKUP menu via check box options. Even more, I also had an error message upon restoring to my edited backup that there was duplicate blah blah at lines 3356 or something. I simply edited the config file, removed the duplicate lines then restored again and all was well. It sounds complex but it was all simple and common sense based. I was done in 20 minutes or less and I am an amateur when it comes to pfSense and almost clueless with *BSD. Hope I've helped you.
  • R

    Squid AD authentication problem

    1
    0 Votes
    1 Posts
    993 Views
    No one has replied
  • D

    Shalla blacklist will not install/download

    3
    0 Votes
    3 Posts
    2k Views
    D
    Kom, I verified the unit was capable of squid.  After searching everywhere I could, I contacted the pfsense store in hopes they could help without burning one of my support tickets. The really nice guy replied, after I gave a digest of my tale of woe,,, stating mozilla firefox sometimes will prevent the shalla list from downloading/installing. I did a factory restore (in an effort to wipe out any mistakes I may have made, installed squid and squidguard, and did the configuration in chrome.  Success!!! the blacklist downloaded and saved, and my test of blocking gambling/dating/fortunes/porn as well as allowing a few others worked splendidly.  I did need to remember to click the green "Apply" button on the general tab of squidguard for the settings to take hold. What a journey for my first day with pfsense! I hope this will help others who have experienced my frustrations with this portion of configuration
  • H

    Barnyard2

    1
    0 Votes
    1 Posts
    617 Views
    No one has replied
  • H

    Using 3rd party antivirus

    4
    0 Votes
    4 Posts
    2k Views
    K
    As far as I know there are no up to date commercial AV products for FreeBSD. There was one such product by Kapersky but it's been abandonware for years: http://www.kaspersky.com/about/news/product/2005/Kaspersky_Lab_begins_beta_testing_of_three_new_versions_of_Kaspersky_Anti_Virus_for_Linux_FreeBSD_and_OpenBSD
  • D

    NUT help please

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • D

    Alternative to AutoConfigBackup?

    2
    0 Votes
    2 Posts
    883 Views
    B
    For us poor people ;) https://github.com/KoenZomers/pfSenseBackup I recommend that you create a new (backup)user that only has the necessary privileges to create a backup.
  • F

    Squid reverse proxy quandry

    1
    0 Votes
    1 Posts
    683 Views
    No one has replied
  • R

    PKG via Proxy slightly broken?

    2
    0 Votes
    2 Posts
    730 Views
    jimpJ
    There are a few threads about this, but it should be fine once you get to 2.3.1, we put in a fix for pkg and proxies there.
  • S

    Failing to install the packages.

    3
    0 Votes
    3 Posts
    1k Views
    G
    I wanted to delete it but a reinstall did this Installing pfSense-pkg-squidGuard… Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. Checking integrity... done (0 conflicting) The following 7 package(s) will be affected (of 0 checked): New packages to be INSTALLED: pfSense-pkg-squidGuard: 1.14_3 [pfSense] squidGuard: 1.4_15 [pfSense] db5: 5.3.28_3 [pfSense] squid: 3.5.19 [pfSense] krb5: 1.14.1 [pfSense] pkgconf: 0.9.12_1 [pfSense] cyrus-sasl: 2.1.26_12 [pfSense] The process will require 29 MiB more space. [1/7] Installing pkgconf-0.9.12_1… [1/7] Extracting pkgconf-0.9.12_1: ….... done [2/7] Installing krb5-1.14.1… [2/7] Extracting krb5-1.14.1: …....... done [3/7] Installing cyrus-sasl-2.1.26_12… *** Updated user `cyrus'. [3/7] Extracting cyrus-sasl-2.1.26_12: …....... done [4/7] Installing db5-5.3.28_3… [4/7] Extracting db5-5.3.28_3: …....... done [5/7] Installing squid-3.5.19… ===> Creating users and/or groups. Using existing group 'squid'. Using existing user 'squid'. ===> Pre-installation configuration for squid-3.5.19 [5/7] Extracting squid-3.5.19: …...... pkg: cannot rename //usr/local/etc/squid/errors/zh-cn.NyXZdUVRExqV to //usr/local/etc/squid/errors/zh-cn: Is a directory [5/7] Extracting squid-3.5.19… done [5/7] Deleting files for squid-3.5.19: …....... done Failed bzzzzzzzzzzzzzzzt      :o
  • J

    NUT blazer_usb

    4
    0 Votes
    4 Posts
    4k Views
    T
    Try setting it to APC Back-UPS USB It works for me with a CyberPower UPS…
  • C

    2.3.1 - What happened to Packages?

    2
    0 Votes
    2 Posts
    1k Views
    C
    That's getting into things that are potentially risky at breaking other parts of the system. bhyve is available to run VMs. 'pkg install vm-bhyve' for a management framework for it.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.