Subcategories

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

    4k Topics
    21k Posts
    JonathanLeeJ
    @firefox you could always turn off save settings on squid and squid guard and delete the package and reinstall. You could also manually remove the config from the xml file. Those are also options but I think the fresh firmware is the best approach. It does work on that version I got it going.
  • 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
    keyserK
    @jrey said in pfBlockerNG syslog logentries to remote SIEM: @keyser I so want to answer this, but then at the same time (no I don't) ... pfblocker using syslog messaging in real time. no tailing of files, no other packages, just code. Huuuh? That seems very very interesting I noticed your name in other posts around the forum where you seemed to be QUITE proficient at coding/developing. Are you by any chance considering involvement in developing and refining the pfBlockerNG package? It would be SO great if you are looking into adding native syslog to the pfBlockerNG package - or an easy workaround that does not require additional packages and “temporary” edits in files that does not survive service restarts or pfSense updates. Here’s that you will fill me/us in on the solution you are using to your Greylog - please, pretty please with sugar on top
  • 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
    606 Posts
    M
    @yobyot I've SSHed into pfsense and for the sake of testing I've simply run the command: tailscale up --auth-key=tskey-client-kQ_THE_REST_IS_A_SECRET\?preauthorized=true\&ephemeral=false --accept-dns=false --accept-routes --advertise-exit-node --advertise-routes=X.X.X.X/24 --advertise-tags=tag:pfsense Note the preauthorized=true and ephemeral=false I gave this key all permissions (temporarly as I just wanted to verify it's working) of course I had to register the tag used also in the ACL tags pane: https://login.tailscale.com/admin/acls/visual/tags so far so good
  • 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.
  • NRPE2 | Icinga/nagios | check_load | Almost there

    2
    0 Votes
    2 Posts
    2k Views
    G
    http://www.smallbusinesstech.net/more-complicated-instructions/nagios/setting-up-nagios-on-a-debian-server-to-remotely-monitor-an-untangle-server define service{         use                            generic-service                host_name                      pfsense         service_description          Current Load         check_command check_nrpe_1arg!check_load }
  • Snort - what does it do?

    2
    0 Votes
    2 Posts
    707 Views
    BBcan177B
    http://en.wikipedia.org/wiki/Snort_(software) https://doc.pfsense.org/index.php/Setup_Snort_Package https://forum.pfsense.org/index.php?topic=61018.0
  • NTOP - Never really gets internal host names correct.

    1
    0 Votes
    1 Posts
    958 Views
    No one has replied
  • Problem with Sarg application

    5
    0 Votes
    5 Posts
    3k Views
    K
    I don't use Dansguardian, so I am not sure if you have to configure SARG for either Dansguardian or Squid. You probably don't want to configure it for both. My guess, is that your configuration is correct now, cause you have an index that shows up and the realtime works. If you look under: Services - Proxy: Log rotate (this setting will conflict with SARG) Status - SARG Reports - Schedule - Schedule Options - Action after sarg From what I read, you should leave Squid to not rotate logs at all and have SARG do it instead. Or you can modify the CRON job for SARG so it runs right before Squid rotates logs. If you leave Squid rotating logs, what happens is that at midnight, it will restart and zero out the acess.log, so when SARG tries to read the access.log it will be empty, producing a blank report. You can test your configuration by going ahead and opening up the SARG schedule and clicking Force update now. Then check Status - System Logs and it should show any errors if SARG is having an issue. If it works, you should see updated reports.
  • Squid proxy

    16
    0 Votes
    16 Posts
    4k Views
    KOMK
    Glad to hear you got it working.
  • Squid3-dev problems

    4
    0 Votes
    4 Posts
    2k Views
    F
    I figure out good solution First uninstall squid3-dev (and squidguard if any) then install  squid3    (3.1.20 pkg 2.1.0) then uninstall squid 3 finally install  squid3-dev tm make squidguard work with squid3-dev you should flow this steps https://forum.pfsense.org/index.php?topic=73640.0
  • HTTP loadbalancer VIP with rewrite question

    2
    0 Votes
    2 Posts
    634 Views
    F
    Update, I have got this to work with Varnish3 with manual entries.
  • Fresh HAVP install does not start

    1
    0 Votes
    1 Posts
    791 Views
    No one has replied
  • Request for haproxy-devel-1.5-dev25-amd64.pbi

    7
    0 Votes
    7 Posts
    2k Views
    J
    sounds good. thanks for the information. the current package is stable so I am in no hurry.
  • Samba pbi

    1
    0 Votes
    1 Posts
    697 Views
    No one has replied
  • Snort not Alert- arp spoofing

    7
    0 Votes
    7 Posts
    6k Views
    H
    Thanks For Your Kindly Helping Dear <3 Thank YOu  :)
  • Snort cannot start

    3
    0 Votes
    3 Posts
    3k Views
    P
    asphyx Thank´s, this work for me!.
  • Lcdproc-0.5.6 randomly stopping

    3
    0 Votes
    3 Posts
    2k Views
    N
    I've had this issue since the beginning of me using pfSense & LCDProc (1-2 years).  I believe the issue is if one of the interfaces that the LCDProc client is monitoring, goes down or dissapears, then LDCProc client dies. I believe this is why my LCDProc client does not start at router start - the VPN interfaces aren't up by the time LCDProc starts.  A simple restart of the LDCProc service from the web console starts LCDProc fine.
  • Cron Package not running command?

    4
    0 Votes
    4 Posts
    2k Views
    jimpJ
    At the very least, ping should be /sbin/ping, and expr should be /bin/expr There may be more but I didn't look over every line. You'll need to fix any place that runs a command without specifying the full path.
  • Bug or possible problem with Proxy (Squid)

    1
    0 Votes
    1 Posts
    546 Views
    No one has replied
  • PfBlocker Lists Disappearing?

    12
    0 Votes
    12 Posts
    3k Views
    J
    Hi BBCan177, I am going to try your script. I'll get back to you to let you know my results :) Thanks again for your help! Best regards, Joel.
  • Recognizing lcdproc status with disabled LCDd

    1
    0 Votes
    1 Posts
    657 Views
    No one has replied
  • Problem with Dansguardian application

    4
    0 Votes
    4 Posts
    2k Views
    R
    Your clients go to dansguardian… dansguardian forwards to squid.
  • Email Reports Package is not sending emails

    9
    0 Votes
    9 Posts
    4k Views
    F
    I think that patch was just for pfsense in general.  Multiple recipients will work with other notifications.  Although I'm no programmer I think this is more of a issue with the actual mail report package?
  • Postfix adding extra domain names

    8
    0 Votes
    8 Posts
    1k Views
    B
    Maybe something about installing the current package on 2.1. Perhaps an update to 2.1.4 would be worth a try before reinstalling.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.