@Cabledude said in System Logs-Gateways: no entries after 24.11 update:

[24.11-RELEASE][root@SPK.home.arpa]/root: ps aux | grep 'dpinger'
root 82858 0.0 0.1 12952 2540 0 S+ 16:00 0:00.01 grep dpinger
[24.11-RELEASE][root@SPK.home.arpa]/root:

means : no dpinger process is running !
You should see : see above, previous post,w where I gave 1 for IPv4 and 1 for IPv6. You should see the same thing.
No dpinger running == totally normal that there are no gateway logs ;)

I just restarted my pfSense this morning as I upgraded to 25.03.b.20250414.1838 which came out yesterday and :

[25.03-BETA][root@pfSense.bhf.tld]/root: ps aux | grep 'dpinger' root 7412 0.0 0.1 14692 3084 - Is 08:10 0:00.62 /usr/local/bin/dpinger -S -r 0 -i WAN_DHCP6 -B 2a01:dead:beef:a600:92ec:7 root 7653 0.0 0.1 14692 3084 - Is 08:10 0:00.56 /usr/local/bin/dpinger -S -r 0 -i WAN_DHCP -B 192.168.10.4 -p /var/run/d root 51651 0.0 0.1 14076 2684 0 S+ 09:23 0:00.00 grep dpinger

and logs do show up for me now.

Btw : the beta releases are really good ... no issues what so ever for me (vanilla dual stack pfSense. with captive portal, FreeRadius, minimal pfBlocker and some other small gadgets).

Yes we need more information to diagnose this. Still this? https://forum.netgate.com/topic/189542/pfsense-access-interruption

If so I suggest continuing there.

But if you're running in hyper-V still check for the reported hveventX issue: https://forum.netgate.com/post/1207821

@Gblenn
currently all my environments are in hyper v so I will not be able to experiment on proxmox.
I can't figure out why pfsense is cutting off access but I will focus on finding out

thanks

First, in the GUI, stop FreeRadius.

Then, in a first console access, you run

radiusd -X

Then, in the second (use SSH ?!) start our radtest :

@laurens-DS said in Setting up FreeRADIUS on pfSense with Google LDAP and integrating with UniFi Controller:

when i do a radtest

In the first console, with the Radius debug log output, you can see the reason.

@jazzl0ver Awesome, thanks 🎯

[root@gw-2 ~]# /sbin/glabel label swap0 /dev/blabla

was exactly the part which I have been missing 🏷

And why:

[root@gw-2 ~]# glabel list

Didn't showed me anything 🔑

I have never understood why a licence for a short duration (1 year) can not readily be moved when the old hardware is not functional (cold spare or hardware failure).

Having a licence tied to hardware makes perfect sense for a long term licence (where ongoing company income comes from old hardware dying and being replaced eg Netgate hardware) but makes no sense when an annual licence fee is paid.

Perhaps Netgate just dislikes selling software and really only wants to sell hardware.

@balsal7346 said in Verizon FiOS Home Internet with CR1000A Router to use with Netgate 1100:

netgate 1100

I know this is an old post, but wanted to provide my approach since I took an interest in pfsense only a couple of months ago.

I found a video (https://www.youtube.com/watch?v=Vf1sTkxxjLs&list=WL&index=2) that helped me convert the CR1000A into an access point.

I configured the pfsense software using https://www.youtube.com/@NaomiBrockwellTV

I plugged the ethernet cable from the ONT into the WAN port of the pfsense box.

I plugged to converted CR1000A into the a network switch.

I plugged the LAN port of pfsense into the switch.

This way the pfsense firewall is between the Internet and the CR1000A that acts as an AP for my wireless devices since I didn't want to spend any extra for a different AP.

I'm still on a steep learning curve for the pfsense software, but I have wired and wireless access to the Internet for most common activities.

@pst Never mind, a two hour wait and a prayer seems to have resolved whatever state the box got itself into...

@Gblenn that, and Adguard can do DOT and DOH.
I might enforce the DOH servers on the client side.

@NGUSER6947

you can install coturn on your Nextcloud server, here is a german howto:
https://www.c-rieger.de/stunserver-coturnserver/

@stephenw10 Thanks for that!

@gstlouis
I'm also using the apcupsd package on an pfSense installation. The UPS supplies a Proxmox server. On this I installed apcupsd as well.
The service connects to pfSense via NIS and gets the UPS status from it and triggers its shutdown on its own.

The shutdown of the server works as expected on power outages this way.
Just ensure that the other hosts shutdown before pfSense.

@stephenw10 ok I will try it later on my test machine

@chpalmer so I have to reboot the modem to connect a new device to the modem Ethernet, that was one thing that wasn't happening today. Got it.

Still no uptream support for the 113 version as far as I can see.

But personally I'd choose an x520 over that every time. 😉

@james-braga said in after upgrade to 24.11: squid doesn´t start:

https://github.com/pfsense/FreeBSD-ports/commit/009dc5f68e0cf1d1a767d1a9119bcbaface44823

It's a patch to ports so you need to adjust the Path Strip Count to 4.

@bmeeks Thanks for the post, but I saw that too. I searched high and low and so far nothing to explain why the “top -aSHm io -o write” command will not show details, only the header. I really need to find how to get the details of what is writing to the SSD (no EMMC here). Many others have done so.

@bmeeks @stephenw10 @michmoor

Just an update. I removed SNORT package and swap usage went down to %7

@bmeeks as you pointed I was using SNORT on a few vlan interfaces and subscribed to paid rules. Since SNORT is not going to be moving to newer releases in PFSENSE anytime soon and I have no technical justification to use it in my home network (LOL - I know, "But I wanted to learn"). Other real world problems take priority.

Will open another thread about file useage, thank you all for the pointer hopefully others will benefit from this thread.

@SteveITS said in Is it *always* good to update pfSense?:

https://docs.netgate.com/pfsense/en/latest/releases/25-03.html#dashboard

Thanks Steve,
The Redmine log appears to be quite positive. Meanwhile I reversed this patch:

Subject: [PATCH] Refresh widgets at specified intervals. Fix #15725

which made it a little bit better, but I am pleased to see that 25.03 will bring a definitive fix.

@26289 said in pfsense openvpn status:

Any advice on how to fix this?

tell use what you found here :

0a77966c-1f14-4b59-8563-631fd0bbc741-image.png

the log messages always tell you when things go 'wrong'.