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
    604 Posts
    M
    Hi all, I wanted to share that I’m also experiencing issues with Tailscale (v1.86.4) on the latest pfSense CE (v2.8.0). After either a pfSense reboot or a Tailscale service restart, my node is logged out of Tailscale — exactly as many of you have described here. It bothered me enough that I opened a support ticket with the Tailscale team. I explained the problem, included details, and linked this thread as a reference. The good news is that support responded quickly and said they’re setting up a pfSense VM to reproduce the issue. In the meantime, they suggested a workaround: “Based on the behavior described here and in the thread, it looks like the auth key used for authentication may be expiring. Since OAuth clients don’t expire, switching to an OAuth Client rather than an Auth Key might resolve this. See our docs here: https://tailscale.com/kb/1215/oauth-clients#registering-new-nodes-using-oauth-credentials I tested this, and after configuring Tailscale with OAuth, everything worked! Tailscale now stays connected and authenticated even after a reboot or service restart. That said, I did tell support that while OAuth solves the issue, it used to work out of the box with the simpler interactive login / auth key flow. Something seems to have changed on the Tailscale side, and I hope they identify and fix it. But until then, the OAuth workaround is a solid fix. I’d love to hear how it’s working for the rest of you. Anyone else try OAuth yet? Cheers
  • 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.
  • Snort with all my rules enable not starting

    7
    0 Votes
    7 Posts
    2k Views
    bmeeksB
    @simby: Any help, sugestion? or where is snort config file? Post any Snort messages from the system log. I suspect you need to enable one or more per preprocessors if you have enabled every single rule. Depending on the power of your hardware, it can take Snort up to a minute or more to start up if you enable all the rules.  Are you sure you are waiting long enough? By the way, it is never a good idea to enable and run all the rules. You will likely get a lot of false positives.  You should pick only the rules necessary to cover your environment.
  • NTOP

    2
    0 Votes
    2 Posts
    928 Views
    S
    I had some issues as well. But after a re-install all started working for me. I also saw an issue where it was not working with firefox and only with chrome. Have you try a different browser?
  • RRD Graphs with Captive Portal

    3
    0 Votes
    3 Posts
    1k Views
    K
    See here http://forum.pfsense.org/index.php/topic,66745.msg367763.html#msg367763
  • Reverse-Resolving IP to Domain Name, Then Blocking?

    5
    0 Votes
    5 Posts
    2k Views
    E
    @jimp: They block it by forward resolution, not reverse. OpenDNS sees the DNS query for www.badplace.com, and returns a record that sends the client somewhere else or nowhere at all. They don't block things by IP and they never see a host record in the query, it's all in DNS (sort of like the DNS proxy I described) Ah, that makes sense! Hmm… That (I would think) would be much easier than using Squid's method of doing it. Just force clients to direct their DNS queries through pfSense, compare the URLs to a blacklist, and return the IP address of a block page, rather than screwing with certificates and stuff... Do you know of any free solutions outside of pfSense that do this? I'm looking around for one, and haven't seen one yet.
  • Joomla behind pfSense

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Help:In 2.1 ,the snort's blocked is automatically cleared

    3
    0 Votes
    3 Posts
    1k Views
    bmeeksB
    I discussed this with one of the pfSense Core Team members.  He acknowledged this is caused by the filter_reload() function in 2.1 and some changes within it.  He has this on his list to look at fixing.  That's the good news.  The bad news is since this is something in the core code and not in the Snort package, it will take a longer time to work its way into the patch update process. Bill
  • Squidguard-devel 1.5

    2
    0 Votes
    2 Posts
    3k Views
    jimpJ
    The squidguard-devel PBI should be up now.
  • Squid Not Working after upgrade to 2.1

    4
    0 Votes
    4 Posts
    2k Views
    C
    I looked at the squid config and did not see anything unusual ( I am not a squid expert though). The rebooting solution seems to be working. It has been running for about 2 hours without an issue. Now I see that the RRD graphs do not show the captive portal data. On to the next issue. Thanks for the solution.
  • Unbound 1.4.20_8: fix for IPv6 host overrides

    2
    0 Votes
    2 Posts
    923 Views
    D
    I've added this information to bug #3056 on redmine.
  • Can't reinstall squid3 after upgrade from 2.0.3 to 2.1

    2
    0 Votes
    2 Posts
    1k Views
    I
    Hi! I also had problems with squid3 after upgrade from v2.0.3 to v2.1 release I got error that the package didn´t install correctly after upgrade. In menu "Installed packages" the squid3 package was not listed. First tried to install without reboot but it didn´t work. Uninstalled the package from menu "Installed packages" and rebooted. Installed package again with success. Rebooted again to check if the package started. Now I have the squid3 package up and running. /illern. Running v2.1 Release full install (i386)
  • Squid + Captive Portal = not logging usernames?

    10
    0 Votes
    10 Posts
    4k Views
    marcellocM
    Translate this one from Portuguese forum http://forum.pfsense.org/index.php/topic,66809.0.html
  • Pfsense, varnish & port 80 - can i do this?

    6
    0 Votes
    6 Posts
    3k Views
    marcellocM
    Test.html csn be the same on all servers and can return anything as varnish check http code (200 ok) Change Firewall rule to source any destination wan address port 80.
  • Snort 2.9.4.6 Pkg v 2.5.9

    203
    0 Votes
    203 Posts
    115k Views
    bmeeksB
    @maverick_slo: Hi! snort-2.9.4.6.tbz is June version on the link u posted? Regards, M UPDATE #2 (9:22 AM September 28):  The updated Snort binary for 2.0.3 pfSense installs is now available in the files repository. UPDATED INFO (9:30 PM September 27):   I received a note back from the pfSense guys.  There are some issues with getting the 2.0.3 binary packages rebuilt.  The issues are generic with the Ports tree and not specific to Snort.  It could be later this weekend or even early next week before the 2.0.3 binaries get rebuilt.  If you have a 2.1 install, you are golden because the PBI packages are good to go. If you want the new Snort GUI fixes, then go ahead and reinstall the Snort package now.  Just click the PKG or XML icons.  They both will do the same thing in terms of reinstalling the GUI PHP code.  I will post back later when the new Snort binaries for 2.0.3 pfSense are built and posted. **Original Post follows –- ** Yeah, I think maybe those rebuild overnight.  I will e-mail the Core Team guys and have one of them check it out.  The new binary is not a huge deal, but if you use the SMTP preprocessor and sometimes saw the message about "SMTP:  changing file_depth requires a restart", then the updated binary will fix that (and allow Snort to soft-restart correctly). It won't hurt anything to do a package reinstall by clicking the PKG or XML icon, then later when the new binary is posted you can do the remove and re-install then.  The major bug fixes and new features are all in the GUI code anyway. Bill
  • Using Squidguard + Dansguardian?

    2
    0 Votes
    2 Posts
    2k Views
    T
    Dansguardian will do ACLs as well. What, specifically, do you wish to achieve with Squidguard that you don't believe you can't with Dansguardian?
  • TunnelStateData

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Snort Menu

    1
    0 Votes
    1 Posts
    864 Views
    No one has replied
  • Ifstated or similar

    1
    0 Votes
    1 Posts
    773 Views
    No one has replied
  • 0 Votes
    6 Posts
    2k Views
    N
    Yeah… that's what I've did... Though the other way looked much simpler. C'est la vie.
  • SquidGuard Time Restrictions not working ?

    2
    0 Votes
    2 Posts
    2k Views
    G
    I found this topic http://forum.pfsense.org/index.php?topic=59671.0 and i execute``` /usr/local/sbin/squid -k reconfigure Time restriction are now applied and it's working as expected : i created some schedule 09:00-09:10, 09:20-09:30,  09:40-09:50 transitions are working. a bit strange right ?
  • No packages with logging facilities..

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.