[2.8.0-RELEASE][admin@t70.stevew.lan]/root: pkg search pfSense-pkg pfSense-pkg-Avahi-2.2_7 pfSense package Avahi pfSense-pkg-Backup-0.6.3 pfSense package Backup pfSense-pkg-Cron-0.3.8_6 pfSense package Cron pfSense-pkg-FTP_Client_Proxy-0.3_9 pfSense package FTP_Client_Proxy pfSense-pkg-Filer-0.60.6_9 pfSense package Filer pfSense-pkg-LADVD-1.2.2_5 pfSense package LADVD pfSense-pkg-LCDproc-0.12_2 LCDproc package for pfSense pfSense-pkg-Lightsquid-3.0.7_5 pfSense package Lightsquid pfSense-pkg-Netgate_Firmware_Upgrade-0.47.1 pfSense package Netgate Firmware Upgrade pfSense-pkg-Notes-0.2.9_5 pfSense package Notes pfSense-pkg-Open-VM-Tools-10.1.0_5,1 pfSense package Open-VM-Tools pfSense-pkg-RRD_Summary-2.2 pfSense package RRD_Summary pfSense-pkg-Service_Watchdog-1.8.7_4 pfSense package Service_Watchdog pfSense-pkg-Shellcmd-1.0.5_4 pfSense package Shellcmd pfSense-pkg-Status_Traffic_Totals-2.3.2_7 Traffic Totals using the vnStat database pfSense-pkg-System_Patches-2.2.20_2 pfSense package System_Patches pfSense-pkg-Tailscale-0.1.8 pfSense package Tailscale pfSense-pkg-Telegraf-0.9_8 pfSense package Telegraf pfSense-pkg-WireGuard-0.2.9_5 pfSense package WireGuard pfSense-pkg-acme-0.9_1 ACME package for pfSense pfSense-pkg-apcupsd-0.3.92_9 pfSense package apcupsd pfSense-pkg-arping-1.2.2_6 pfSense package arping pfSense-pkg-arpwatch-0.2.3 Arpwatch package for pfSense pfSense-pkg-bandwidthd-0.7.7 BandwidthD package for pfSense pfSense-pkg-bind-9.20_1 BIND DNS suite with updated DNSSEC and DNS64 pfSense-pkg-cellular-1.2.4 Voleatech Cellular Module Interface pfSense-pkg-darkstat-3.1.4 pfSense package darkstat pfSense-pkg-freeradius3-0.15.14 FreeRADIUS 3.x package for pfSense pfSense-pkg-frr-2.0.2_6 FRR package for pfSense pfSense-pkg-haproxy-0.63_10 pfSense package haproxy pfSense-pkg-haproxy-devel-0.64_1 pfSense package haproxy-devel pfSense-pkg-iperf-3.0.5 pfSense package iperf pfSense-pkg-lldpd-0.9.11_3 802.1ab Link Layer Discovery Protocol (LLDP) daemon pfSense-pkg-mDNS-Bridge-1.0 pfSense package mDNS Bridge pfSense-pkg-mailreport-3.6.4_5 pfSense package mailreport pfSense-pkg-mtr-nox11-0.85.6_5 pfSense package mtr-nox11 pfSense-pkg-net-snmp-0.1.5_13 Net-SNMP package for pfSense pfSense-pkg-nmap-1.4.4_8 pfSense package nmap pfSense-pkg-node_exporter-0.18.1_5 pfSense package node_exporter pfSense-pkg-nrpe-4.2 pfSense package nrpe pfSense-pkg-ntopng-6.2.0 pfSense package ntopng pfSense-pkg-nut-2.8.2_5 Network UPS Tools pfSense-pkg-openvpn-client-export-1.9.5 pfSense package openvpn-client-export pfSense-pkg-pfBlockerNG-3.2.8 pfSense package pfBlockerNG pfSense-pkg-pfBlockerNG-devel-3.2.8 pfSense package pfBlockerNG pfSense-pkg-pimd-0.0.3_7 PIMD package for pfSense pfSense-pkg-siproxd-1.1.4_2 pfSense package siproxd pfSense-pkg-snmptt-1.0.0_2 pfSense package snmptt pfSense-pkg-snort-4.1.6_25 pfSense package snort pfSense-pkg-softflowd-1.2.6_2 pfSense package softflowd pfSense-pkg-squid-0.5.3 pfSense package squid pfSense-pkg-squidGuard-1.16.23 pfSense package squidGuard pfSense-pkg-stunnel-5.50_13 pfSense package stunnel pfSense-pkg-sudo-0.3_10 pfSense package sudo pfSense-pkg-suricata-7.0.8_2 pfSense package suricata pfSense-pkg-syslog-ng-1.16.2 pfSense package syslog-ng pfSense-pkg-tftpd-0.1.3_6 pfSense package for tftp server pfSense-pkg-tinc-1.0.35_7 pfSense package tinc pfSense-pkg-udpbroadcastrelay-1.2.4 pfSense package UDP Broadcast Relay pfSense-pkg-zabbix-agent5-1.0.9 pfSense package zabbix-agent pfSense-pkg-zabbix-agent6-1.0.9 pfSense package zabbix-agent pfSense-pkg-zabbix-agent7-1.0.9_1 pfSense package zabbix-agent pfSense-pkg-zabbix-proxy5-1.0.9 pfSense package zabbix-proxy pfSense-pkg-zabbix-proxy6-1.0.9 pfSense package zabbix-proxy pfSense-pkg-zabbix-proxy7-1.0.9_1 pfSense package zabbix-proxy pfSense-pkg-zeek-3.0.6_6 Zeek Network Security Monitor package for pfSense

