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.
  • OLSRD in Pfsense 2.3+

    1
    0 Votes
    1 Posts
    375 Views
    No one has replied
  • Tinc issues and questions

    12
    0 Votes
    12 Posts
    4k Views
    N
    @ioiioi: @ssppcc: In all cases, I can´t find the tun0 interface in the GUI, but I can find it via SSH with ifconfig. have ever fixed this problem? I got the same here, and would like to do 1:1 nat on tun0. but can't see tun0 from the interface menu. and of coz could not add rules for that. by default, tun interfaces have been hidden. you can unhide it in /etc/inc/util.inc or /etc/inc/utils.inc. first backup the file and search for "function get_interface_list" function, then remove the "tun" from "array". go to interface assign tab and press save, then you can add tun interface
  • Configure LCDproc Screens one by one

    2
    0 Votes
    2 Posts
    654 Views
    P
    Second, i have 5 Interfaces, in the Screen with the Interfaces Status ("WAN up" and so on), i never see all Interfaces because its only one Colums. Can i change it so the Interfaces are in different rows? The Interfaces widget on the dashboard has a summary of up/down state of each interface. And in the current release you can filter the list to just display the interfaces that you care about.
  • PyPy Package

    1
    0 Votes
    1 Posts
    538 Views
    No one has replied
  • HAroxy dashboard widget settings panel does not open (2.3.4)

    1
    0 Votes
    1 Posts
    434 Views
    No one has replied
  • MOVED: HAProxy will hangs when I upgrade to pfsense 2.3.4

    Locked
    1
    0 Votes
    1 Posts
    498 Views
    No one has replied
  • MOVED: SQUID proxy is not creating NAT rules and forwarding to port 3128

    Locked
    1
    0 Votes
    1 Posts
    465 Views
    No one has replied
  • MOVED: Duda sobre squid+squidguard

    Locked
    1
    0 Votes
    1 Posts
    480 Views
    No one has replied
  • Unable to start Freeradius after upgarding 1.7.7 to 1.7.8

    2
    0 Votes
    2 Posts
    616 Views
    D
    Read this and configure the certificates. https://forum.pfsense.org/index.php?topic=128923.0
  • Unable to see mac address in Radius-Request

    4
    0 Votes
    4 Posts
    1k Views
    K
    MAC addresses are local to the connected ethernet segment, they are meaningless on any other context because they are not used in connections that cross routing points.
  • LCDproc-dev and EZIO-100/MTB-134 LCD

    2
    0 Votes
    2 Posts
    2k Views
    F
    We are working on it here: https://forum.pfsense.org/index.php?topic=129820.0
  • Mbmon

    2
    0 Votes
    2 Posts
    2k Views
    N
    @derek_bartram: Hi, I'm having some difficulty getting to grips with temperature sensing on my Firebox x1250e with pfsense 2.2.6-RELEASE (i386) A number of sites include the pfsense docs site mentions it is possible using mbmon, however it appears the docs are out of date (there is references to pkg_add command which doesn't appear to exist). Does anyone know how I could get this installed please? Alternatively something similar to check system temperature. I'm looking to turn the fan speed down somewhat as it's currently unacceptable to the missus, but I don't really want to turn it down to low if system temperature is going to be excessively high. –--- FROM DOC SITE ----- If you have modified the cooling in the box such as reducing the fan speed or swapped out the CPU for a more powerful one it's a good idea to test the maximum temperature is still within a sensible value. You can do this by monitoring the cpu temperature while forcing the CPU to 100%. On the XTM5 box you can use the coretemp module to directly read the CPU core. This is built into 2.1 already and information is on the forum to read it in 2.0.X. All the other boxes require the use of an older program to read the thermal sensor connected to the SuperIO chip, mbmon. Remount the filesystem RW (if you're running Nano) then install it: pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.3-release/Latest/mbmon.tbz <<< Failing step, with Command not found. Then issue a rehash so pfSense knows where the new binaries are: rehash Monitor the system temperature: mbmon -I Im having the same problem, some hope somebody can help. //Nerone
  • 2.3 LCDPROC

    69
    0 Votes
    69 Posts
    36k Views
    stephenw10S
    Which particular post in that thread? I don't see anything on that page you linked to concerning baud rate. Steve
  • Feature Request: Disable Service Watchdog

    1
    0 Votes
    1 Posts
    614 Views
    No one has replied
  • Tinc on 2.3.3-p1

    Locked
    3
    0 Votes
    3 Posts
    996 Views
    J
    Yep, that worked, thanks :)
  • SquidGuard Bug

    4
    0 Votes
    4 Posts
    2k Views
    A
    Anybody found a solution to this issue? Thanks
  • MOVED: 2.3.3 not filtering anymore

    Locked
    1
    0 Votes
    1 Posts
    361 Views
    No one has replied
  • 0 Votes
    3 Posts
    822 Views
    G
    Hi quadrinary, Thanks for your reply. Since my post, our firewalling solution is in master/slave mode without any outage. Your reply seems to be a good idea. We will test in the last few nights and give you a reply. Bertrand
  • Unexplainable Issue with BIND!!!

    2
    0 Votes
    2 Posts
    1k Views
    N
    Hi Again, I narrowed down my findings. I logged in through the shell and notice that the actual zone files in the slave server are not being updated (though the GUI is synced with master). Deleting the zone files from the slave and resyncing solves the issue of replying of old records. It seems that the zone transfer works fine when there is no existing zone file in the slave. Sadly, it is unable to update if there is any existing file. I figure that the XMLRPC syncs the backend database of the GUI. To my understanding, it is then supposed to either generate the slave zone file based on that data, or it should initiate a transfer of the actual zone file of the master (like any other master-slave dns zone transfer). I am still unsure if there is configuration mistake or its happening because of a bug. I'll appreciate any help, opinion or suggestions. Thanks in advance.
  • Freeradius 1.7.8 on pfsense 2.4.0 : eap-tls bug on ca+crl pem file output

    2
    0 Votes
    2 Posts
    810 Views
    L
    solved! https://github.com/pfsense/FreeBSD-ports/pull/344 thanks doktornotor!
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.