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
    D
    Retested on 24.11-RELEASE (amd64) all seems to work. So it seems right to file a bug for this issue.

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

    2k Topics
    16k Posts
    cyb3rtr0nianC
    @rlrobs Yes it’s still working fine here.

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

    571 Topics
    3k Posts
    K
    @pulsartiger The database name is vnstat.db and its location is under /var/db/vnstat. With "Backup Files/Dir" we are able to do backup or also with a cron.

  • Discussions about the pfBlockerNG package

    3k Topics
    20k Posts
    M
    I resolved this by accepting the T+Cs via https://www.maxmind.com/en/accounts/1205389/geolite2/eula

  • 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

    493 Topics
    3k Posts
    GertjanG
    @EChondo What's your pfSense version ? The instructions are shown here : [image: 1753262126227-1acdc586-cb29-4148-9e36-81ade4e5e60c-image.png] A restart of a service will start by re creating their config files. If a certificate changed, it will get included. When the process starts, it will use the new certificate. @EChondo said in Issue with ACME Certificates Refresh & Restarting HAProxy: I haven't been able to confirm if the above works(mine just renewed, don't feel like doing it again just to test), so we'll see in 60 days I guess. No need to wait x days. You can re test / renew right away, as you are 'allowed' to renew a couple (5 max ?) of times per week.

  • Discussions about the FRR Dynamic Routing package on pfSense

    294 Topics
    1k Posts
    J
    @div444 i'm finding the same - did you find a solution or did reverting fix it? Hoping there is a patch fix or something to get it working! Rather not rollback if i can avoid it

  • Discussions about the Tailscale package

    90 Topics
    578 Posts
    T
    Re: How to update to the latest Tailscale version? I am on latest released Netgate 6100 pfSense PLUS v24 ( pfSense_plus-v24_11_amd64-pfSense_plus_v24_11 ) pkg config abi FreeBSD:15:amd64 pkg -vv | grep -A 3 "pfSense:" pfSense: { url : "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_11_amd64-pfSense_plus_v24_11", enabled : yes, priority : 0, cat /usr/local/etc/pkg.conf ABI=FreeBSD:15:amd64 ALTABI=freebsd:15:x86:64 PKG_ENV { SSL_CA_CERT_FILE=/etc/ssl/netgate-ca.pem SSL_CLIENT_CERT_FILE=/usr/local/etc/pfSense/pkg/repos/pfSense-repo-0001-cert.pem SSL_CLIENT_KEY_FILE=/usr/local/etc/pfSense/pkg/repos/pfSense-repo-0001-key.pem } This firewall is obviously running on FreeBSD 15 no longer on 14. But can I use the freshports link for FreeBSD 14 amd64 quarterly which is at tailscale 1.86.2 or can I only go up to version tailscale 1.84.2_1, and need to wait until they have a version of tailscale 1.86.2 or higher for the FreeBSD 15? Would it be good enough to tell it to ignore the OSVERSION? export IGNORE_OSVERSION=yes Note: use of 14 and not 15 ? pkg add https://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/All/tailscale-1.86.2.pkg service tailscaled restart tailscale up

  • Discussions about WireGuard

    690 Topics
    4k Posts
    J
    I've read through some other posts about this, but they either didn't say whether the proposed solution worked or they were very convoluted and difficult to understand. Here is our scenario: We have 6 locations--Las Cruces (LC), Sunland Park (SP), El Paso (EP), Abilene (ABI), Fort Worth (FW), and Plano (PL). LC and ABI have software that is accessed by the other 4 locations via VPN. There are WireGuard VPNs set up between LC and those 4 locations (SP, EP, FW, PL), and ABI and those 4 locations (SP, EP, FW, PL). There is also a WireGuard VPN connection between LC and ABI. LC and ABI have 2 internet connections. SP, EP, FW, and PL each have one internet connection. If the primary internet connection goes down at either LC or ABI and failover occurs to the secondary internet connection, is there a way to set up the WireGuard VPN connections so that they also failover without purchasing some 3rd party application? Thanks.
Log in to post
Load new posts
  • X

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

    2
    0 Votes
    2 Posts
    990 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
    720 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
    706 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
    987 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
    612 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
    878 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
    680 Views
    No one has replied
  • R

    PKG via Proxy slightly broken?

    2
    0 Votes
    2 Posts
    725 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.
  • M

    Obfsproxy and SS5 packages

    2
    0 Votes
    2 Posts
    1k Views
    D
    that's a very interesting feature, any new about that ?
  • Z

    Nut package & 2.3 - will my existing config be honored?

    13
    0 Votes
    13 Posts
    3k Views
    D
    @daplumber: Mea Culpa, I too missed NUT not being ready for 2.3, so I'm currently living without it. Interestingly the hand-hacked UPS widget is still showing up on the dashboard, but obviously with no information in it. An official UPS widget as part of the NUT package would be a very-nice-to-have…  8) I can offer my APC Back-ups 550 and CyberPower 1000VA (both USB) for testing NUT builds? Yay! NUT is back and with a VERY nice widget! From 2.3.1, don't know if it was back ported. Happy UPS NUT camper again! Yes, my previous config showed up just fine and "just worked" impressive! My only enhancement request would be to monitor more than one UPS, especially remotely.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.