@stephenw10 said in Logging my daily changing WAN-address:

Yup, that's exactly what we thought. Just waiting for a build to test....

Note that Suricata likely has the same issue. See my comment in this thread for the relevant section of source code: https://forum.netgate.com/topic/197701/error-on-snort-with-if_pppoe/8.

You didn't mention specifically, but we assume you mean you upgraded to pfSense 2.8 Community Edition. Generally speaking, you should avoid pulling the power (i.e. physically unplugging/replugging) as much as possible. When running CE on your own hardware, it's not good for the underlying operating system, FreeBSD, nor pfSense's 'system' files for that matter, to experience an abrupt loss of power.

@stephenw10 @gerdesj Thank you both for the information. I am now looking at posts from BBCan177 and there are indeed plenty. As for the link to the official documentation of the pfblocker package, I'm afraid that it isn't of much help, the information there is somewhat limited.

Thanks to all for the conversation, this was very useful!

👍

@Hakon74 Unfortunately that link no longer appears to work.

Yup. The cost of getting most of those is huge. It would have to be recouped somewhere.

Well it's presented that way because the vast majority of users are either reinstalling Plus on an eligible device or installing CE on one that isn't. But I agree it could be clearer. I'll raise it.

You should open a request here: https://redmine.pfsense.org/

I can remove your NDI if you send it to me in chat. Or if you upgrade to 2.7.2 first you will see 2.8.0 offered.

@ChrisJenk said in How to redirect IPv4 *and* IPv6 NTP traffic:

Any idea how I can redirect IPv6 NTP traffic alongside IUPv4 NTP traffic?

What I did was find what host name they were using and created an alias to my home server.

To update on this problem, it is solved with the CE 2.8 version

The 4200 must be one such model. I restored to a new one using ECL (super handy not to need to connect to it), noted it hadn't enabled the RAM disks (presumably, needed a restart), and then it remained the default 40/60 after a couple of boots. Not sure if that means the values get set sometimes, or it's been that way for months...seems like I would have noticed before now. Anyway I see it's fixed in 25.03 as noted.

For those worried about drive wear there is https://redmine.pfsense.org/issues/16210.

@stephenw10

Good news. I was able to format the USB drive as UFS, reinstalled, and everything is up and running on my (now) backup 1100.

Interestingly, on this one it configured the /VAR disk for 120MB as I had set in the configuration, rather than limiting it to 60MB as the other device did. I am guessing that the Restore process just sets it to whatever the configuration is and it doesn't have the UI glitch holding it at 60MB.

Thanks so much for your assistance (again), Stephen. Very much appreciated.

If you have Snort or Suricata installed make sure the log settings for those are saved as something useful.

Yup just install 2.8 clean and restore your config into it. There's little point in trying to upgrade an ancient 2.4.5 install.

Confirmed still an issue as of May 2025 with pfSense CE 2.8.0 and Status Traffic Totals package version 2.3.2_7

I also updated the Redmine bugtracker: https://redmine.pfsense.org/issues/11797

Mmm. Fun*. Yeah I still agree this all seems like a workaround to force something that wasn't designed to work that way. There must be a better way...

Hmm, so mostly stuff in Tailscale. Except the Ubuntu updates, which is hard to explain. Nothing should have changed there.

The beta is pretty stable. I'm running it as my edge here without issue. If you are running ZFS so you can roll back then I would try it.