Subcategories

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

    4k Topics
    21k Posts
    JonathanLeeJ
    @firefox That is weird did you just try this or have you used it in the past?
  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    M
    Hi, I had a problem with my home network today, so I checked pfsense and discovered that suricata had blocked the wan ip. After some tests and triggering some suricata alerts, the wan ip was blocked. I restarted pfsense and ran some more tests, but the problem no longer occurred. I then checked the wan interface settings and indeed the ip list does not include the wan ip, both now that it's working and before, when it was blocked. I'm using pfsense 2.8.0 and suricata 7.0.8_2. I use PPPoE to access the Internet.
  • 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
    Ran into this issue today as well running on 25.07.1 with pfblockerNG-devel 3.2.7. Followed the steps outlined in this thread to edit the pfblockerng.sh file, then deleted/force reloaded all the lists, and all was well again. Thank you everyone in this thread for your your help and great instructions.
  • 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

    496 Topics
    3k Posts
    R
    @provels said in updating to acme 1.0 breaks system beyond repair: need to restore from backup: This same mess happened to me, even w/o Acme, going from 25.07 to *.1. Blew, reinstalled w/ Crowdsec, blew again, reinstalled, clipped all the Crowdsec info from config.xml, restored config, back to normal. Crowdsec is a great concept, but I think I'm out. I never had this issue with Crowdec before the ACME update, even with updating from 2.7 to 2.8 there was no issues. In fact after restoring from a backup after the ACME update, Crowdsec reinstalled just fine, and this was before the recent release a couple days ago that contained a fix.
  • 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
    603 Posts
    W
    @totalimpact in my case I dsid not reboot the router, after I copied the new key tailscale went online.
  • Discussions about WireGuard

    697 Topics
    4k Posts
    H
    I figured out the issue. I missed adding the 3rd locations Lan to the static routing. Now all is working perfect.
  • HAVP + Squid + SquidGuard = Slow??

    6
    0 Votes
    6 Posts
    3k Views
    O
    Hi, I made the changes in Dns Forwarders, but without any good results, the pages are still slow opening. Any advice ? Thank you
  • Squid + Dansguardian issue

    33
    0 Votes
    33 Posts
    8k Views
    L
    Just thought I'd report back. I  did a wipe/rebuild and everything is working as expected.
  • Snort - VPN - P2P-ruleset

    2
    0 Votes
    2 Posts
    1k Views
    X
    Yep, happened to me. Well the vpn wasn't blocked because I have the remote host added to the $home_net, but it was triggering an alert. 1:2003310 ET P2P Edonkey Publicize File
  • Squid caching alternative

    2
    0 Votes
    2 Posts
    1k Views
    K
    If you install the "Proctor Caching" software you will see that it is just Squid for Windows repackaged with a web framework that provides a user interface for the online testing. Once you install the Proctor Caching software you could edit the conf file: C:\ProctorCache\squid\etc\squid.conf And point it to your pfsense box IP address and port. Stop and Start via the .BAT files and you should be good. This way you can still use their software and your pfsense box together. You will be caching on two levels though. Hope this helps.
  • Squid3 reverse proxy config (HTTPS not redirecting)

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Reset Package Configuration (DansGuardian)

    3
    0 Votes
    3 Posts
    1k Views
    marcellocM
    Remove the package and then remove dansguardian config from config.xml. You can do it by editing a backup file or directly with viconfig cmd on console/ssh. On both cases, be careful.
  • HAProxy forwardfor trouble

    4
    0 Votes
    4 Posts
    4k Views
    P
    Hey Aviz, When using "mode tcp" haproxy cannot modify headers send through the encrypted SSL connection. You only option when needing to modify https traffic would be to switch to the haproxy-devel package and configure a certificate to perform ssl-offloading/decryption on haproxy, and then modify headers before sending to the backends. You can choose whether or not you want that backend connection to be encrypted again. Which might be required for the application to work properly, though plain http to the backend would take less CPU power. (You might also accomplish this with putting 'stunnel' in front of haproxy 1.4.. But i would not recommend that..) Another option when using haproxy-devel would be to use its transparent client-ip option. So the backend sees the connection coming in from the actual client-ip.. Please note that backend then 'must' use pfSense as a default-gateway for reply traffic to be properly processed by HAProxy. And that connections directly to the backend will fail with the current 'fwd' rules used in ipfw.. Greets PiBa-NL
  • Dansguardian 2.12.0.3_2 does not work

    25
    0 Votes
    25 Posts
    5k Views
    R
    @marcelloc: @rjcrowder: something definitely got broken in the 2.12.0.3_2 version of the package. That's the official version from ports compiled by core team, the code doesn't have some patches @rjcrowder: At any rate… the workaround seems to be installing the 2.12.0.3 version from your repository... I'm trying to port e2guardian to freebsd and then pfsense. As I said, dansguardian is no longer being updated by maintainers on sourceforge. Many commits are pending. AFAIK, e2guardian will not have use restrictions as dasnguardian has. The gui will be almost the same, just the package name will change. If core team aproves, it will be applied to pfsense 2.1 Very nice… I'll look forward to that... Thanks again Marcello
  • Bandwidthd breaks pfS RRD Graphs (Traffic, Packets)

    3
    0 Votes
    3 Posts
    1k Views
    C
    Haven't seen that. Any RRD-related errors in the system log?
  • Ipguard with pf 2.1.2

    3
    0 Votes
    3 Posts
    848 Views
    N
    @marcelloc: @N3w4dm1n: For now its not compatible to the last version of pf. Will it be supported next time? What errors are you getting? i click start service. nothing happens, i gues i have to check package logs. ill do monday at work!
  • 2.1.2-RELEASE Defaulted sip.conf and extensions.conf ASTERISK

    1
    0 Votes
    1 Posts
    676 Views
    No one has replied
  • Squid3-dev stops at midnight

    1
    0 Votes
    1 Posts
    527 Views
    No one has replied
  • Open-VM-Tools 8.7.0.3046 (build-425873) cannot install on pfSense 2.1.2

    3
    0 Votes
    3 Posts
    924 Views
    S
    Thanks, but how about the Open-VM-Tools? Aren't they supposed to work with pfSense 2.1.2?
  • Squid and Windows 7/8 browser authentication (negotiate)

    5
    0 Votes
    5 Posts
    1k Views
    J
    Thanks Marcello, I'll have a look at that. :)
  • Newbie Question Regarding SNORT and Interfaces

    2
    0 Votes
    2 Posts
    1k Views
    bmeeksB
    @SMuD: I'd like to install SNORT on my pfSense firewall to monitor packets that get through our WAN interface. I am not interested in the traffic that reaches our WAN but is not allowed in - I want to monitor what makes it inside, after the firewall has parsed the packet. Does this mean that I should enable snort on the LAN and OPT interfaces rather than the WAN? Since we want to monitor the traffic that is allowed into our network should I enable SNORT on the WAN at all? Thanks! Snort puts interfaces it monitors in promiscuous mode, so you are right that it would see and alert on ALL traffic hitting your WAN interface whether the firewall passed the traffic or not.  So putting it on an internal interface is better in my opinion.  This way Snort only inspects what the firewall allowed to pass.  This filters out a bunch of noise.  Another added benefit of having it on the LAN (or other internal interface) is it sees traffic pre-NAT and post-NAT, so you can see the actual internal hosts that may be malware-infected and are attempting to communicate outbound.  Running it only on the WAN means the only local IP you ever see in the logs is the WAN interface IP.  If you don't use NAT, then that is not an issue; but most folks do use NAT and seeing only the WAN IP for all local hosts behind the firewall is not very helpful. If you run Snort on multiple interfaces, then in the name of memory efficiency and CPU workload, I suggest tailoring the rules for the environment behind Snort.  By that I mean if you don't have mail and web servers on your LAN, then don't run those rule sets on the LAN.  Same idea if you don't have DB servers back there.  You choose the rule sets appropriate for the hosts.  But if you have a monster firewall with a ton of RAM and a beefy CPU, you can certainly load it up with all of the rules on all of the interfaces. Bill
  • Freeradius, mOTP and bash

    3
    0 Votes
    3 Posts
    2k Views
    N
    Hi, the freeradius motp features is based on a script - modified for pfsense - from http://motp.sourceforge.net/ The script is written for /bin/bash but this is not the default shell for pfsense so you need an additional package "bash". So there are two possibilities: 1.) Modify the function "function freeradius_motp_resync()" in freeradius.inc starting on line 3897 2.) Rewrite the motp script from /bin/bash to work on the pfsense default shell (recommended) There is a check on this part - if someone enabled mOTP feature on GUI the the package checks if bash is installed but it only checks on a specific version. If it ist not installed it installs bash. If it is installed and mOTP is still enabled it skips the installation. If you disabled mOTP bash will be uninstalled. So bash does not come with the freeradius2 package but it installs later if mOTP is enabled. This is for sure not an elegant solution. PS: if you download bash manually then you can try to just comment out the lines on feeradius.inc which do the check and installation of bash package.
  • Netgate FW-7541 - some packages outdated

    5
    0 Votes
    5 Posts
    1k Views
    P
    I see you edited my link from https://www.pfsense.org to https://packages.pfsense.org It doesn't work with https://packages.pfsense.org, it only works with https://www.pfsense.org. I just tried it again….
  • Inconsistent behavior with Siproxd

    1
    0 Votes
    1 Posts
    671 Views
    No one has replied
  • Bacula-fd looks in the wrong path for config file

    1
    0 Votes
    1 Posts
    754 Views
    No one has replied
  • Reverse Proxy RPCoverHttp Exchange 2013

    8
    0 Votes
    8 Posts
    4k Views
    E
    Thanks to keyser, we have try it in our environmet. And HAproxy works for us to.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.