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
    N
    @andrew_cb That’s a good news. Will this fix find his way also on the community edition? I’m asking because I am on pfsense ce 2.8.0

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

    2k Topics
    16k Posts
    bmeeksB
    @NRgia said in Suricata on Pfsense: @bmeeks Thank you for what you did for Snort or Suricata. I'm not sure what you want me to do on Redmine, due to is a bug tracker. My question is for Product Management, which I will ask it here to be public: What is the plan for these 2 packages, Suricata and Snort? Thank you Yes, Redmine is for both bug reports and feature requests. Asking for the Suricata binary to be updated to the latest 7.0.11 version from upstream is a legitimate Redmine request. I would suggest simply asking for the binary version update instead of asking about future Netgate strategy (such as the support plans for the packages). Strategy discussions typically don't get very far because they deal with proprietary information or plans that a company may not want to publicly discuss. Redmine is where the Netgate developer team tracks all the code changes they make for pfSense. They will see Redmine reports much quicker than a forum post.

  • 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
    GertjanG
    @jeremyc311 said in pfBlockerNG-devel 3.2.8 service pfb_dnsbl don't start: I’m surprised to see in my logs only one blocked IP, which is related to my TrueNAS I'll decode this one : @jeremyc311 said in pfBlockerNG-devel 3.2.8 service pfb_dnsbl don't start: Aug 5 09:01:14,1770008712,bxe1,LAN,block,4,17,UDP,192.168.2.13,116.147.64.181,51765,51413,out,Unk,pfB_PRI1_v4,116.146.0.0/15,ET_Block_v4,Unknown,truenasr740,null,+ Traffic, coming into LAN, from a LAN device (192.168.2.13 = your TrueNAS) going to a Chinise ( 116.147.64.181 ) Brazilian ( 177.72.195.114 - = next line ) was blocked by the "pfB_PRI1_v4" list. That's probably good thing ? ( ! ). Up to you to discover why your NAS should initiate connections to these countries. A NAS can go outside for maintenance purposes, for example to look for updates of it's system. These could be located anywhere of course. The GeoIP IP created a rule for you. How and where do you use that this rule ?

  • 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

    494 Topics
    3k Posts
    johnpozJ
    @jimp Just updated acme package to v1, and did a renew of certs even though they were not do for a while. All went fine, using dns-cloudflare [image: 1755031470221-updated.jpg] On 25.07 of pfsense+

  • 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
    595 Posts
    E
    Updated CE 2.7.2 to 1.86.2_1 Changelog pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/latest/All/tailscale-1.86.2_1.pkg Freshports

  • Discussions about WireGuard

    693 Topics
    4k Posts
    lvrmscL
    Since my upgrade to 25.07-RELEASE (amd64) built on Tue Jul 22 22:24:00 CEST 2025 FreeBSD 15.0-CURRENT, on one end of my most important tunnel, the tunnel still works fine, but the pfSense GUI keeps reporting the service as stopped. I had to remove its monitoring from the Service Watchdog which was also trying to start it, without success. Yet the trafic flows correctly. I'm holding off upgrading my other boxes. Is there something I could do to help diagnose?
