Subcategories

• Cache/Proxy

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

  21k Posts

  J

  @qupfer What did I bang my head over this strange 502 issue. Your solution did it! Thank you so much, even 2.5 years later!
• IDS/IPS

  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.
• Traffic Monitoring

  Discussions about packages that handle bandwidth and network traffic monitoring functions such as bandwidtd, ntopng, etc.
  571 Topics

  3k Posts

  D

  @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.
• pfBlockerNG

  Discussions about the pfBlockerNG package
  3k Topics

  20k Posts

  K

  Hi All. A few years back there was no real good way of getting pfBlockerNG log files to a remote SIEM as pfBlocker had no built-in syslog support. The way pfBlockerNG rotated log files caused the entire log content to be resent/duplicated when the CRON update job ran if you used the syslog-ng package to monitor the log files. A Ticket has been open on this for years: https://redmine.pfsense.org/issues/14878 I can still not find any builtin syslog support, and the log file lines are also still in their own format as opposed to standard Syslog format. Have anyone come up with a good solution to getting pfBlockerNG log files shipped to a SIEM without various workarounds, reformatting and extra packages needed?
• UPS Tools

  Discussions about Network UPS Tools and APCUPSD packages for pfSense
  101 Topics

  2k Posts

  D

  @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.
• ACME

  Discussions about the ACME / Let’s Encrypt package for pfSense
  496 Topics

  3k Posts

  G

  @jimp Done. I was on acme.sh 1.0 (25.07.1) and a downgrade was proposed. Now, the issue is gone.
• FRR

  Discussions about the FRR Dynamic Routing package on pfSense
  294 Topics

  1k Posts

  Y

  said in Please update frr on Pfsense+ to FRR 10.3: https://redmine.pfsense.org/issues/15785 now frr 10.4.1
• Tailscale

  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.
• WireGuard

  Discussions about WireGuard
  696 Topics

  4k Posts

  Q

  Hi Team, I’m running pfSense Plus 25.07.1 with TorGuard WireGuard VPN as my primary tunnel for LAN traffic (for best possible speeds). The tunnel is mostly working now, but I had to go through several fixes and I’m still not confident the configuration is stable. Here’s what I’ve run into: TorGuard support originally helped set up the WireGuard client. It worked fine for about a day, but then the Unbound DNS Resolver stopped working. Even when I re-enabled Unbound manually, LAN clients still couldn’t reach the internet. The main issue seemed to be when switching between WAN (ISP public IP) and the VPN IP. Sometimes traffic didn’t switch over properly, and at one point pfSense even generated a crash report during the switch and restarted. To fix it, I reset the LAN firewall rule so that LAN traffic would route through the VPN gateway when active, and fall back to WAN when the VPN was down. After that, I was able to toggle the VPN on/off without pfSense crashing, and traffic correctly switched between ISP IP and VPN IP. At this point it works, but I don’t think the setup is completely stable. I’d like to ask for guidance on: How to make sure Unbound stays reliable when the VPN gateway goes up/down. Best practices for LAN firewall rules so clients use the VPN when it’s up, and either fall back to WAN or get blocked (kill switch) when the VPN is down. Correctly assigning DNS servers to WAN and VPN gateways. At the moment, in System → General Setup, I don’t see the gateway dropdown next to DNS entries, so my DNS servers are just “floating” with no interface binding. If anyone has suggestions, or can point me to a clean reference configuration for WireGuard + Unbound + proper DNS gateway assignment, I’d greatly appreciate it. I'd really like to have a conference with someone and go over this. I'd like to give them access using RustDesk or TeamViewer so we can talk and they can show me things. I am legally blind so I am one inch from the screen. I've also uploaded the crashdump so you can look over it. I've also been using AI, but I keep going in circles with it, so it's not perfect. Thanks in advance! Warm Regards, Jamestextdump.tar.0