Subcategories

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

    4k Topics
    21k Posts
    JonathanLeeJ

    @aGeekhere They just release Squid 7 and it is stable if you want to check it out

    "The Squid HTTP Proxy team is very pleased to announce the availability
    of the Squid-7.1 release!

    This release is, we believe, stable enough for general production use.
    We encourage all users of any previous major version of Squid to upgrade to it,
    as well as users of beta version 7.0.X.

    It can be downloaded from GitHub, at
    https://github.com/squid-cache/squid/releases/tag/SQUID_7_1

    Since version 6, Squid offers:

    better support for overlapping IP ranges and wildcard domains in acl countless security, portability, and documentation fixes

    Since version 6, some previously deprecated features have been removed:

    Edge Side Includes (ESI) access to the cache manager using the cache_object:// scheme - use
    http instead the squdclient tool - use curl
    http://<squid-address>/squid-internal-mgr/menu instead the cachemgr.cgi tool the purge tool - use the http PURGE method instead Ident protocol support basic_smb_lm_auth and ntlm_smb_lm_auth helpers - use Samba's
    ntlm_auth instead

    Further details can be found in the release notes and in the changelog

    Please remember to run "squid -k parse" when testing the upgrade to a new
    version of Squid. It will audit your configuration files and report
    any identifiable issues the new release will have in your installation
    before you "press go".

    If you encounter any issues with this release please file a bug report at
    https://bugs.squid-cache.org/

    --
    Francesco Chemolli

    squid-users mailing list
    squid-users@lists.squid-cache.org
    https://lists.squid-cache.org/listinfo/squid-users"

    I am having issues with this right now

    "I got as far as this with the make clean install no matter what I do I can’t get this package installed. I have tried pkg install heimdal same error after install and pkg install krb5 and pkg install krb5-devel. I don’t know what I am doing wrong it does the make clean for a while and crashes for the bootstrap version the other one I could get going

    ERROR: checking whether S5L_CTX_sess_set_get_cb() callback accepts a const ID argument" ... yes checking "whether X509_get0_signature() accepts const parameters" ... yes checking whether the TXT_DB use OPENSSL_PSTRING data member... yes checking whether the squid workaround for buggy versions of sk_OPENSSL_PSTRING_V alue should used... no checking whether the workaround for OpenSSL IMPLEMENT_LHASH_ macros should used ... yes configure: OpenSSL library support: yes -lcrypto -lss1 configure "Library -Kit-kros" support: no (auto) /configure: LIBHEIMDAL_KRB5_PATH+=-L/usr/lib: not found /configure: LIBHEIMDAL_KRB5_CFLAGS+=-1/usr/include: not found checking for LIBHEIMDAL_KRB5... no configure: error: Required library 'heimdal-krb5' not found ニニニン Script "configure" failed unexpectedly. Please report the problem to timp87@gmail.com maintainerl and attach the '/usr/ports/uuu/squid/uork/squid-7.1/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system te.g. a /usr/local/sbin/pkg-static into -g -tal. *** Error code 1 Stop. makel1]: stopped in /usr/ports/www/squid *** Error code 1 Stop. make: stopped in /usr/ports/www/squid root@free:/usr/ports/www/squid #"

    it gets so far along and fails with this error.

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

    2k Topics
    16k Posts
    P

    Hi. Is there any way to get Suricata working with the new PPPoE driver (available since version 2.8.0). Unfortunately, after enabling the new driver, Suricata doesn't report any alerts.

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

    571 Topics
    3k Posts
    K

    @pulsartiger
    The database name is vnstat.db and its location is under /var/db/vnstat.
    With "Backup Files/Dir" we are able to do backup or also with a cron.

  • Discussions about the pfBlockerNG package

    3k Topics
    20k Posts
    M

    @Laxarus This worked for me as well. Though I had to search the web how to edit the file (the easiest way).

    Therefore:

    Addition for anyone struggling to find where to edit files on your pfsense system.

    Go to Diagnostics --> Edit File --> insert the location of the file:

    /usr/local/pkg/pfblockerng/pfblockerng.sh

    Go to line number 1232 by filling it in the Go to line field.

    That line should read:

    s1="$(grep -cv ^${ip_placeholder2}$ ${masterfile})"

    replace only (leave the rest intact):

    masterfile

    to

    mastercat

    Then follow the above instructions from @Laxarus https://forum.netgate.com/post/1219635

  • Discussions about Network UPS Tools and APCUPSD packages for pfSense

    99 Topics
    2k Posts
    K

    @elvisimprsntr thanks for your suggestion. I will give it a try.

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

    493 Topics
    3k Posts
    johnpozJ

    @MacUsers

    https://help.zerossl.com/hc/en-us/articles/360060119933-Certificate-Revocation

    edit: oh you prob out of luck

    You can revoke any certificate issued via the ZeroSSL portal. Currently, certificates issued via ACME can not be revoked from inside the portal - please follow the instructions of your ACME client for revoking those certificates.

    the gui in pfsense does not have the ability to revoke - you prob have to move the certs to something you have certbot installed to and revoke that way.

  • Discussions about the FRR Dynamic Routing package on pfSense

    294 Topics
    1k Posts
    R

    I had a similar issue with Routed VTI over IPsec recently. FRR lost its neighbors after rebooting or when a tunnel went down. It never re-discovered it automatically. Only restarting FRR (either in GUI or via CLI) brought the neighbors back.

    When I manually added those under the OSPF neighbors tab in the GUI it seems to solve the problem as well.

  • Discussions about the Tailscale package

    88 Topics
    572 Posts
    A

    We have a very basic configuration between three locations. All are running Netgate firewalls (1x 4100, 1x 6100 & 1x 4200). All are on the latest firmware (03.00.00.01-2Ct-uc-15) and system versions (24.11-RELEASE).

    The local subnets are as follows:
    4100 - 192.168.5.0/24
    4200 - 192.168.4.0/24
    6100 - 192.168.1.0/24

    The VPN traffic between the 4100 and 4200 is functioning 100% as expected

    The traffic between 6100 and the 4100 works going from the 4100 subnet (192.168.5.0/24) to the 6100 subnet (192.168.1.0/24)

    Traffic from the firewall (i.e. the 6100 device) to the 4100 subnet works (i.e. I can ping any device on the 192.168.5.0/24 subnet from the 6100 firewall) but I cannot ping any device on the 4100 (192.168.5.0/24) subnet from any device on the 6100 subnet (192.168.1.0/24) - other than from the firewall itself.

    All routes are correct, but it seems that traffic from the 192.168.1.0/24 subnet hits the firewall and then gets lost - traceroute shows that it goes off into the internet.

    Note too that the 6100 has IPsec VPN configured on it as well

    Suggestions would be appreciated

    Attached is a zipped pdf file with the relevant screenshots
    Relevant screen shots.zip

  • Discussions about WireGuard

    689 Topics
    4k Posts
    P

    @patient0 Yes, have followed that guide and infact have set up quite a few Wireguard tunnels before with no issue. The difference this time is the CGNAT. I am pretty sure its some quirk of the CGNAT that is causing this but still unsure how to diagnose.

    My firewall settings on the tunnel interfaces are correct I think and are the same as I normally use, there is no blockage there.

  • Problem with squid guard target categories

    7
    0 Votes
    7 Posts
    788 Views
    JonathanLeeJ

    @victorrhoden00 reinstall the package remove that file redownload the black list

  • packages do not work after update from pfsense 2.5.2 to pfsense 2.6.0

    14
    0 Votes
    14 Posts
    3k Views
  • wget

    3
    0 Votes
    3 Posts
    230 Views
    P

    @johnpoz Ahh.. Thanks. Will look in to those.

  • Confused with Zabbix

    6
    0 Votes
    6 Posts
    902 Views
    D

    @keyser i think i understood this in the first place, the thing is that from all the videos and the guides that i watched and tried i cant semm to understand where to import the pf sense host to send the data.

  • Syslog-ng Status 10 mins

    3
    0 Votes
    3 Posts
    469 Views
    JonathanLeeJ

    @keyser thank you that fixed it

  • [BUG?] Ram disk breaks ntopng

    Moved
    9
    0 Votes
    9 Posts
    2k Views
    B

    This post is old but for anyone interested, I confirm the issue too: with RAM Disk, ntopng configuration is reset when a "normal" reboot of pfSense occurs (even if Periodic RAM Disk Data Backups is set).

    pfSense v2.7.2-RELEASE package ntopng v0.8.13_10 in pfSense (ntopng-5.6)

    And contrarily to what I read in other posts questioning usefulness of RAM Disk settings, from my limited understanding, I think it's quite useful on my setup: I have a "low cost" box (Beelink EQ12 with a 512Gb SSD). They don't specify the TBW of the disk but I estimated it quite low from SMART health status. After 3 or 4 months of use, SMART indicates disk reached 15% of its lifetime. With 13.1 TB of Data Units Written (raw value 25,742,265), we can approximate the TBW to around 85 TB, which means the SSD is of a very low quality. This does not bother me because I specifically looked for a low cost, "just enough" box for pfSense.
    By comparing SMART measures before and after enabling RAM Disk, I found 3.7/sec vs 0.2 / sec for Data Units Written and 46.2 / sec vs 0.9 / sec for Host Write Commands. I concluded RAM Disk makes a huge difference in my setup. Between RAM Disk and nTopNG, there is no doubt I prefer to keep RAM Disk.

  • 0 Votes
    2 Posts
    811 Views
    JonathanLeeJ

    I know what your thinking, Big deal, I got logs in pfSense,

    But here the issue is, most often you will be running your AP in bridge mode and having pfSense hand out the DHCP addresses, and if your in bridge mode not much info on whats connecting to the NAS internally behind the firewall is ever seen on the firewall logs. This gives you a level of visibility not normally seen within pfSense unless it is configured. Again if you can do it with one AP you can do it with an alias for many APs on a bigger network. This gives you more information into possibile mac spoofing and unauthorized access. If you use remote access and Dynamic DNS for your network, you can see the firewall logs and the AP logs as well.

  • FreeRADIUS cipher_list = "DEFAULT@SECLEVEL=0" (loco M2 client)

    Moved
    3
    1 Votes
    3 Posts
    1k Views
    TechSSHT

    same situation for me

  • Error updating repositories

    6
    0 Votes
    6 Posts
    3k Views
    L

    @aes4096 said in Error updating repositories:

    I solved it using the command certctl rehash

    thx. this saved me from setting up everything from scratch.

    Initially I tried to view installable packages and wondered as the list was EMPTY.
    Then I tried the update process via command line and got multiple errors like:

    pkg-static update

    pkg-static: An error occured while fetching package Unable to update repository pfSense

    pkg-static clean

    pkg-static: Repository pfSense-core missing. 'pkg update' required

    The trick then was to use the debug option: pkg-static -d update
    Here I got an SSL certificate problem: self-signed certificate in certification chain

    solved it with your hint above! Thx

  • Darkstat fails to start

    1
    0 Votes
    1 Posts
    204 Views
    No one has replied
  • How to Decode a pfBlocker-NG Log Entry

    3
    0 Votes
    3 Posts
    457 Views
    R

    @kiokoman Thanks for the reply. This is just buggy app design by the NFL for use on the Roku platform. For now, I will just cast from my iPhone when I want to - that app works without fail. Thanks again.

  • System Patches Package v2.2.9_1

    2
    12 Votes
    2 Posts
    2k Views
    L

    This breaks connectivity from windows terminal openssh which is at OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3 currently in win11.
    No one-click way to get that updated.

    Also putty 0.62 didn't work but the latest 0.80 does work fine from windows.

    Just a heads up.

    /Lars

  • 0 Votes
    1 Posts
    233 Views
    No one has replied
  • unable to list new packages, Unable to update repository pfSense-core

    2
    0 Votes
    2 Posts
    683 Views
    S

    [23.05.1-RELEASE][admin@t]/root: pkg-static upgrade -fy pfSense-repoc
    Updating pfSense-core repository catalogue...
    pkg-static: An error occured while fetching package
    pkg-static: An error occured while fetching package
    repository pfSense-core has no meta file, using default settings
    pkg-static: An error occured while fetching package
    pkg-static: An error occured while fetching package
    Unable to update repository pfSense-core
    Updating pfSense repository catalogue...
    pkg-static: An error occured while fetching package
    pkg-static: An error occured while fetching package
    repository pfSense has no meta file, using default settings
    pkg-static: An error occured while fetching package
    pkg-static: An error occured while fetching package
    Unable to update repository pfSense
    Error updating repositories!
    [23.05.1-RELEASE][admin@nst]/root:

  • Available packages not showing in pfsense 2.7.0 FreeBSD

    5
    0 Votes
    5 Posts
    2k Views
    H

    I encountered another problem with the upgrade, the upgrade to 2.7.1 or 2.7.2 not offered.
    I readed https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html (Repository Metadata Version Errors)
    I solved it in this way:

    From Diagnostics > Command run command: env ASSUME_ALWAYS_YES=yes pkg-static bootstrap -f
    Then Navigate to System > Updates
    Set the Branch to Latest Development Snapshots
    Wait for the page to refresh
    Set the Branch to Latest stable version
    And done!
    Now im running on 2.7.2

    After upgrade The Avaible Packages are displayed.

  • openvpn-client-export 1.9.2 | Viscosity Bundle | ECDSA missing key

    3
    0 Votes
    3 Posts
    395 Views
    S

    @jimp thank you for looking into this ticket.

    Maybe my certs are to old, we can reproduce this on two different systems.

  • HAProxy and RDP

    2
    0 Votes
    2 Posts
    670 Views
    V

    @mpatzwah said in HAProxy and RDP:

    I would like to use for example
    rdp1.mydomain.de connect to 172.30.30.101
    rdp2.mydomain.de to 172.30.30.102
    rdp3.mydomain.de to 172.30.30.103

    I guess, all these host names are mapped to a single public IP. Then how do you think, they could be differed in the RDP protocol?

    When I switch to Type=tcp rdp works but i can´t use the rule "hosts matches" or "host contains"

    Yeah. The host... ACLs target to the host header, which is part of HTTP. Hence it is only available in an HTTP frontend, which is capable to read the header information.

    is there any way to get this working ?

    You shouldn't do a naked RDP connection over the internet anyway.
    So consider to set up a VPN server and go over the VPN, so there is no need use a single IP for multiple RDP servers.

  • PDO library for postgres not found pdo_pgsql

    1
    0 Votes
    1 Posts
    240 Views
    No one has replied
  • Package Manager wont load Available Packages

    11
    0 Votes
    11 Posts
    6k Views
    M

    Suddenly "Available Packages" appeared. Nothing changed here.
    Miracle???

  • 0 Votes
    9 Posts
    12k Views
    astroslugA

    Just adding my experiences onto this issue. TLDR; can confirm that the proposed method worked for me.

    I was seeing not only this issue, but also "Unable to check for updates" in all update-related sections of the Web UI. My update branch was pointing at 2.7.0-RELEASE, but my system was reporting 2.6.0 and the whole system seemed mildly hosed despite still functioning.

    After following the recommendations here by pointing the branch to 2.6.0-RELEASE, then connecting via SSH to bootstrap the package system, I had this:

    /root: pkg bootstrap -f The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: y Bootstrapping pkg from pkg+https://pkg.pfsense.org/pfSense_v2_6_0_amd64-pfSense_v2_6_0, please wait... Verifying signature with trusted certificate pkg.pfsense.org.20160406... done pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible Installing pkg-1.17.5_4... package pkg is already installed, forced install Extracting pkg-1.17.5_4: 100%

    Following that, I tried to run an update via the Web UI, but it said the system is up to date. The branch was now pointing at 2.6.0-DEPRECATED or something like that. I switched the branch back to 2.7.0-RELEASE, and checked for updates via the Web UI again. This time, it looked correct and listed 2.7.0 as an upgrade path. I then carried out a full update. After a nerve-racking 5-minute reboot, pfSense came back online and appears to be operating correctly.

Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.