Log in to post
Load new posts
  • W

    DNS Error updating packages

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

    HAProxy broke after update to pfs 22.05

    4
    0 Votes
    4 Posts
    3k Views
    S
    i had this issue, solved it after changing "httpforclose" to "httpclose" as the new version doesn't support that old config var, perhaps dev can do some some parsing magic? lucky the error code lead me to this
  • F

    This topic is deleted!

    1
    0 Votes
    1 Posts
    11 Views
    No one has replied
  • B

    How does cron service get restarted ?

    3
    0 Votes
    3 Posts
    625 Views
    B
    @Gertjan For some reason, I wrongly assumed that cron would only read the crontab file when the service re/started. Thanks for the explanation, and the tips for how I could check this myself next time. +1
  • B

    Snort Rule Update Settings time has a bug with the cron job

    4
    0 Votes
    4 Posts
    704 Views
    bmeeksB
    A package update containing the fix for this bug is building and should show up for users shortly. The new Snort package containing this bug fix is 4.1.6_9.
  • BlueCoffeeB

    Snort fails to install.

    36
    0 Votes
    36 Posts
    3k Views
    bmeeksB
    @BlueCoffee said in Snort fails to install.: got the new box and all is well guess the other one was bad. Ive installed Suricata (looks alot like snort) Would you set this up on lan also? Do you know where I can read more about the setup? don't want to not have it set correct this time around. You can find several Sticky Posts at the top of the IDS/IPS sub-forum here: https://forum.netgate.com/category/53/ids-ips. As with Snort, I recommend putting Suricata only on internal interfaces (LAN, DMZ, etc.). The only time I would veer from this approach is on a box with very limited RAM and/or CPU horsepower and I had a fairly large rule set enabled. That might be a point where you conserve RAM and CPU by just putting a single instance on the WAN instead of several instances on internal interfaces. But you will have the limitations I mentioned in my earlier post. Best practice would dictate that the different interfaces on a firewall likely will need different IDS/IPS rules enabled. Rules should be tailored to the unique vulnerabilities and threats present on the protected network. So, in that scenario, individual IDS/IPS instances on internal interfaces works better (if you have the necessary RAM and CPU power). As you noticed, Suricata and Snort have an almost identical GUI. That's because a ton of the Suricata PHP GUI code was a copy and paste from the Snort GUI. Any basic set up instructions you find for Snort on pfSense will also apply to Suricata on pfSense. One key difference is that Suricata does not use Preprocessors in the way that Snort does. Suricata just works differently internally. The preprocessors were a way for Snort to add new features over the years. Suricata accomplishes that a bit differently internally, so no need for specific preprocessors. There are settings similar to the Snort preprocessor settings under the FLOW/STREAM and APP PARSERS tabs in Suricata. A big difference in the packages is the rich EVE.JSON logging system in Suricata. Initially EVE.JSON logging is disabled causing Suricata to log essentially the same way as Snort did. But if you enable EVE.JSON logging for an interface, you can capture a lot of data about network traffic and of course any alerts. Suricata can log a lot of data with EVE.JSON logging and many of the options underneath that feature enabled. Just be sure you go to the LOGS MGMT tab and enable automatic log management. The defaults you find there should be fine for an initial install. Here is a link to the official documentation: https://docs.suricata.io/en/suricata-6.0.13/.
  • R

    CloudFlared Zero Trust on PFSense

    2
    3 Votes
    2 Posts
    828 Views
    M
    @romulo-reuwsaat I also would love to see this as a package.
  • B

    How can I get this UDP relay package for casting across VLANs?

    123
    1 Votes
    123 Posts
    59k Views
    S
    Thanks to all involved in creating this. I am now able to cast to 'Google Home device/speaker groups' across VLANs, which wasn't previously possible.
  • W

    Anyone have a guide for getting Airplay working across subnets with avahi?

    15
    0 Votes
    15 Posts
    13k Views
    RUBENCH00R
    @munson Hi, I'm not saying it's wrong but in short it works like this, without creating so many rules. I allow the ITO Network to have access to the Lan Network OPT1 ect ect ect .... [image: 1692299420616-rulesiot-resized.png]
  • P

    HAProxy set up with ACME Cert and CloudFlare

    4
    0 Votes
    4 Posts
    2k Views
    M
    There is a new video, perhaps it can help you.. It was released today.
  • jimpJ

    LCDProc package version 0.11.4_2

    9
    3 Votes
    9 Posts
    2k Views
    E
    @jimp was kind enough to update the LCDProc package to include a NTP server screen georou @ GitHub originally created and we updated. Current package is 0.11.5. There is a pending update to 0.11.5_1 (screens below) that improves the display of PPS, GPS, vs GPS+PPS in certain edge cases. https://github.com/pfsense/FreeBSD-ports/commit/b3a3a4bf28ad8a50211b6775ed20011097ceeef9 If you have a PPS source, it will display either the number of satellites (GPS) or stability value (PPS). Otherwise, it will display the Active Peer Server IP address. Notes: I am by no means a NTPD algorithm expert, but I noticed if a source is marked as a valid PPS Peer "o", NTPD uses that to sync and serve time to clients regardless if there a separate Active Peer "*" used for time data. If a GPS is being used for both a PPS Peer "o"and source of time data, it will be marked as PPS Peer "o" and there will be no other Active Peers "*" marked (see screen cap below). The NTP Widget seems to display the Active Peer "*" even when the PPS Peer "o" is actually being used to sync and serve time to clients. Which source is actually served to clients can be confirmed with "ntpq -c sysinfo". If you want to see the stability value when using a GPS with PPS, you can simply set the Clock ID of the GPS source to "PPS". I intentionally did not include seconds on the display since even with the LCDProc Refresh Frequency set to 1 second, time will jump multiple seconds with each screen refresh. Not sure if there is another mechanism that would improve the refresh rate of the first row to eliminate increments of multiple seconds. Feedback welcome, subject to the limitations noted above. I happen to be using a Garmin 16X (PPS Only) and 18X (GPS+PPS). NTPD only supports one PPS source at a time, thus marks the second as False Ticker "x" https://github.com/elvisimprsntr/pfsense-ntp-gps. (WIP) [image: 1691501128729-screenshot-2023-08-08-at-9.25.04-am-resized.png] [image: 1691499425902-lcdgps.png] [image: 1691499425822-lcdpps.png] [image: 1691499425730-lcdip.png]
  • S

    Unable to Install Wazuh Agent on Pfsense+ ,Latest AMI - PKG manager breaks with installation of agent

    12
    0 Votes
    12 Posts
    7k Views
    W
    I tried to install Wazuh agent too following this article https://marcius.pro/index.php/2022/03/11/wazuh-criando-regra-no-pfsense-para-bloquear-ip-de-atacante/, and I've success on FreeBSD12/pfSense 2.6 CE. However, in FreeBSD14/ pfsense 2.7 CE or pfSense+ 23.1.1, I haven't succes. The error is code_text ```Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1 2404007936:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_05_1-main/sources/FreeBSD-src-plus-RELENG_23_05_1/crypto/openssl/ssl/statem/statem_clnt.c:1921: Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1 2404007936:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_05_1-main/sources/FreeBSD-src-plus-RELENG_23_05_1/crypto/openssl/ssl/statem/statem_clnt.c:1921: Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1 2404007936:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_05_1-main/sources/FreeBSD-src-plus-RELENG_23_05_1/crypto/openssl/ssl/statem/statem_clnt.c:1921:
  • D

    nrpe 4.1: check_icmp broken

    1
    1 Votes
    1 Posts
    475 Views
    No one has replied
  • G

    Snort isn't in time sync

    2
    0 Votes
    2 Posts
    460 Views
    bmeeksB
    Snort gets its time from the firewall system. It has no special or unique time setting.
  • N

    LLDP not starting after latest update (0.9.11_2)

    9
    0 Votes
    9 Posts
    2k Views
    dennypageD
    @Neosmith20 said in LLDP not starting after latest update (0.9.11_2): Installed packages to be DOWNGRADED: pkg: 1.19.2 -> 1.19.1_1 [pfSense] ... after that, I uninstalled lldpd, reinstalled it, and then it immediately came up. Fantastic.
  • gnitingG

    Add custom command to Service Watchdog

    1
    0 Votes
    1 Posts
    325 Views
    No one has replied
  • S

    avahi seemingly not working

    20
    0 Votes
    20 Posts
    3k Views
    RobbieTTR
    I added this rule on a VLAN to allow mDNS to work across subnets. I've had this rule in place well before recent updates though: [image: 1690485850885-2023-07-27-at-20.20.58.png] ️
  • jimpJ

    LCDProc package version 0.11.3

    Locked
    5
    0 Votes
    5 Posts
    930 Views
    jimpJ
    @fireodo said in LCDProc package version 0.11.3: @jimp said in LCDProc package version 0.11.3: I see the problem there, I have a fix ready, I'll include it in my next update sometime this week depending on how much time I have available Glad you found the culprit - anyway, there is no hurry! Thanks a lot! I just pushed the new version with the fix for this, it should be available soon. https://forum.netgate.com/topic/181790/lcdproc-package-version-0-11-4
  • aaronsshA

    FreeRADIUS MAC authentication

    15
    0 Votes
    15 Posts
    8k Views
    keyserK
    @aaronssh Well, I’m using mac-auth and my clients are entered on the MAC addresses sheet, so it does work in the right configuration. But if you are not going to use 802.1x you can just create the MAc addresses as users.
  • T

    nrpe 3.1_6 service control broken on pfSense 2.7.0

    6
    0 Votes
    6 Posts
    1k Views
    D
    seems that the service entry in config.xml is not updated automatically. on an untouched system, after update to nrpe 4.1, config.xml still looked like this: <service> <name>nrpe</name> <rcfile>nrpe3.sh</rcfile> <executable>nrpe3</executable> with this the service was not starting. after removing the "3"s I can start the service from web gui.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.