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.
  • Captive portal - is it me or is this product not ready?

    3
    0 Votes
    3 Posts
    883 Views
    bmeeksB
    Hi Miles: I'm not a captive portal user or maintainer, but there is a dedicated forum for it here:  https://forum.pfsense.org/index.php?board=2.0 Someone in there might be able to help.  You may have tried there already, and if so just ignore this post. Bill
  • Trying squid but can't even block a domain

    1
    0 Votes
    1 Posts
    610 Views
    No one has replied
  • PfBlocker Alias log problems

    4
    0 Votes
    4 Posts
    1k Views
    BBcan177B
    @splmachine: That rule was exactly what I needed, Thanks. Now I can match up rule number with the actual rule. One last thing though, looking in the log settings I have raw logging enabled, and most of the options enabled. Is there a way to have the logging show pfBlockerAliasName vs something like "Rule 50"? Or is that it? Is Rule 50 one of the Default rules or a pfBlocker Rule? If its a Default rule it will just show the Rule Number. You would most likely leave these three off. Especially the first one as you will get a lot of noise. Log packets blocked by the default rule   Log packets blocked by 'Block Bogon Networks' rules   Log packets blocked by 'Block Private Networks' rules One thing to remember is that if you modify a Rule, it will change the Rule Names in the Firewall log (all will be mismatched). This will hopefully be fixed in 2.2
  • Squid3-dev causes Fatal error: Call to undefined function curl_init()

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Postfix disabled on pfsense upgrade…why?

    2
    0 Votes
    2 Posts
    751 Views
    marcellocM
    The service is disabled during uninstall/reinstall.
  • NRPE dont_blame_nrpe=1

    1
    0 Votes
    1 Posts
    718 Views
    No one has replied
  • Captive portal auth page

    2
    0 Votes
    2 Posts
    603 Views
    M
    File manager.  Great.
  • Captive portal vouchers

    1
    0 Votes
    1 Posts
    688 Views
    No one has replied
  • LightSquid Problem

    2
    0 Votes
    2 Posts
    689 Views
    S
    yesss, for next refers,it was a simple mistake by me,just select lightsquid>setting>Report Scheme (something other than Text) :D [image: 222.PNG] [image: 222.PNG_thumb]
  • Nmap-6.40_2 pkg v1.2 - Failing to Install

    6
    0 Votes
    6 Posts
    2k Views
    K
    No worries, upgrading to 2.1.3 has fixed the issue. Must have been something that got changed in the package or the package system. Thanks! Edit: Not sure if it matters, but the error message said something pertaining to a missing nmap.inc, install failed, then the install would gracefully back out and perform the nmap uninstall, removing all nmap components. If I can get the exact error message from an un-updated install I will before I update it.
  • Suricata package blocking mode coming soon

    16
    0 Votes
    16 Posts
    4k Views
    bmeeksB
    @BBcan17: Great stuff… This will make testing that much easier!! EDIT: On another note, also having the functionality to create a fresh NEW interface would also be beneficial instead of trying to re-enable all of the previously disabled rules. That functionality is there today with the current (+) icon.  I'm not changing that one.  I will be adding new (+) icons beside each configured interface.  Clicking the (+) beside an already configured interface will perform the DUP function.  The layout will be pretty much just like the firewall rules page.  So the (+) icon at the top right of the tab will create a new fresh interface (just like it does today).  The (+) icon beside an existing configured interface will DUP it. In terms of the rules, on the RULES tab today is an icon that will remove all forced enable/disable changes for all rules on the interface.  This essentially resets the rules to their default state.  There is a similar icon that will do this for only the currently selected category. Bill
  • Suricata - MM/DD/YYYY Log Entry Formating

    4
    0 Votes
    4 Posts
    1k Views
    bmeeksB
    @priller: Not "alerts.log" …... "suricata.log".  It uses a different date format from all the other logs. suricata.log 3/5/2014 -- 14:37:21 To match the other logs that should be 5/3/2014, or more specifically 05/03/2014 .  Today being 5/5, it's a bad day to compare the different formats!  ;D alerts.log 05/01/2014-02:38:47.669925 http.log 05/03/2014-17:40:37.873931 tls.log 05/02/2014-07:39:35.069581 Oh…sorry, I understand now.  I will look again in the config docs, but I don't think there is any way to change that outside of editing the actual binary source code.  I can see how much of an issue that would be and perhaps sneak it into the next release when I upgrade to 2.0. Bill
  • Lots of snort alerts after pfsense update to 2.1.2

    13
    0 Votes
    13 Posts
    5k Views
    BBcan177B
    Then I am baffled as to why one firewall has the issue while another (supposedly configured the same way) does not.  There would be only two logical explanations:  (1) either they are, in fact, not actually configured the same although they are supposed to be, or (2) you said one was VMware-based, and it is conceivable that VMware's virtual networking could play into the mix with that HTTP_INSPECT alert. Maybe setting up a standalone pfSense install to see if VMWare is the culprit is the best solution to rule out the Virtual machine idiosyncrasys. or a VM machine for the Main Site.
  • Captive Portal issues

    2
    0 Votes
    2 Posts
    591 Views
    M
    A simple reboot of the laptop resolved it.  Why would this be the case?
  • Asterisk-1.8.26.1 package on pFsense 2.1.2

    3
    0 Votes
    3 Posts
    1k Views
    C
    Tx. I noticed another issue this WE. I took a fresh Asterisk backup and did some config tests. After that I wanted to go back to my backup (as I usually do after testing)…: it restored the backup and initiated a reboot after reboot....it re-installed the Asterisk package again !!!! then I had to restore (again) and it works... Strange behaviour no ?
  • HAPROXY Connection limit

    2
    0 Votes
    2 Posts
    3k Views
    P
    Seems you have found the wrong forum? pfSense which is based on FreeBSD has nothing to do with CentOS ? You should probably try the haproxy mailing-list for this question, maybe one of the core developers present on that list can help you further: haproxy@formilux.org
  • Suricata 1.4.6 pkg v1.0.1 no alerts, no blocking

    3
    0 Votes
    3 Posts
    1k Views
    bmeeksB
    @simby: Hi! i have install Suricata 1.4.6 pkg v1.0.1 with snort. Snort is disabled, suricata is On with AC + blocking. In log i don see any alerts, no blocking. I have tested with grc.com  :(( I have pfsense 2.1.3 x64 Not a good idea at all to run these two packages together on the same firewall.  I would remove the Snort package if you want to use Suricata.  Also, did you select some rules for Suricata to enforce?  You did not mention that in your post.  Oh, and one other point– Suricata really works best only with the Emerging Threats rules.  There are many of the Snort rules that have Snort-specific keywords in them, and these rules will fail to compile on Suricata.  Suricata will start, but it will not use any rules that fail to compile.  This is different from Snort.  If Snort chokes on any rule during compilation, it will not start up.  Go to the Logs Browser tab and examine the suricata.log file for the interface and look for any errors. Bill
  • 0 Votes
    1 Posts
    756 Views
    No one has replied
  • Snort is not blocking

    6
    0 Votes
    6 Posts
    1k Views
    bmeeksB
    @tomtomtom6600: hi bmeeks, thanks for explaining my second problem. This is clear now. Back to my first problem. I will do what you have mentionend, but is it possible that my problem has something to do with squid running in transparend mode. Is it possible that those downloads are cached thanks Ah!  Yes, caching is a possibility.  If you mentioned it before, I missed you saying anything about squid running. Bill
  • 0 Votes
    3 Posts
    990 Views
    W
    Hrmm yeah only unbound-1.4.21_1.tbz is available. 1.4.22 for 2.0.X was not built for some reason automatically. You on 2.1.3 now so I am not going to worry too much :)
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.