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.
  • Any Presetup steps to make Squidguard work - quick question

    Locked
    4
    0 Votes
    4 Posts
    2k Views
    V
    Try the squidguard Default and ACL or squid proxy server settings. No need to setup each browser for a proxy. I tested it on my network.
  • 64bit snort?

    Locked
    4
    0 Votes
    4 Posts
    3k Views
    J
    Building this file tonight or in the morning. Night. James
  • MOVED: squid cannot start after fresh install on latest 2.0 snapshots

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • MOVED: dismal squid performance

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Snort - whitelists?

    Locked
    2
    0 Votes
    2 Posts
    2k Views
    J
    Add the VPN ip to a NETLIST. James
  • Snort 2.8.6 pkg v. 1.32 Issue

    Locked
    7
    0 Votes
    7 Posts
    3k Views
    J
    @jamesdean: Sorry about that, I forgot to add a file. James Good guys finish last.  ;D
  • Openh323

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Users get blocked by Snort package

    Locked
    2
    0 Votes
    2 Posts
    3k Views
    C
    Your suppression should look like this; suppress gen_id 119, sig_id 1 suppress gen_id 119, sig_id 2 suppress gen_id 119, sig_id 4 suppress gen_id 119, sig_id 13
  • Snort Update Issue with Snort 2.8.6 pkg v. 1.31

    Locked
    6
    0 Votes
    6 Posts
    3k Views
    D
    I had a similar issue - what fixed it it was Services / Snort / Global Settings / Reset button. I had to reconfig Snort, but everything works great now.  Just fantastic; love this package.
  • Squid Blacklist url w/ path

    Locked
    3
    0 Votes
    3 Posts
    9k Views
    N
    @jimp: It's a regex, iirc, so for "any number of characters (or none)" use .*, not * So try this: example.com/.*/w4m Thank you; I'll will try that. Since I posted, I was able to install squidGuard and compose a Destination List; by following the instructions on the squidGuard Quick Start page http://diskatel.narod.ru/sgquick.htm. That allowed me to selectively block just the dating and inappropriate portions of Craigslist. I do have Shalla's Blacklist installed, but it's 'hard coded' for just one or two Craigslist cities. I'll try your wildcard syntax and see if it works with a squidGuard destination list.  Right now, my Dest List uses a long set of URLs and I'll have to add another one for each additional city.  If your suggestion works there as well, the same URL set will work for every Craigslist city.  I'd forward the entries to Shalla SS; for integration into his list. I'll also be using your syntax, where I originally intended.  Don't know for what, but something will pop up soon enough. Your response is appreciated. NV
  • MOVED: Squid and LDAP on 2.0

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • MOVED: Squid Pfsense

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Squid + SquidGuard + ( Transparent proxy & Proxy Authentication )

    Locked
    4
    0 Votes
    4 Posts
    12k Views
    K
    Try This: Let your squid listen on Optional Interface in Non Transparent Mode. Just forward all the http traffic from LAN interface to Optional Interface where your squid is listening (Default 3128). Since Your Squid is not going be in Transparent Mode you can Enable Authentication. :)
  • Recent clamd needed

    Locked
    35
    0 Votes
    35 Posts
    21k Views
    jimpJ
    I updated the package to pull the new version. It should be up in about 5 minutes.
  • DenyHost 0.5.1 with pfsense 1.2.3

    Locked
    5
    0 Votes
    5 Posts
    4k Views
    G
    @ToxIcon: 2010-07-11 19:08:52,679 - sync        : ERROR    <fault 1:="" "exceptions.keyerror:'timestamp'"="">Traceback (most recent call last):   File "/usr/local/lib/python2.5/site-packages/DenyHosts/sync.py", line 117, in receive_new_hosts     self.__prefs.get("SYNC_DOWNLOAD_RESILIENCY"))   File "/usr/local/lib/python2.5/xmlrpclib.py", line 1147, in call     return self.__send(self.__name, args)   File "/usr/local/lib/python2.5/xmlrpclib.py", line 1437, in __request     verbose=self.__verbose   File "/usr/local/lib/python2.5/xmlrpclib.py", line 1201, in request     return self._parse_response(h.getfile(), sock)   File "/usr/local/lib/python2.5/xmlrpclib.py", line 1340, in _parse_response     return u.close()   File "/usr/local/lib/python2.5/xmlrpclib.py", line 787, in close     raise Fault(**self._stack[0]) Fault: <fault 1:="" "exceptions.keyerror:'timestamp'"=""></fault></fault> Looks like the problem is not python. From the FAQ Denyhosts was written for 2.3 and 2.4. This might help someone but I don't use it because VPNs are a we bit safer  ;) DenyHosts requires Python v2.3 or later. If you are using an earlier version of Python then you should install a newer version of Python on your system. Multiple versions of Python can safely co-exist on your server so you do not need to worry about breaking any dependencies. You should obtain the latest version of Python and install it on your system. Depending on the method of download, your latest Python executable is typically installed in /usr/local/bin or /usr/bin. If you downloaded version Python v2.3, then the executable is python2.3. If you downloaded Python v2.4 then the executable is python2.4. If you will be using DenyHosts in daemon mode, then you will need to edit the daemon-control-dist script. You will want to copy this file to "daemon-control" such that future DenyHosts upgrades will preserve your edits. $ cp daemon-control-dist daemon-control Assuming you installed Python v2.4 and the executable is in /usr/bin then you will need to make the following changes to your daemon-control script: Line # From To 1 #!/usr/bin/env python #!/usr/bin/python2.4 18 PYTHON_BIN = "/usr/bin/env python" PYTHON_BIN = "/usr/bin/python2.4" You may need to modify the above paths to reflect the actual installation location and version of Python that you installed. If you are not using DenyHosts in daemon mode then to execute DenyHosts you would do the following: $ python2.4 denyhosts … args... -or- $ python2.3 denyhosts ... args...
  • Snort-dev Package Update and Bug List

    Locked
    1
    0 Votes
    1 Posts
    9k Views
    No one has replied
  • Problem connecting to Package System?

    Locked
    2
    0 Votes
    2 Posts
    2k Views
    S
    I have the same problem.
  • Squid traffic management

    Locked
    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • Squid + squidguard + backup

    Locked
    1
    0 Votes
    1 Posts
    4k Views
    No one has replied
  • [SUGGESTION] FreeSwitch on nano embedded / writing logs to usb-disk

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