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
    J
    @KOM Good morning. The goal is to keep Pfsense and have another proxy option in case Squid really doesn't work anymore (from what I've researched, Squid has been discontinued).

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

    2k Topics
    16k Posts
    RedDelPaPaR
    @bmeeks Understood. Thank for kindly for your help. I will likely be ordering a new unit soon.

  • Discussions about packages that handle bandwidth and network traffic monitoring functions such as bandwidtd, ntopng, etc.

    573 Topics
    3k Posts
    dennypageD
    @kabeda If memory serves, that old version of ntopng did not run as user ntopng, but as user nobody. There are lots of problems in that old version. Anyway, check the ownership and permissions of /var/db/ntopng and make sure it matches the user that ntopng runs as. You may need to set ownership of the entire hierarchy. Example: /usr/sbin/chown -R nobody:nobody /var/db/ntopng However, the better choice would be to upgrade to a more recent version.

  • Discussions about the pfBlockerNG package

    3k Topics
    20k Posts
    GertjanG
    @netboy said in is something wrong with pfBlockerNG?: arm64 That might be a factor. I said that our code base is "bit-wise" identical - and we use the same processors. Actually, that's wrong. X86/amd64 isn't arm64 at all. So, I'm not finger pointing, but I can't test the 'arm' version, as I'm using a 4100, a amd64 device. I has a new unbound version installed yesterday. The previous version was 1.23.x - the new version is 1.24.1. To get it : ssh or console, option 8, and then pkg update pkg upgrade and again, not sure if this is valid for arm.

  • Discussions about Network UPS Tools and APCUPSD packages for pfSense

    102 Topics
    3k Posts
    dennypageD
    @fjmp24 said in Notification: UPS ups battery is low: If I remove ignorelb directive, my UPS shuts down after 16 seconds This means your UPS is signaling a low battery. Either your battery is bad, or your UPS is bad. Most likely battery, but you never know. I suggest reaching out to Eaton support.

  • Discussions about the ACME / Let’s Encrypt package for pfSense

    503 Topics
    3k Posts
    M
    I am using the DNS-Update method I have to use a DNS-Sleep of 5 minutes to let the letsencrypt txt dns record update propagate. During this 5 minutes the acme-webgui times out. when the acme-webgui times out the Action list is NOT executed. How can I solve this ? Would it maybe be an idea to let the acme.sh script execute the actions in the action list as a post-hook instead of the web-gui? Or maybe add an option to add post-hooks in the webUI ?

  • Discussions about the FRR Dynamic Routing package on pfSense

    296 Topics
    1k Posts
    C
    This one has been tricky still not sure what to try. Any ideas?

  • Discussions about the Tailscale package

    93 Topics
    644 Posts
    C
    @elvisimprsntr Thank you. I would not be surprised if I ended up with a lengthy solution that works but needs significant improvement. I am using a Netgate 6100 with pfSense+, starting with version 24.x. I had updated Tailscale without trouble per this discussion by using pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-x.y.z.pkg. This worked until pfSense+ version 25.0.07 (FreeBSD 15-CURRENT) and Tailscale upgrade 1.88.3. After several attempts and web searches, I was only able to install that upgrade by using: fetch https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.88.3.pkg, and then IGNORE_OSVERSION=yes pkg-static add -f tailscale-1.88.3.pkg. Then, I could not restart Tailscale, no matter what I tried, including the sequence: service tailscaled stop, tailscale logout, service tailscaled start, and then tailscale up.

  • Discussions about WireGuard

    714 Topics
    4k Posts
    R
    I was on PfSense version 23.xx (don't recall the xx) and was able to start the Wireguard service. I upgraded to the 25.11 beta version and now the Wireguard service will not even start. I am on Wireguard version 2.1, and I see that there are versions that go up to 2.9. How do I upgrade to a later version? The only version in the pfSense updater is 2.1. Thank you
Log in to post
Load new posts
  • M

    CRON job - calling URL

    3
    0 Votes
    3 Posts
    1k Views
    M
    @rcoleman-netgate THANK YOU :) That did the trick
  • S

    Netgate SG-1100 unable to install packages

    8
    0 Votes
    8 Posts
    2k Views
    R
    @spectre-988 said in Netgate SG-1100 unable to install packages: I've been working on using the device at my home for a HA fail over device. I've got the device to become part of the HA but when the primary wants to sync the packages they aren't able to due to packages not being installed. I try to install myself but package manager just sits at waiting for the update system to initiate. I am not sure if the version of Pfsense I am using is the problem or the Bios. I know both are older and tried to update Pfsense version and get that the system is on a later version than the official release. Without physically separated interfaces the 1100 is not suited for HA. It could do it, sure, but the WAN, LAN, and OPT are all the same NIC in the system, just VLAN'd to a switch. Your expectations should be very tempered -- failover cannot happen based on physical disconnection and is going to be unreliable.
  • J

    Zabbix Uncaught Error

    5
    0 Votes
    5 Posts
    2k Views
    J
    Hi, The solution it'a in this link: https://github.com/rbicelli/pfsense-zabbix-template/pull/118 I hope help somebody.
  • S

    This topic is deleted!

    1
    0 Votes
    1 Posts
    69 Views
    No one has replied
  • 4

    HAproxy can only connect to "Default Backend"

    1
    0 Votes
    1 Posts
    893 Views
    No one has replied
  • R

    Tailscale - package request / work opportunity

    2
    0 Votes
    2 Posts
    2k Views
    J
    @returntrip https://youtube.com/watch?v=Fg_jIPVcioY
  • N

    HAProxy - route by domain name

    haproxy acl
    2
    0 Votes
    2 Posts
    2k Views
    N
    @nasheayahu said in HAProxy - route by domain name: wwwkohanyimcom Host matches: no no www.kohanyin.com kohanyimcom Host contains: no no kohanyin.com I found the problem, my domain was spelled incorrectly...
  • D

    How to get tcptraceroute, or a functional equivalent

    3
    0 Votes
    3 Posts
    1k Views
    E
    I know that this question is old, but it actually helped me getting tcptraceroute on opnsense. The key thing was pkg add from freebsd. So for me it needed to be updated since I am on freebsd:13:amd64, I found https://freebsd.pkgs.org/13/freebsd-amd64/ with search :) So for me the resulting command was: pkg add http://pkg.freebsd.org/FreeBSD:13:amd64latest/All/tcptraceroute-1.5beta7.txz Still same version of tcptraceroute 2 years later, but it is how to find the package name that is important So thanks for this thread.
  • R

    Wireguard Works only when OpenVPN Running in 2.6.0

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

    22.05 upgrade - site-to-site wireguard broken

    2
    0 Votes
    2 Posts
    1k Views
    J
    @buzz2912 Sounds like; https://forum.netgate.com/topic/173074/22-05-upgrade-breaks-remote-access-openvpn/15 same problem.
  • N

    stunnel won't start

    2
    0 Votes
    2 Posts
    862 Views
    N
    Nvm im dumb... didn't read this line: [!] Service [Wireguard_SSL]: Protocol not supported
  • G

    Freeradius limit access

    7
    0 Votes
    7 Posts
    2k Views
    G
    @mcury Thanks but this doesn't work in the users file. I think it's very restricted in what sort of entries can be made :(
  • B

    pfSense+ 22.05/Wireguard dependency not documented

    Moved
    15
    0 Votes
    15 Posts
    2k Views
    B
    @jimp Ok. So I took a few minutes and there's somthing I'm not getting. When the Update setting is set to 22.05 the Package Manager shows two updatable packages, WireGuard 0.1.6_1 and ipsec-profile-wizard 1.0_4. [image: 1656626435886-screenshot-22.05.png] And much to my surprise, when the Update setting is set to 22.01, I see one updatable package WireGuard 0.1.6_1 !: [image: 1656626445074-screenshot-22.01.png] Is this correct? Is WireGuard 0.1.6_1 supposed to work on 22.01, or not? Upgrading WireGuard to 0.1.6_1 is the action that took down WireGuard in our NH router. Here are the messages from the NH log that appear to describe the problem: Jun 27 21:12:15 kernel linker_load_file: /boot/modules/if_wg.ko - unsupported file type Jun 27 21:12:15 kernel KLD if_wg.ko: depends on kernel - not available or version mismatch What's wrong?
  • D

    bind no longer running after pkg/pfsense updates

    4
    0 Votes
    4 Posts
    1k Views
    S
    @dvl Great. Option 2 would have been to reinstall and restore from backup. The upgrade thing catches lots of people. I put it in my sig a while back. One such problem is when the package is dependent on a PHP version that doesn't exist in the older pfSense, so it gets upgraded. There's a redmine to hopefully fix it or at least block/warn people.
  • W

    Bind upgrade producing errors on pfsense 2.5 upgrade

    112
    4 Votes
    112 Posts
    40k Views
    A
    Well one issue with the move to the new version. Previously bind was installed on my /cf now it is in /var/etc/named/etc/namedb/ a side effect, is whenever the router is restarted all my keys specified as global option will vanish include "/etc/namedb/acme-keys.key"; include "/etc/namedb/ddns-key-inf.key"; include "/etc/namedb/ddns-key-sec.key"; include "/etc/namedb/ddns-key.key"; An idea would be to save them in the pfsense configuration.
  • J

    WebUI takes forever to load if UPS unreachable...

    Moved
    8
    0 Votes
    8 Posts
    2k Views
    J
    @dennypage said in WebUI takes forever to load if UPS unreachable...: I am assuming that the host running the NUT sever is using a fixed IP address, yes? And in the NUT config on pfSense, are you using the IP address (rather than hostname) to identify the NUT sever? Yep, my whole network is based around fixed IP's, either both on the machine and dhcp server or only in dhcp server. And yes pfsense connects via IP. @dennypage said in WebUI takes forever to load if UPS unreachable...: You might want to consider moving to using pfSense as the NUT sever and having the other host as a client. NUT on pfSense is very stable. Well my room is kinda limited because of the network cabling, the pfsense box and the UPS is on the opposite end of my room. Would require a 5 meter+ cable to connect the 2. Thats why i opted for a dedicated box and ATM this problematic box is the only one i can use. Done a few things to it including installing intel-microcode package and seems to be stable now ( knocks on wood ).
  • V

    System -> Patches results in 404 after 22.05 upgrade from 22.01

    Moved
    5
    1
    0 Votes
    5 Posts
    1k Views
    V
    @jimp Thanks that worked. It seems like the install process did not recognize that the Patches package was there and re-installed it. But left the menu option in place. [image: 1656510068927-420937b5-a131-4cd4-9c3e-8450d18f77e7-image.png]
  • E

    PF, FreeRadius and SQL

    1
    0 Votes
    1 Posts
    860 Views
    No one has replied
  • Z

    No upgrade icons

    Moved
    11
    0 Votes
    11 Posts
    2k Views
    Z
    @bmeeks OK ... I understand
  • J

    Nmap package

    13
    0 Votes
    13 Posts
    2k Views
    stephenw10S
    Hmm, looks like that was changed here: https://github.com/pfsense/FreeBSD-ports/commit/7f64c9db1a0f5c0ffc18afe7a9f7a9b9f82f9c67 Not sure how you ended up with both though.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.