Subcategories

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

    4k Topics
    21k Posts
    F
    @JonathanLee no way to fix this ?? to do some kind of purge to squid and squidguard and install them again The last option I'm trying to avoid is to reinstall the entire system.
  • 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
    I am considering a “novel” solution to this lack of syslog support in pfBlockerNG. The obvious way would still be to use syslog-ng but I’m instead considering using the builtin syslogd in pfsense as that is already shipping pfsense logentries to my siem. It seems it would be quite simple to use the SHELLCMD package to run a small daemon script at startup that monitors the needed pfBlocker logfiles with “tail -F” and then converts the contents into a more syslog friendly format before piping that into “logger” with the local0 facility as destination. That destination is already syslogged of to my SIEM by the builtin syslogd setup in pfSense. This would probably still see everything being shipped in duplicates because of how pfBlockerNG rotates its logs (if that has not been fixed), but this way I could adapt the script to skip entries in the 1 minute timeframe when the pfBlocker reload happens. That it still a rather shitty and complicated solution requiring a package, but it seems builtin syslog support is not in the pfBlockerNG development priority list, so a manual workaround is required.
  • 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
    H
    I figured out the issue. I missed adding the 3rd locations Lan to the static routing. Now all is working perfect.
  • MOVED: Snort False-Positives

    Locked
    1
    0 Votes
    1 Posts
    533 Views
    No one has replied
  • Ntopng stopped working and will not start up

    Locked
    9
    0 Votes
    9 Posts
    7k Views
    D
    @gwaitsi: "redis" dependency package  - seems not to be enabled. it is there, and returns set redis_enable to YES in /etc/rc.conf 1/ This is not how you enable services in pfSense 2/ Stop necroposting, this thread is 2,5 yrs old, concerning incredibly buggy PBI packages. Someone lock this, please. Just attracting noise.
  • Siproxd Registered Phones

    3
    0 Votes
    3 Posts
    1k Views
    bill_mcgonigleB
    Fix here works: https://github.com/hb9xar/FreeBSD-ports/commit/14af74e81fe9f432fa95015e1a0c92b4f3af6537#diff-09ab23ef3879c4419b1d960795ed94f7
  • Redis (ntopng dependency) defaults to listening on all interfaces?

    3
    0 Votes
    3 Posts
    1k Views
    jimpJ
    I was looking at something else in ntopng today and went ahead and tested/committed a fix so that redis now only binds to localhost. Still worked fine for me so I pushed the new version out for everyone.
  • Do I need snort and/or pfblocker ?

    2
    0 Votes
    2 Posts
    1k Views
    DerelictD
    Probably not. Personally, I would leave the FTP server running and only enable the firewall rule/port forward when it is needed.
  • MOVED: Getting Lightsquid's IP Resolve -> DNS working

    Locked
    1
    0 Votes
    1 Posts
    482 Views
    No one has replied
  • MOVED: PFBlockerNG Errors Loading Rules - "Macro Not Defined"

    Locked
    1
    0 Votes
    1 Posts
    442 Views
    No one has replied
  • MOVED: Snort keeps blocking an IP address that's in the pass list

    Locked
    1
    0 Votes
    1 Posts
    419 Views
    No one has replied
  • MOVED: Suricata - VTR rules md5 fails to download

    Locked
    1
    0 Votes
    1 Posts
    396 Views
    No one has replied
  • FreeRadius Group Membership not working

    2
    0 Votes
    2 Posts
    1k Views
    A
    Stills seems to be a bug in the freeradius implementation of LDAP-Auhtorize. See my post here : https://forum.pfsense.org/index.php?topic=82209.msg566789#msg566789 and this : https://forum.pfsense.org/index.php?topic=43675.msg515428#msg515428
  • Freeradius ldap group filter issue

    2
    0 Votes
    2 Posts
    4k Views
    A
    Stills seems to be a bug in the freeradius implementation of LDAP-Auhtorize. See my post here : https://forum.pfsense.org/index.php?topic=82209.msg566789#msg566789 and this : https://forum.pfsense.org/index.php?topic=43675.msg515428#msg515428
  • Problem install of package. tar: Failed to set default locale

    2
    0 Votes
    2 Posts
    2k Views
    jimpJ
    That "error" is harmless, there is likely some other different error happening. Post the full output from the package installation window when it fails.
  • Upgrading an external package in pfSense

    2
    0 Votes
    2 Posts
    887 Views
    jimpJ
    That depends on what you mean by "keep this package up to date". If you mean keeping the package itself current/updated, there is no way to keep it updated that does not also potentially compromise the integrity of the package set on pfSense. One of several reasons we do not recommend installing packages from other repositories, including FreeBSD's own repositories. You can reinstall it by hand when you know an update is available. FreeBSD packages are good about not clobbering your own files/data when uninstalling/updating/installing again. If you mean keeping it across pfSense updates, that's even less certain. You will likely have to manually reinstall it after each update.
  • Package installation problem.

    6
    0 Votes
    6 Posts
    5k Views
    D
    Urgh…. By NOT cutting the install output.
  • Working with Packages on 2.3 and Converting to Bootstrap

    Locked
    41
    0 Votes
    41 Posts
    28k Views
    jimpJ
    This thread was specifically for people who were developing packages previously who needed information on converting existing packages for use on pfSense 2.3 in the new pkg and bootstrap framework. Not for general package creation questions.
  • 0 Votes
    1 Posts
    532 Views
    No one has replied
  • FreeRadius authentication and check-items

    1
    0 Votes
    1 Posts
    754 Views
    No one has replied
  • Dnscrypt-proxy comming to pfsense package?

    13
    0 Votes
    13 Posts
    4k Views
    C
    johnpoz we get it, you dont like dnscrypt, so why are you in this thread? If someone wants to run dnscrypt on their own kit, its none of your business. My setup on my existing router which I plan to migrate to pfsense is sort of like this local caching resolver -> forwards uncached requests to my own dnscrypt endpoint of which that resolves out on the internet. and yes I know what dnssec is and the mode is nothing to do with dnssec. uozewe -I am willing to send something your way for the work, a cli only package is good enough for me, so just the binary, rc script and maybe sample configuration.  I got no issue editing unbound and what not to add forwarder manually.
  • Installation of pfSense-pkg-openvpn-client-export: 1.3.8 failed

    2
    0 Votes
    2 Posts
    914 Views
    jimpJ
    Your pkg metadata is very out of date if it's trying to fetch a file that old. Try running "pkg update -f" from a shell prompt and then see if it works. It should be pulling version 1.3.13, not 1.3.8.
  • UPS Mgnt Software - PowerPanel Business Edition

    2
    0 Votes
    2 Posts
    1k Views
    w0wW
    I don't see any version of this software available for freebsd. If NUT works you don't need anything other to be installed on firewall.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.