Subcategories

• Cache/Proxy

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

  21k Posts

  D

  Retested on 24.11-RELEASE (amd64) all seems to work. So it seems right to file a bug for this issue.
• IDS/IPS

  Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.
  2k Topics

  16k Posts

  S

  So since there is no version 25.03. There is an official 25.07 now but only get a 7.08.2 what happen to the rest up to Suricata 7.0.10 or 7.0.12?
• Traffic Monitoring

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

  3k Posts

  K

  @pulsartiger The database name is vnstat.db and its location is under /var/db/vnstat. With "Backup Files/Dir" we are able to do backup or also with a cron.
• pfBlockerNG

  Discussions about the pfBlockerNG package
  3k Topics

  20k Posts

  G

  @rasputinthegreatest said in pfBlockerNG not logging anything by default?: is impossible even on a clean installation if it's embedded in firmware for example. Because "you don't want to". (no time, other interest, etc) Remember : pfSense is 'open source' **. So, here it is - to be seen by everybody who takes the effort to understand what it all means. ** granted : the FreeBSD kernel has its own github source tree, and can be found else where. Maybe there are a process or two (binaries) that are owned by Netgate without freely accessible source but these can be reverse engineered (tools exist) if you really want to know what happens in there. @rasputinthegreatest said in pfBlockerNG not logging anything by default?: In default logs it would not show up. And that's a good thing. Just know that you can see them if you need to. pfBlockerng makes already nice stats for you. @rasputinthegreatest said in pfBlockerNG not logging anything by default?: What does that look like? On this kind of devices : My 4100 : there is no VGA or HDMI connector. So, when the system boots, you can't see the BIOS, you 'see' nothing untill the web GUI engine starts. For that to work, a LAN interface needs to be up. For an interface to be up, the system had to boot to the end without errors. So, these devices have a "serial port". That port is sued to spit out the BIOS and boot process. Hook up a serial 'USB' connector, and use a terminal emulator. If you use a "PC" as a pfSense device then you have a video card, and USB mouse, keyboard etc so that will be your 'console' access. Hook up a screen and you see the boot process etc. Another example : your smart switch , How do you access the GUI ? => with a web browser. You can't attach a VGA screen to it neither. What happens when the firmware update fails ? You have to use the console access - if one exist. If it doesn't : you waste bin the device as no access anymore. Neither your APs, Printers, coffee machine, airco; whatever. Most have a 'hidden' serial connection for low 'console' level access. Always 'command line based' of course.
• 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
  493 Topics

  3k Posts

  G

  @EChondo What's your pfSense version ? The instructions are shown here : [image: 1753262126227-1acdc586-cb29-4148-9e36-81ade4e5e60c-image.png] A restart of a service will start by re creating their config files. If a certificate changed, it will get included. When the process starts, it will use the new certificate. @EChondo said in Issue with ACME Certificates Refresh & Restarting HAProxy: I haven't been able to confirm if the above works(mine just renewed, don't feel like doing it again just to test), so we'll see in 60 days I guess. No need to wait x days. You can re test / renew right away, as you are 'allowed' to renew a couple (5 max ?) of times per week.
• 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

  585 Posts

  L

  @veddy254 said in How to update to the latest Tailscale version?: @lbm_ said in How to update to the latest Tailscale version?: https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.84.2_1.pkg pkg: An error occured while fetching package I would recommend verifying the DNS settings in PfSense and verifying date/time is correct. Barring that, try again later and see if it still fails. I was able to successfully run the command on my 2.8.0 install (I didn't install it because I've already installed it) so it seems localized. Interesting. After I (reinstalled) tailscale the /etc/resolv.conf was overwritten. So I just readded the DNS entries in the Pfsense WebUI, and not it worked. pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.84.2_1.pkg Fetching tailscale-1.84.2_1.pkg: 100% 11 MiB 11.9MB/s 00:01 Installing tailscale-1.84.2_1... Newer FreeBSD version for package tailscale: To ignore this error set IGNORE_OSVERSION=yes - package: 1500054 - running kernel: 1500029 Ignore the mismatch and continue? [y/N]: y package tailscale is already installed, forced install Extracting tailscale-1.84.2_1: 100% And pkg info tailscale tailscale-1.84.2_1 Name : tailscale Version : 1.84.2_1 Installed on : Wed Aug 6 09:17:23 2025 CEST Origin : security/tailscale Architecture : FreeBSD:15:amd64 Prefix : /usr/local Categories : security net-vpn Licenses : BSD3CLAUSE Maintainer : ashish@FreeBSD.org WWW : https://tailscale.com/ Comment : Mesh VPN that makes it easy to connect your devices Shared Libs required: libthr.so.3 libc.so.7 Annotations : FreeBSD_version: 1500054 build_timestamp: 2025-07-30T02:26:16+0000 built_by : poudriere-git-3.4.2-12-g74a54a88 port_checkout_unclean: no port_git_hash : 275975297bc ports_top_checkout_unclean: no ports_top_git_hash: 0cd2c078c1e Flat size : 35.4MiB Description : Tailscale is a mesh VPN alternative, based on WireGuard, that connects your computers, databases, and services together securely without any proxies.
• WireGuard

  Discussions about WireGuard
  692 Topics

  4k Posts

  M

  This is still an issue as of 2.8.0 / 25.07, and it drives me crazy. Gateway failure works as expected, the wireguard tunnels will fail over to the backup gateway and continue on as normal, but will never recover once the failed gateway comes back online. While a reboot will (usually) fix it, I usually just go into my routing settings and mark the secondary gateway as down, forcing it to revert back to the primary... the users tend to dislike it when I reboot the firewall in the middle of the day