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 That is weird did you just try this or have you used it in the past?

  • 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
    T
    Ran into this issue today as well running on 25.07.1 with pfblockerNG-devel 3.2.7. Followed the steps outlined in this thread to edit the pfblockerng.sh file, then deleted/force reloaded all the lists, and all was well again. Thank you everyone in this thread for your your help and great instructions.

  • 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
    604 Posts
    M
    Hi all, I wanted to share that I’m also experiencing issues with Tailscale (v1.86.4) on the latest pfSense CE (v2.8.0). After either a pfSense reboot or a Tailscale service restart, my node is logged out of Tailscale — exactly as many of you have described here. It bothered me enough that I opened a support ticket with the Tailscale team. I explained the problem, included details, and linked this thread as a reference. The good news is that support responded quickly and said they’re setting up a pfSense VM to reproduce the issue. In the meantime, they suggested a workaround: “Based on the behavior described here and in the thread, it looks like the auth key used for authentication may be expiring. Since OAuth clients don’t expire, switching to an OAuth Client rather than an Auth Key might resolve this. See our docs here: https://tailscale.com/kb/1215/oauth-clients#registering-new-nodes-using-oauth-credentials I tested this, and after configuring Tailscale with OAuth, everything worked! Tailscale now stays connected and authenticated even after a reboot or service restart. That said, I did tell support that while OAuth solves the issue, it used to work out of the box with the simpler interactive login / auth key flow. Something seems to have changed on the Tailscale side, and I hope they identify and fix it. But until then, the OAuth workaround is a solid fix. I’d love to hear how it’s working for the rest of you. Anyone else try OAuth yet? Cheers

  • Discussions about WireGuard

    697 Topics
    4k Posts
    H
    I figured out the issue. I missed adding the 3rd locations Lan to the static routing. Now all is working perfect.
