Subcategories

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

    4k Topics
    21k Posts
    J
    @JonathanLee use Pfsense 2.8.1.
  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    DARAD
    Hello team, I have a Netgate 8200 running 24.11-RELEASE (amd64) with Suricata 7.0.8_5 package installed. Suricata doesn't seem to start. It loops to red once I press the Play button on the interface. It leaves no logs in the System logs, it leaves no logs in suricata.log at /var/log/suricata/suricata_ovpns933787/suricata.log I tried launching it manually: # /usr/local/bin/suricata -V or # /usr/local/bin/suricata -c /usr/local/etc/suricata/suricata_33787_ovpns9/suricata.yaml -i suricata_ovpns933787 and I get this output ld-elf.so.1: /usr/local/bin/suricata: Undefined symbol "__strlcpy_chk@FBSD_1.8" Thanks in advance, Dara
  • 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
    tinfoilmattT
    @vicking said in No blocks on IP: Is it a bad idea to have the action set to deny both instead of inbound only? Question is squarely for admin. Per the infoblock which explains, in part, the "Deny Inbound", "Deny Outbound", and "Deny Both" actions: 'Deny' Rules: 'Deny' rules create high priority 'block' or 'reject' rules on the stated interfaces. They don't change the 'pass' rules on other interfaces. Typical uses of 'Deny' rules are: Deny Both - blocks all traffic in both directions, if the source or destination IP is in the block list Deny Inbound/Deny Outbound - blocks all traffic in one direction unless it is part of a session started by traffic sent in the other direction. Does not affect traffic in the other direction. One way 'Deny' rules can be used to selectively block unsolicited incoming (new session) packets in one direction, while still allowing deliberate outgoing sessions to be created in the other direction. In other words: When set to "Deny Inbound", incoming connection requests from WAN hosts are blocked and therefore no state will be created. However a LAN host can still establish state to an otherwise listed IP. If set to "Deny Outbound", outgoing connection requests from LAN hosts are blocked and therefore no state will be created. However an incoming connection request from an otherwise listed IP to an 'open' WAN port can still establish state. If set to "Deny Both", both incoming connection requests and outbound connections requests are blocked and therefore no state will be created regardless of connection direction.
  • Discussions about Network UPS Tools and APCUPSD packages for pfSense

    102 Topics
    3k Posts
    C
    @dennypage Nicely done sir!
  • 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
    654 Posts
    C
    @luckman212, Thanks for your suggestion. I will check what I have in /usr/local/pkg/tailscale/state, and also the RAM disk settings others have brought up. I could learn more about where Tailscale and pfSense store system files. If I find anything worth sharing, I will let you know.
  • Discussions about WireGuard

    715 Topics
    4k Posts
    H
    @RNM-0 Thanks for your comment and sharing your fix. Unfortunately I don't want to take down pfsense and downgrade versions. I'm currently fine at the moment since I'm using Tailscale and that works. I also fixed the other crash I was having with pfblocker by changing a line code that wasn't pushed out under this version. Hopefully the stable release won't take too long to release but it appears there's still some open bugs that need to be fixed before that happens, and ironically, both the pfblocker and wireguard issues aren't on that list of bug fixes.
  • Zabbix Proxy?

    1
    0 Votes
    1 Posts
    424 Views
    No one has replied
  • After the last update pfsense 2.4.4 p3

    Locked
    12
    0 Votes
    12 Posts
    1k Views
    johnpozJ
    @jimp said in After the last update pfsense 2.4.4 p3: pf2ad Maybe he didn't pay his 60.00 € the guy wants for that package... That site is OLD... shoot it still says pfsense is owned by Electric Sheep Fencing ;)
  • This topic is deleted!

    0
    0 Votes
    0 Posts
    12 Views
    No one has replied
  • softflowd: multiple collectors

    1
    1 Votes
    1 Posts
    270 Views
    No one has replied
  • Snort and SquidGuard issues

    1
    0 Votes
    1 Posts
    346 Views
    No one has replied
  • 0 Votes
    9 Posts
    701 Views
    K
    I think I figured this out by installing pfsense in virtualbox VM, configuring it and then comparing pkg info commands between it and my live system. The live system always had a warning about pkg version 35 is newer than installed database 34 at the top, and there were a few other packages that were newer versions than the stock 2.4.4p3 system. The pkg version warning did not sit pretty with me so thats when I decided to blow away this new install and start over. After I wiped the drive and did a reinstall, I reapplied my config file. The interfaces were different from the old system (re0, igb0). Therefore until I got to the physical console and fixed it, the packages never installed because it could not contact the internet. The second time around I edited my xml config file in notepad++ and altered the WAN and LAN with the proper igb0 and igb1 designations as they are on the new box. Next wipe I got it back up and restored config. This time since the interfaces were correct, when it restarted it had internet access and the system was able to automatically reach out and download all of the packages. At the top of the web ui in a yellow banner it said to hold off on any changes while packages are reinstalled from the internet. (This is the behavior I noticed in my VirtualBox install test). The only one I had to manually install was bandwidthd (it was in the menu but the package wasn't installed). But after giving the system time installing all of these packages, I was able to install the Unifi controller using the github script. I then pkg lock these three packages: boost-libs-1.71.0_2 icu-65.1,1 mongodb34-3.4.23 I then installed the command line packages for lsof and nano, and they installed and work without issue. Nothing was downgraded or removed. System is running smoother than it ever has. I think the pkg database got messed up in the original install after importing the config, since the system was not able to contact the internet and complete the package install. There was no button in the UI to "retry" and reloading the config and just choosing package database did not seem to do anything. A clean install fixed it.
  • Pfsense 2.4.3 Freeradius 3.x ldap problem

    2
    0 Votes
    2 Posts
    645 Views
    M
    @magokbas said in Pfsense 2.4.3 Freeradius 3.x ldap problem: With the same settings as FreeRadius2, FreeRadius 3 ldap (active directory) don't work. when activate ldap is did not work sql. sql started to work after last update but ldap still does not work. This problem still persists.
  • FreeRadius - Wifi auth with PWD and TTLS

    1
    0 Votes
    1 Posts
    921 Views
    No one has replied
  • SIProxd registrations not releasing.

    1
    0 Votes
    1 Posts
    266 Views
    No one has replied
  • Snort 4.0_8

    2
    0 Votes
    2 Posts
    433 Views
    bmeeksB
    @cdx304 said in Snort 4.0_8: Snort does not want to start again .Was working fine ? Pfsense is latest 2.5 build . I assume you mean Snort 4.0_8 has been working for you and then just suddenly started not working. If so, then read on. This is almost always caused by a rule syntax error (or could be a required preprocessor is not enabled). Look in the pfSense system log and you should see a Snort error message that will tell you what's wrong. When the rules update (usually twice each week) it is entirely possible for either a rule to be published or updated and have a syntax error in it, or a rule that was previously default-disabled by the Snort team might have been changed to default-enabled by an update. If that particular rule need a preprocessor enabled that you have disabled, that can result in a startup failure. So check the pfSense system log to see why Snort is not starting. Post back here if are not able to identify the cause.
  • Antivirus on pfsense

    1
    0 Votes
    1 Posts
    344 Views
    No one has replied
  • Freeradius with remote mariadb server

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • What is the status of ARPWATCH package?

    10
    1 Votes
    10 Posts
    2k Views
    G
    @vw-kombi said in What is the status of ARPWATCH package?: I recently had to delete and re-create a vpn ouotbound connection, and arpwatch did not like this. In addition to the usual mesages, I am getting this with every cron execution - the interface mentioned in the email I get below does not exist anymore. It is not mentioned in the xml if I do a backup and edit either - I assume its in some sort of arpwatch database, but no amount of uninstalling and re-installing seem to rectify this email every 5 minutes : X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin> X-Cron-Env: <HOME=/root> X-Cron-Env: <LOGNAME=root> X-Cron-Env: <USER=root> Error: Unable to get interface "ovpnc3" statistics. I don't know anything about the inner workings of pfSense, but is it possible that this is causing an interface to become visible/invisible, and arpwatch is "just doing it's job" in alerting that a "device" has appeared on the network (and not been marked as an allowed device), disappeared, and then reappeared. Every tine the device comes back, it generates an alert, and unless there is some way to mark the MAC address as "allowed" this behaviour will never stop. Just a thought, I don't know if it has any merit.
  • [SOLVED] Bug while updating System_Patches

    7
    0 Votes
    7 Posts
    2k Views
    EveningStarNME
    @jimp Thank you, and to everyone else who replied here, too. I uninstalled v1.2_2 and installed v1..2_3, and everything worked as expected.
  • Adding to the user fields in Freeradius

    1
    0 Votes
    1 Posts
    337 Views
    No one has replied
  • Snort Rules in pfsense always failed

    4
    2
    0 Votes
    4 Posts
    701 Views
    bmeeksB
    Not that it really should matter in terms of starting up, but you apparently have no rules selected for your LAN interface. That means Snort would not be really doing anything for you even if it started. At 10:11:19 in the log is a warning about "no text rules or IPS Policy selected for: LAN". Your Snort Subscriber Rules are also failing to download. Notice the "Server returned error code 505" message in the log at 10:10:28. The most likely cause of that is a trailing space in your Oinkcode. Retype or paste in your Oinkcode again and be sure that is no trailing space at the end and that every character is correct. So from the log, Snort appears to have started successfully. Does it still not show as running? Open a CLI (command line interface) session on the firewall either directly on the console or via an SSH connection and see what the output of this command is -- ps -ax | grep snort Do you see any running Snort processes in the output of that command? I also see a Gateway Alarm message in the log. If that happens often and if the gateway monitoring logs a "gateway down" message, that will trigger pfSense to issue a "restart all packages" command. If more than one instance of that happens in rapid succession it can result in the Snort process either getting clobbered, or sometimes, two duplicate Snort processes getting started.
  • Iperf version

    Moved
    12
    0 Votes
    12 Posts
    1k Views
    jimpJ
    That was just a cosmetic issue and is corrected in the repo, so when the next build happens, it will be fixed.
  • SquidGuard on pfSense 2.4.4: Segmentation Fault (core dumped)

    2
    0 Votes
    2 Posts
    649 Views
    KOMK
    Remove squidguard and then try to get squid working alone first. If it still dies, check the System log for anything related.
  • Possibly a broken pkg database

    1
    0 Votes
    1 Posts
    262 Views
    No one has replied
  • Freeradius with Unifi wifi setupd guide?

    9
    0 Votes
    9 Posts
    4k Views
    johnpozJ
    Yeah would be nice to have an option.. My controller runs all the time, and wouldn't call it major ;) You should be able to pick, or even have option of say if controller is offline the AP sends..
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.