Subcategories

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

    4k Topics
    21k Posts
    KOMK
    @jucelio_rosa Squid runs on 2.8.1 but there was a library bug IIRC. If you manually start squid then check the system log, do you see this error? The command '/usr/local/sbin/squid -f /usr/local/etc/squid/squid.conf' returned exit code '1', the output was 'ld-elf.so.1: /usr/local/sbin/squid: Undefined symbol "_ZTVNSt3__117bad_function_callE"'
  • 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
    N
    @Gertjan said in is something wrong with pfBlockerNG?: "is something wrong with my pfBlockerNG?". First off, thanks for the detail reply. After my post, I "changed" DNSBL -> DNSBL mode from "unbound python mode" to "unbound mode" and so far i have no issues. I understand what you are saying & hinting "maybe something is wrong with my settings" - my response is this: Everything was working before i upgraded the pfsense software to " 25.07.1-RELEASE (arm64)" -- Before the update my DNSBL Mode was set as "unbound python mode" and everything worked. Here is my "inference" - something broke in pfBlockerNG after the upgrade and I cannot 100% point to what that setting (my) is? I will observe for some days how this change in DNSBL mode works out and report the findings.
  • 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
    642 Posts
    C
    For pfSense+ Version 25.0.7 FreeBSD 15.0-CURRENT: I had a recent issue after upgrading Tailscale to 1.90.4 and afterwards rebooting pfSense. Tailscale would not authenticate. After researching, I found a solution and a suggested workflow for future upgrades. First, I was able to get Tailscale to re-authenticate by executing the following commands (Tailscale Service was offline after the reboot): service tailscaled stop tailscale logout sysrc tailscaled_enable="YES" service tailscaled start tailscale up So that you know, here is the AI-generated one-liner for future upgrades on 25.x FreeBSD 15.0-CURRENT systems. I will test with the next available upgrade package: "service tailscaled stop && tailscale logout || true && fetch https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-X.Y.Z.pkg || exit 1 && IGNORE_OSVERSION=yes pkg-static add -f tailscale-X.Y.Z.pkg && rm -f tailscale-X.Y.Z.pkg && sysrc tailscaled_enable="YES" && service tailscaled start && tailscale up && tailscale version && tailscale status"
  • 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
  • Wake On LAN works but CRON command fails

    6
    0 Votes
    6 Posts
    2k Views
    M
    @Gertjan Thanks for all of your help with this issue. I'm unsure why yours is working when you use the actual ip address of your server in CRON, but mine is not. Because of what I saw in the packet capture, I decided to imitate what the GUI is doing. I changed the command in CRON to: /usr/local/bin/wol -i 192.168.2.255 bc:ee:7b:db:fc:f4 The above command works in CRON to wake up my server. From what you said, I'm guessing this is because "192.168.2.255" is the "broadcast address" of the LAN interface of the $(bcip) as described in your post. /usr/local/bin/wol -i 192.168.2.4 bc:ee:7b:db:fc:f4 The original command above did nothing and didn't even show up in "packet capture" until after the server was already up and running, then I would get something similar to what you got in your packet capture in your screenshot above, as you can see from my previous post. However, the command with the actual ip address reserved for my server in Pfsense fails to wake-on-lan my server, but 192.168.2.255 does work. Thanks for all of your advice and help which resulted in changing "4" to "255" and now it works.
  • 0 Votes
    1 Posts
    457 Views
    No one has replied
  • 1 Votes
    171 Posts
    194k Views
    G
    It's relevant for me too, thank you for explanation
  • 2.6->2.7 PHP Error in status_traffic_totals

    Moved
    2
    0 Votes
    2 Posts
    619 Views
    jimpJ
    That error was probably from when the package was being removed. That particular error has been fixed in the 2.7.0 package for quite a long time: https://redmine.pfsense.org/issues/13775
  • [SOLVED] Unable to Install or Upgrade Packages

    Moved
    44
    1 Votes
    44 Posts
    44k Views
    M
    Just wanted to post as I ran into this issue today. I was able to fix this by submitting a TAC ticket with my NDI and SN. The team found a mismatch in their database to which they fixed, and I was able to update all my packages.
  • telegraf / influxdb | Upgrade to 2.7 issues

    1
    0 Votes
    1 Posts
    603 Views
    No one has replied
  • Is something wrong with arpwatch?

    3
    3
    0 Votes
    3 Posts
    782 Views
    S
    @NogBadTheBad I just did that and it stopped, and i think I know why. Those cams use L2 for discovery. Thank you very much!
  • Where are the configurations of the various packages?

    5
    0 Votes
    5 Posts
    2k Views
    GertjanG
    @darkcorner You said in the other thread : @darkcorner said in Network access blocked after update: that I now have to configure from scratch.. That's a 'noop' ;) When you remove all ('big') packages before upgrading, the upgrade process goes much faster. When you have a copy of that config.xml file, right after the upgrade and reboot, you should import config. All packages that are marked as "installed and configured" in the config file will get downloaded, installed and configured. A final reboot and you're ok. Nothing to reconfigure - with the exception : if there are new options, you should check these packages and make your config choices.
  • radtest not found / Problems with FreeRadius

    9
    0 Votes
    9 Posts
    2k Views
    johnpozJ
    @abuttino said in radtest not found / Problems with FreeRadius: grr, was using the wrong pfSense server. not sure why that should matter running the pkg command, I could see it not having freerad installed as to why radtest not there. But the pkg command? Maybe that just generic sort of error since that pfsense didn't actually have the radtest file because freerad was not installed.
  • LCDProc (/dev/cua1) failed (No such file or directory)

    6
    3
    0 Votes
    6 Posts
    2k Views
    S
    @elvisimprsntr said in LCDProc (/dev/cua1) failed (No such file or directory): @sebr Looks like the Peplink Balance series LCD displays have the ST7066U (or compatible) LCD controller. http://lcdproc.omnipotent.net/hardware.php3 [image: 1685199430941-screenshot-2023-05-27-at-10.55.49-am-resized.png] Is there a /dev/lpt0 port listed? If so, you might try the following: Com port: (/dev/lpt0) Driver: HD44780 and compatible Connection type: Likely 4bit or 8bit, but try each until you find one that works. If not, then it might be connected to a serializer chip, thus /dev/cua* Thanks for your help, I'll go back and test this.
  • FreeRadius with Windows Active Directory

    4
    0 Votes
    4 Posts
    2k Views
    D
    @Gertjan said in FreeRadius with Windows Active Directory: You are using "PAP authentication" ? Should FreeRadius work with Active Direcroty throught NPS Radius or as LDAP autorization? i think it work as LDAP, as there are Base DN Filter and Base Filter attributes. i have configured in pfsense LDAP authentification to web page and there are also Base DN attributes thats why i think it works not throught NPS. Here is my LDAP web authentification Spoiler [image: 1695206363091-e1799302-4e6d-427f-8032-f2001e496b0f-image.png]
  • Snort is blocking gmail attachment download randomly.

    2
    1
    0 Votes
    2 Posts
    529 Views
    bmeeksB
    Find the rule that is false-positive triggering on your Gmail downloads and disable it. To do that you will need to cross-reference IP addresses in your alerts shown on the ALERTS tab. None of the alerts you are showing in your screenshot appear relevant to Gmail.
  • ntopng errors in system log

    5
    0 Votes
    5 Posts
    2k Views
    A
    Sorry, i have the same issue. Any fresh ideas?
  • System Patches package version 2.2.5

    17
    7 Votes
    17 Posts
    5k Views
    jimpJ
    Any further questions about the change in 2.2.6 should go over in the new thread: https://forum.netgate.com/topic/182725/system-patches-package-version-2-2-6
  • System Patches package version 2.2.6

    1
    6 Votes
    1 Posts
    2k Views
    No one has replied
  • Zabbix Agent 2 - Monitor pfSense CPU Temperature

    1
    0 Votes
    1 Posts
    423 Views
    No one has replied
  • HAproxy-devel issue

    3
    0 Votes
    3 Posts
    1k Views
    E
    I know this is an old thread, but it is the only one that matches the issues I have had over past 2 days. I have latest version fully updated pfsense and packages. I was running HAProxy Devel. Again fully up to date (as of 06/09/2023), given dates as I am unsure what versions. All of a sudden our RDS users were not able to open applications. In our setup we have a RDS Gateway, people log into the HTML5 interface for RDS, then they open an app in browser. Accessing and loggining into the HTML5 interface worked fine and always worked, even with fully updated. But when you tried to open an app, it would fail to open. After messing about for a bit, I accidently forwarded 443 to the RDS gateway, and everything was working. Once I learnt this, I had to put 443 back to HAProxy as our intranet was no longer working. WIth this information, I knew it was something to do with HAProxy not handling the connection correctly. So I uninstalled HAProxy Devel, and installed HAProxy package 0.63_1. Now everything is working perfectly as it has been for years. I know its been some time since this thread was made, but what ever that problem ended up being, its happening again. Something is wrong with HAProxy Devel.
  • I did not install these packages

    2
    1
    0 Votes
    2 Posts
    689 Views
    johnpozJ
    @pV5 those are the extra packages that pfsense + gets.. Yeah they would be there by default
  • DNS Error updating packages

    1
    0 Votes
    1 Posts
    354 Views
    No one has replied
  • HAProxy broke after update to pfs 22.05

    4
    0 Votes
    4 Posts
    3k Views
    S
    i had this issue, solved it after changing "httpforclose" to "httpclose" as the new version doesn't support that old config var, perhaps dev can do some some parsing magic? lucky the error code lead me to this
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.