Log in to post
Load new posts
  • V

    Squidguard3 not working

    13
    0 Votes
    13 Posts
    3k Views
    V
    ok, I believe I found a work around. First install Squid3 Second, disable the Antivirus and hit save If you are using Transparent proxy make sure you select your proxy interface and save Once you do this Squid should fire. If you want to use Squidgaurd then you'll need to install, check your configuration and then hit download to download your block list. For some reason squidguard won't fire if you hit apply or save in the main menu. If it still doesn't fire go back to the main menu, hit apply then save then go back and tell it to download the block list again and it should fire once it finishes downloading and installing the block list. This is the only way I can get squidgaurd to work. If you follow the download with hitting apply or save again squidgaurd will stop.
  • J

    SNORT vs Suricata Detection

    4
    0 Votes
    4 Posts
    6k Views
    bmeeksB
    Good advice above from jflsakfja and fsansfil. In my view it is sort of like preferring vanilla over chocolate when choosing an ice cream flavor.  It is a case of personal taste. If you have a paid Snort VRT subscription, then those rules are updated twice per week (on Tuesdays and Thursdays).  The Emerging Threats Open rules (ET-Open) are updated pretty much daily, but they cover a subset of the threats that are covered by the ET-Pro (paid) rules.  The ET-Pro rules are also updated daily.  Currently an ET-Pro subscription is $499/year.  The Snort VRT (for home use) is $29.99/year.  There are free Snort rules available that only require you to register, but they are 30-days old (meaning no protection for any threats newer than 30 days). So if you use the totally free rules from either Snort VRT or Emerging Threats, you have to accept the fact you are not protected from all of the current threats.  However, as jflsakfja said, you can compensate by writing your own custom rules for either package (Snort or Suricata) if you fully understand your network and have a good grasp of the signatures for current malware threats. In my view, neither package is necessarily "better". Bill
  • S

    Upgrade to pfsense 2.2 broke postfix forwarder

    2
    0 Votes
    2 Posts
    2k Views
    S
    Well, crap.  I found out my issue is this: https://forum.pfsense.org/index.php?topic=40622.msg479547#msg479547 Apparently pfsense 2.2 security sysctrl option does not allow non root users to listen on low ports - and /var/spool/postfix is owned by the postfix user.
  • N

    HAProxy stable in 2.2?

    3
    0 Votes
    3 Posts
    938 Views
    N
    All right. Thank you. Nicolas
  • N

    Haproxy-devel external address option (pfsense 2.2)

    3
    0 Votes
    3 Posts
    1k Views
    N
    Hi, thank you for your answer. Nicolas
  • D

    Bypass ssl-bump on squid3-dev

    37
    0 Votes
    37 Posts
    19k Views
    marcellocM
    @webstor: He has to generate a certificate for the required domain when bumping server-side first, it is a wildcard generated for the correct domain and not the ip. I know it is for the site. the question is, in transparent mode, how could squid know without intercepting that connection from 192.168.1.1 to 64.54.10.10 is a request to microsoft windows update? Squid will only know the domain after interception, so acl will take no effect. Also there are some notes about fast and slow acls that not work on this or that squid option.
  • T

    Need the best squid caching policy for a slow connection

    4
    0 Votes
    4 Posts
    1k Views
    T
    I had a similar network in size, and the cache hit ratio was around 15-20%. YMMV. That would likely increase if SSL interception was enabled but that bring it's own set of problems. Try it, it isn't too difficult to setup, especially if you use the pfsense package.
  • bmeeksB

    Suricata 2.0.6 pkg v2.1.4 Release Notes (pfSense 2.2 only)

    8
    0 Votes
    8 Posts
    1k Views
    C
    Your welcome Bill! Good call on how you programmed this.
  • W

    Smokeping on pfSense

    22
    1 Votes
    22 Posts
    7k Views
    D
    So you mean - killbyname in case something happened to pid file? I wouldn't do it like that, but I am not developing pfSense. If developers need to killbyname, they should be using link with different name themselves :) I am not here to judge this. If that's how it is done currently, we'll use workaround, I just don't like that many workarounds around pfSense :(
  • H

    Squid + SquidGuard + AD

    12
    0 Votes
    12 Posts
    12k Views
    A
    @Luiz Gustavo , there is now other repositories working ???????
  • S

    Mailreport Problems

    4
    0 Votes
    4 Posts
    2k Views
    P
    This is in Mail Report 2.3, available now. Along with fixes here also: https://forum.pfsense.org/index.php?topic=83668.msg488777#msg488777
  • M

    Bacula Client Package doesn't work on 2.2-rc

    6
    0 Votes
    6 Posts
    2k Views
    jimpJ
    Bacula should be OK now on 2.2, as of package version 1.0.6.
  • M

    Sarg + dansguardian

    2
    0 Votes
    2 Posts
    892 Views
    R
    @markusxyz: Is there any conflict with sarg+dansguardian? Should I use squidguard instead? There is no incompatibility between Sarg and dansguardian. However, you will have to set the log format for dans to output in the squid format for Sarg to parse it. BTW, there are much better options for dansguardian reporting… you could install webmin and the DG reporting package - or see this thread https://forum.pfsense.org/index.php?topic=69003.msg377440#msg377440 The question on squidguard has nothing to do with Sarg… squidguard and dansguardian are not the same thing. Squidguard does blacklist based filtering. Dans does both blacklist and content based filtering.
  • O

    Simple set-up Squid3 and Clam with Failover

    3
    0 Votes
    3 Posts
    919 Views
    O
    Well, I got Failover working. Ticking the "default gateway switching" box did the trick. I did not need to add a floating rule like many trying to do this in 2.1.5.
  • K

    Snort Rule Fatal Error

    3
    0 Votes
    3 Posts
    979 Views
    K
    Thanks BBcan177, I'll disable the rule.
  • E

    Ntopng won't load

    3
    0 Votes
    3 Posts
    1k Views
    E
    Thanks for the response.  Looking at the PFsense dashboard, it's sitting at 20% memory usage of the 2GB of memory being used.  I've got other fish to fry with my network, so ntopng is more of a luxury.  Alas, it was wonderful when it worked.
  • ?

    2.2 and bind package: libz.so.5

    8
    0 Votes
    8 Posts
    2k Views
    D
    @knebb: Just wondering as there is now no symlink libz.so.5 nor libz.so anywhere… Well yes, that is the point! It does NOT need libz.so.5. It gets moaning about that one since the linker symlink under /usr/lib points to the non-existent deprecated library version. (If you look into /usr/pbi, the PBI thing somehow creates its own directory structure for each package under /usr/pbi/<packagename-$arch>/local, and redirects the calls and produces its own symlinks copies there. So, just removing/fixing the broken symlink under /usr/lib is not enough. You need to nuke and reinstall the package as well. At least that's my understanding of these stupid issues, I hate the PBI thing with passion and pretty sure at least some of the few remaining package maintainers are of the same opinion.</packagename-$arch>
  • N

    Pfsense 2.2 - squid3 - skype + icq: error:invalid-request - HIER_NONE/- text/htm

    2
    0 Votes
    2 Posts
    3k Views
    marcellocM
    While intercepting port 443, on http protocol will work. Skype uses port 443 but it's protocol is not http. That's why it's not working
  • A

    Freeradius authentication over IPSEC

    5
    0 Votes
    5 Posts
    2k Views
    D
    This won't work out of the box with IPSec for reasons documented here: Why can't I query SNMP, use syslog, NTP, or other services initiated by the firewall itself over IPsec VPN
  • M

    Ezjail package?

    1
    0 Votes
    1 Posts
    908 Views
    No one has replied
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.