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 voucher page not opening

    3
    0 Votes
    3 Posts
    755 Views
    DerelictD
    Can you manually connect to http://interfaceaddress:8000/  ??
  • Captive portal on pfSense

    2
    0 Votes
    2 Posts
    822 Views
    M
    It seems many times I post here, a bit of knowledge is forced back to me through the web, my keyboard and into my head.  It seems I figure it out immediately after posting (whether or not a get good advice). In this case it was the interface assignment which was set to the physical interface, not the VLAN on that interface. Miles Deep out
  • Snort 2.9.6.0 pkg v3.0.8 Update – Release Notes

    1
    0 Votes
    1 Posts
    701 Views
    No one has replied
  • [Solved] Corrupt config? Failed packages upgrade etc.

    11
    0 Votes
    11 Posts
    3k Views
    BBcan177B
    @bmeeks: While not a bad idea, if the IP address changed, then it would become a false "fix" and folks would assume it was working when it in fact might not be. If pfSense could fix the code to allow domain names it would be really beneficial. Couldn't an alias be setup as packages.pfsense.org and at each interface restart, it would perform a dig packages.pfsense.org +short as the ip address? I assume that the repo is coded in the update page and could be extracted. Just a thought.
  • FreeRaDIUS-XMLRPC

    2
    0 Votes
    2 Posts
    1k Views
    N
    Hello it`s work very well on new version of FreeRADIUS package (2.2.5) Thank you very much
  • 0 Votes
    7 Posts
    5k Views
    bmeeksB
    @priller: @bmeeks: Based on my testing, either the patched binary or turning off the delayed-detect feature worked.  Translated, that means you need the new binary if you want to leave "delayed-detect" set to "on", but if you don't have the new binary yet, you can just set "delayed-detect" to off and should still not see the bug. It seems to be OK with that set to "off". We tried that previously ( https://forum.pfsense.org/index.php?topic=74778.msg410720#msg410720 ) and still had a problem.  Other than having multiple interfaces then vs. a single one now,  I'm not sure what else is different in the config .. or the sequence of events to trigger it.  Anyway, looking much better today. From my understanding of the bug and the Suricata binary code, the call to load the Suppress List entries was made and the list successfully loaded before the rule signatures had been loaded.  So there were, at that moment, no rules in the memory table for the Suppress List to match and thus the flag to "not alert" was not set for any Suppress List rules.  Delayed-Detect is an option designed for inline IPS operation that allows Suricata to go ahead and come up and start passing traffic even before all the rule signatures (detection) are loaded and enabled.  So in this mode, there is a time where traffic will pass uninspected.  In the current quasi-IPS/IDS mode Suricata uses, this parameter has no meaning but I had defaulted it to "on" for the future.  When you disable Delayed-Detect, the rules load earlier and thus are in memory when the Suppress List is loaded and parsed.  So this means rules can match up. The reason this worked using the icons on the Alerts tab is those add the entry to the list and then initiate a "live rule swap" within Suricata.  This is not the same as a restart, thus the rules are in memory and can be matched up against the Suppress List when it loads as part of the "live rule swap".  Restarting the service, however, does trigger the bug when Delayed-Detect is enabled. I've done two things to address this in the upcoming release.  First, I back-ported a patch from 1.4.7 to the 1.4.6 version used on FreeBSD that makes sure the Suppress List is loaded after the rules have been processed.  Second, I added a checkbox on the INTERFACES tab to allow the Delayed-Detect feature to be manually enabled or disabled by the user.  It will default to disabled. Bill
  • Radius with MAC filtering

    2
    0 Votes
    2 Posts
    2k Views
    M
    't Works  ;D Although it took me quite some learning, as I am an economist and not a technical guy  :-[ I too have a Ubiquity access point which supports Radius. So basically this is it: 1. I have laptop and smartphones which connect wireless. 2. I created a special VLAN for wireless only. 3. pfSense cert manager has created certificates (so: not passwords). 4. The certificates are installed in the laptop (wifi connection) and in the smartphones (android). 5. After setting up Radius to use these certificates: 5.a. The smartphone connects to the Ubiquity, which has been told to use Radius, and the address of the Radius-server. 5.b. The Ubiquity forwards the connection request via the switch to the pfSense where Radius resides. 5.c. Somewhere/somehow the client certificate (how this works is not quite clear to me, but it works) of the smartphone is offered to the pfSense radius server to indentify the smartphone. The other way around the server identifies itself to the smartphone with it's server certificate (to avoid MitM-attacks). 5.d. If this authentification is approved the Radius server tells the Ubiquity to allow access for the smartphone. 5.e. The DHCP-server on the VLAN then issues an IP and the firewall assures the smartphone can only go to the internets, and not to the LAN. 't Works  ;D I hope this helps  :P Bye,
  • SquidGuard search Members in Groups

    1
    0 Votes
    1 Posts
    626 Views
    No one has replied
  • Dansguardian and Squidguard together?

    4
    0 Votes
    4 Posts
    1k Views
    R
    If i understand your requirement correctly, what you are asking for is doable in DG… There was another thread where someone was talking about getting it working. Just saw it in the last couple days...
  • Dansguardian-2.12.0.3_2 problems

    12
    0 Votes
    12 Posts
    3k Views
    P
    @torsurfer: @pfSense2User I think you need to enable 'execute' permissions on both the clamav and dansguardian directories. Try this: chmod u+x /var/log/clamav /var/log/dansguardian I made a script to chmod the entire /var/log directory called perms.sh in the /usr/local/etc/rc.d folder: #!/bin/sh /bin/chmod -R 777 /var/log Then, I used the chmod +x perms.sh to make the file as an executable for everyone; lo and behold, it runs! Thank you kindly!
  • Dansguardian Multiple time limit blocks

    7
    0 Votes
    7 Posts
    4k Views
    C
    Step 1. Go to Site Lists under ACLs in dansguardian Step 2. Edit the Default profile….Under banned.....type all the sites which you want  time based access...Site1.com,Site2.org,Site3.net,Site4.com,Site5.org,Site6.info Step 3. Create a new profile, example Time1. Step 4. Under Exception lists of Time1 type the list of sites you want to grant access to For eg you want to grant access to Site1.com, Site2.org & Site2.net from 17:00 hrs to 18:00 Mon-sat Hence Under Exception list you will add #time: 17 00 18 00 012345 Site1.com Site2.org Site3.net Step 5. Create another profile Time2....type the list of sites you want to grant access to For eg you want to grant access to Site4.com, site5.org, Site6.info from 09:00 to 13:00 Mon-Fri hence Under Exception list you will add #time: 09 00 13 00 01234 Site4.com Site5.org Site6.info Step 7. Include the paths of the profiles Time1 & Time2 under the exceptionlists of Default Profile eg..under Exceptionlist of Default profile it should be .Include .Include Adding these two lines instructs dansguardian to parse these files one by one Similarly any number of banned, exception & greylists with different access times can be created.
  • Squid/squidlight question (is it caching correctly?)

    2
    0 Votes
    2 Posts
    836 Views
    H
    Im interested in this topic too. I hope someone who knows will answer? many thnx in advance :)
  • Pfsense having trouble installing squid while snort is installed

    4
    0 Votes
    4 Posts
    1k Views
    H
    After updating to never version i have issues installing every package. I actually have  this problem: Beginning package installation for squid3 . Downloading package configuration file… done. Saving updated package information... done. Downloading squid3 and its dependencies... Checking for package installation... Downloading https://files.pfsense.org/packages/amd64/8/All/squid-3.1.22_1-amd64.pbi ...  (extracting) Loading package configuration... done. Configuring package components... Additional files... squid.inc failed. Backing up libraries... Removing package... Starting package deletion for squid-3.1.22_1-amd64...done. Removing squid3 components... Tabs items... done. Menu items... done. Services... done. Loading package instructions... Include file squid.inc could not be found for inclusion. Deinstall commands... Not executing custom deinstall hook because an include is missing. Removing package instructions...done. Auxiliary files... done. Package XML... done. Configuration... done. Cleaning up... done. Failed to install package. Installation halted. I will try to disable snort and hope the best? Many thnx for this tip. It could solve mine problem, cause i COULD install snort... Many many thnx
  • 0 Votes
    2 Posts
    1k Views
    marcellocM
    My repo is not a pfsense package fork. Use only official repo. If you need any package from my repo, use pkg/pbi via console/ssh
  • Unable to create Suppression Lists

    15
    0 Votes
    15 Posts
    2k Views
    bmeeksB
    @fmaxwell: @marcelloc: The code was merged today. take a look. I just did a package reinstall and that completely solved the inability to create a suppression file.  Thanks! You're welcome!  Sorry about the bug.  It was totally my fault.  In adding some additional security for configuration changes, I accidentally broke saving a new list… :-[ Bill
  • Snort question To Snort, or not to Snort

    5
    0 Votes
    5 Posts
    1k Views
    bmeeksB
    fragged is correct.  This only impacts the IP REPUTATION preprocessor.  It is disabled by default.  I was just pointing it out as one area that can fail with RAM disks.  The downloaded rules tar balls and the individual interface rules are stored on the /usr partition. There once was a bug where Snort did not put the /usr partition in read/write mode when trying to update some files, but I think I have all of those fixed now.  Report back if you notice any errors in the system log about attempting to write to a read-only partition. Bill
  • HAVP: Streaming Devices and Netflix workaround

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • Uploading file failed

    5
    0 Votes
    5 Posts
    3k Views
    P
    Hi finalcut, If nothing is shown in the firewall log, then creating a floating rule like you proposed (https://forum.pfsense.org/index.php?topic=71515.msg414518#msg414518)wont help.. Unless you have rules that match but don't log traffic. But i think that this kind of problem is unlikely to be the cause of your current issues.. You could try is disabling the trafficshaper, maybe that 'interacts' strangely with squid..?? Would also be interesting to see some packet captures of both the wan and lan side simultaneously while a failing upload is being made, so it is clear which side of the connection 'breaks'. Then combine that with logging of squid with a higher then normal verbosity and it should help in determining what part of the process causes it to fail. Greets PiBa-NL
  • 0 Votes
    3 Posts
    1k Views
    D
    Hi. There is an update for fix this. fix lock file when using usb devices add lockfile option Also, we are expecting the upgrade to 3.14.12 on FreeBSD ports, so we can update here on pfSense. Best Regards.
  • PfBlocker recommended lists - overlap with Snort

    2
    0 Votes
    2 Posts
    1k Views
    BBcan177B
    Here is a link to a discussion I had in regards to blocklists. https://forum.pfsense.org/index.php?topic=73353.msg402927#msg402927 Some of those lists are for mail servers and can be ignored. If you add more blacklists, you will need to increase the maximum table entry. Goto  Advanced:Firewall/NAT  and increase the "Firewall Maximum Table Entries". There is no functionality currently to see if the blacklists are downloading the lists at the specified frequency unfortunately.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.