Subcategories

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

    4k Topics
    21k Posts
    N
    @andrew_cb Thank you very much for this, I just tried your proposed solution and it did work! That was driving me crasy! Way simpler than deleting the haproxy_server_state file.
  • 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
    T
    @andrebrait will you be able to rebase pfblockerng-adblock-clean on top of devel in the foreseeable future? I have been able to make use of patches until I upgraded to 25.07-RELEASE. The conflicts are deep. Oddly the pfblockerNG-devel package is 3.2.7 despite the current refs having 3.2.9 in the Makefile.
  • 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
    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
    594 Posts
    E
    @totalimpact Tailscale 1.54.0 is 2+ years out of date. Tailscale has made quite a number of changes since Tailscale 1.54.0, likely rendering it incompatible with their servers. I would consider manually updating the Tailscale FreeBSD package. FreshPorts does not maintain an archive of all the releases, only the latest compiled by the volunteer maintainers. The key to manually upgrading is knowing which FreeBSD version your pfSense release is running, i.e. 14 or 15. You can following along here.
  • Discussions about WireGuard

    692 Topics
    4k Posts
    P
    SOLVED. Turns out nothing wrong with my tunnel setup and not due to CGNAT. The reason PING works and other traffic doesn't is due to packet size and MTU. Something on the wireless network means that the default MTU doesn't work, forcing a smaller MTU to 1280 on pfSenseB fixed this. This Reddit thread has more details of this issue: https://www.reddit.com/r/WireGuard/comments/qmsa2n/ping_works_but_sites_arent_loading/
  • HAProxy GUI error after upgrade to pfSense+ 23.01

    23
    1 Votes
    23 Posts
    5k Views
    G
    Happy to confirm the error has been resolved by upgrading to pfSense+ 23.05. That release includes the upgraded package haproxy-devel 0.62_13 (was haproxy-devel 0.62_12). Hope this helps someone.
  • Bandwidthd legend/logo pics not showing

    3
    2 Votes
    3 Posts
    969 Views
    A
    Same problem after so many years
  • udpbroadcastrelay wont start

    Moved
    3
    0 Votes
    3 Posts
    643 Views
    B
    @stephenw10 thanks for your answer. looks like you have to configure a forward to be able to start the service, thanks
  • No available packges (2)

    Moved
    9
    0 Votes
    9 Posts
    849 Views
    S
    @Dobby_ this one actually works. thank you so much for your help!
  • Block layer 7 on websites

    13
    0 Votes
    13 Posts
    2k Views
    M
    @ammar177 Using pfBlockerNG. Create an alias of ASNs you want to block (netflix,hulu,peacock,etc..). Apply that alias to the IPs that should be blocked. There isnt a clean way to block streaming sites on pfsense. Snort openapp.id rules have not been updated in some time (over 5 years) so they will not account for the latest streaming sites. You will need to write your own rules for that. If you are looking to block streaming media sites on a phone its probably best to point that client to openDNS or NextDNS where you can do category-based blocking and not use pfSense for DNS. That's the best recommendation i can give.
  • Freeradius not taking new ACME certificate

    18
    0 Votes
    18 Posts
    2k Views
    A
    There’s nothing more expensive about providing a wildcard. But, if they were the same price nobody would buy a single domain certificate, because it would be simpler and as cheap to buy the wildcard. People who provide certificates have invested time and money to be in that club. Therefore they want to get back as much as they can from selling them. People are willing to pay more for wildcards so they are charged more. It’s just ordinary economics.
  • node_exporter failing uname collector

    1
    0 Votes
    1 Posts
    259 Views
    No one has replied
  • FreeRADIUS config file exposure/preservation feature request

    1
    0 Votes
    1 Posts
    346 Views
    No one has replied
  • radsecproxy package

    1
    0 Votes
    1 Posts
    236 Views
    No one has replied
  • Enabling/disabling interfaces creates issues for ntopng

    1
    0 Votes
    1 Posts
    255 Views
    No one has replied
  • System Patches package version 2.2.4

    1
    10 Votes
    1 Posts
    558 Views
    No one has replied
  • Should I uninstall a patch before/after an upgrade?

    Moved
    5
    0 Votes
    5 Posts
    1k Views
    jimpJ
    If you added a patch manually and that fix is included in the new release, then just delete the entry from the package without touching it. If you revert a patch after upgrading you undo the fix and put back the bad code. Manual patch entries are never automatically removed. Only the "recommended" list changes automatically by version.
  • pkg repository update fall

    1
    0 Votes
    1 Posts
    407 Views
    No one has replied
  • lcdproc crystalfontz problem

    11
    0 Votes
    11 Posts
    2k Views
    Dobby_D
    @fireodo said in lcdproc crystalfontz problem: @Dobby_ said in lcdproc crystalfontz problem: Thank you very much indeed, would be one of my next options (project) to enrich my small APU´s. If you like to look here too: https://lcdstore.de/CF635TMFKU Cool after installing the Power and reset button in/on the APU I would assume that could be the next "project" or perhaps later if the Bluetooth serial port is ready installed.
  • [Solved] pfSense-pkg-System_Patches reinstallation failed!

    8
    0 Votes
    8 Posts
    1k Views
    F
    @SteveITS said in [Solved] pfSense-pkg-System_Patches reinstallation failed!: @furom They’re working on something. There’s an open redmine from a couple years ago but I don’t have the URL handy. At least it blocks it now. Per my sig it was… worse. That is great. And fully agree, this is much to prefer over ruining your system, no doubt at all so with some more insight, only grateful it (as usual with pfSense) turned out well :)
  • Several vulnerable packages without update

    16
    0 Votes
    16 Posts
    2k Views
    Dobby_D
    @fadinzr [23.05-RELEASE][root@xx xx xx]/root: pkg audit -F vulnxml file up-to-date libxml2-2.10.3_1 is vulnerable: libxml2 -- multiple vulnerabilities CVE: CVE-2023-29469 CVE: CVE-2023-28484 WWW: https://vuxml.FreeBSD.org/freebsd/0bd7f07b-dc22-11ed-bf28-589cfc0f81b0.html curl-8.0.1 is vulnerable: curl -- multiple vulnerabilities CVE: CVE-2023-28322 CVE: CVE-2023-28321 CVE: CVE-2023-28320 CVE: CVE-2023-28319 WWW: https://vuxml.FreeBSD.org/freebsd/a4f8bb03-f52f-11ed-9859-080027083a05.html py39-setuptools-63.1.0 is vulnerable: py39-setuptools -- denial of service vulnerability CVE: CVE-2022-40897 WWW: https://vuxml.FreeBSD.org/freebsd/1b38aec4-4149-4c7d-851c-3c4de3a1fbd0.html redis-7.0.10 is vulnerable: redis -- HINCRBYFLOAT can be used to crash a redis-server process CVE: CVE-2023-28856 WWW: https://vuxml.FreeBSD.org/freebsd/96b2d4db-ddd2-11ed-b6ea-080027f5fec9.html 4 problem(s) in 4 installed package(s) found. [image: 1685297038850-27latest.jpg] [image: 1685297038896-27latestpkg.jpg]
  • Minor UI bug in udpbroadcastrelay

    1
    0 Votes
    1 Posts
    367 Views
    No one has replied
  • Package Upgrades via CLI

    4
    0 Votes
    4 Posts
    733 Views
    JonathanLeeJ
    Pkg update Pkg clean Clean gets rid of old versions no longer needed
  • system_patches update question

    Moved
    12
    0 Votes
    12 Posts
    2k Views
    RobbieTTR
    @jimp Looks fine to me now [running 23.05]. A few minutes ago: [image: 1685104895736-2023-05-26-at-13.39.19.png] Now: [image: 1685104911689-2023-05-26-at-13.40.17.png] ️
  • After upgrade to 23.05 RELEASE, Syslog-NG won't start

    16
    0 Votes
    16 Posts
    2k Views
    provelsP
    @jimp Yes, great work as always. All it takes is another one of us mooks to run your code and it's, "Oh, yeah, that..."!
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.