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.
  • 0 Votes
    3 Posts
    2k Views
    C
    This means you installed that awful mess of a Lusca package which points your packages to a server that's full of malware. Best to reinstall, and don't blindly run commands you find on the Internet.
  • Haproxy Fatal Error

    9
    0 Votes
    9 Posts
    2k Views
    P
    Funny it works a few hours before the pkg v0.29 pullrequest was merged. ;D Anyway if you do run into any other issue with haproxy let me know. I do intend to keep it working on 2.1.x for some time to come.. However the binaries wont be updated anymore, so you are (slightly?) at risk there! Still i don't regularly check my fixes&changes on 2.1, so it might happen again that i break it. :o sorry in advance.. :-[ Regards, PiBa-NL
  • Filemanager pkg Error after update to 0.2.0

    4
    0 Votes
    4 Posts
    804 Views
    D
    PR merged, BTW.
  • Packages and XMLRPC Sync

    11
    0 Votes
    11 Posts
    16k Views
    D
    @marcelloc: Ever considered splitting this to a separate inc and getting it included into core? I find your code in lots of packages, fixing the same comment typos and code style everywhere. It's most completely identical otherwise, except for some customized log messages… Sounds really like a waste of time to maintain the code in loads of places. In some packages, most of the PHP code is the copy-paste of XMLRPC sync. Example - 2/3 of the actual code are XMLRPC sync.
  • Freeradius not starting automaticly when booting up PFSense

    5
    0 Votes
    5 Posts
    2k Views
    M
    Okay, clear. The package FreeRADIUS is not starting at boot, but is giving the error above, when I manually start it, it works.
  • Instructions for Asterisk package?

    1
    0 Votes
    1 Posts
    548 Views
    No one has replied
  • Zabbix 2 Proxy compatibility

    1
    0 Votes
    1 Posts
    725 Views
    No one has replied
  • MOVED: Filter correctly HTTPS sites using squid3

    Locked
    1
    0 Votes
    1 Posts
    431 Views
    No one has replied
  • Clamav not working in 2.2.4 - can it be fixed in setting?

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • MOVED: Snort Pass White List not working correctly?

    Locked
    1
    0 Votes
    1 Posts
    507 Views
    No one has replied
  • [solved]bacula - webgui config - bug?

    8
    0 Votes
    8 Posts
    2k Views
    P
    package upgraded thank you
  • [nanobsd] Not enough space

    2
    0 Votes
    2 Posts
    3k Views
    P
    System->Advanced, Miscellaneous tab, RAM Disk Settings. Increase the size of /var Keep in mind the amount of real memory you have in your system - do not increase /var so much that all your real memory is consumed.
  • Unable to install packages. Stop at extracting

    2
    0 Votes
    2 Posts
    696 Views
    D
    Go to Diagnostics - NanoBSD and make it permanently read-write.
  • MOVED: Reverse proxy limits session traffic for RDS Gateway

    Locked
    1
    0 Votes
    1 Posts
    474 Views
    No one has replied
  • MOVED: Transparent reverse proxy by HAProxy in 3-Legs scheme

    Locked
    1
    0 Votes
    1 Posts
    509 Views
    No one has replied
  • 0 Votes
    1 Posts
    376 Views
    No one has replied
  • Snort 3.2.6 not saving alert or block list when pfsense is rebooted

    3
    0 Votes
    3 Posts
    775 Views
    F
    Ok my bad then.
  • Snort feature request OPTx renamed to name assigned in the interface

    1
    0 Votes
    1 Posts
    485 Views
    No one has replied
  • Problem with Postfix forwarder

    13
    0 Votes
    13 Posts
    3k Views
    A
    @biggsy: Get rid of mailscanner/spamassassin to start.  Add back in once you have postfix working.  (You may find that you don't need anything more than postfix.) You didn't follow the Quick Start Guide exactly because you had LAN Net as the listen interface.  Now that postfix is listening on WAN Address, you need to have a way for remote mail servers to connect and send mail from the Internet through your WAN interface. Do you have a real domain?  Do you have a DNS MX record that points to your WAN Address?  Without those, it is going to be very difficult to help you. Please do not post in two threads.  That doesn't encourage people to try and help you. biggsy,  I have DNS MX, where I put the DNS MX?
  • Nagios/NRPE Monitoring of Internal Private Network Hosts [RESOLVED]

    3
    0 Votes
    3 Posts
    3k Views
    D
    Hi, Now resolved. There were quite a few things at play here. First was the use of SSL in the original check_nrpe from our external nagios server, and not in the second nrpe fired off from the firewall. Then there was the lack of the firewalls IP in allowed hosts. Then there was selinux on the private hosts that kept denying nrpe bind to our custom port. It also doesnt help that the private hosts do not have internet outbound for security purposes. So troubleshooting and downloading packages etc, very time consuming. Thanks.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.