@manjotsc Great! I'm just going to reference this other thread on the same topic, same solution.

@keyser Seeing that FreeBSD 14 is now at the core of pfSense in 23.01, and Wireguards ChaCha20-Poly1305 cipher has been made available for both IPsec and OpenVPN DCO, where are we in terms of hardware acceleration of this stream cipher? It rumours here and there but not really something that will be available soon for usage. Is it supported at all at this point? The new Intel Atom C5000 or P5000 SoC series will be sorted with QAT 2 or QAT 3 as I am informed. If so in which cases - AES-NI, QAT on Intel? SafeXcel on > arm? The DPDK has something right now "available", that is using the Intel QAT to support the ChaCha-Poly algorithm as I know it is the only available source about at this time. This patchset adds Chacha20-Poly1305 implementation to Intel QuickAssist Technology pmd. I know ChaCha20 is much faster (soft) on the CPU than traditional AES block ciphers, but still, Intel released benchmarks on linux that showed wireguard could see anything from 3 to 10X speed increase using AVX512 and QAT. Linux is not FreeBSD, and FreeBSD is the underlying OS for pfSense. They are both "unixoide" OS but nothing more. I would really like to switch to Wireguard for my Site 2 Site tunnels, but since I have SG-2100’s in the other end, The ARM architecture is different from the x86_64 and comes also with an own crypto unit, its strong and powerful but not the same as Intel QAT.

@00sjsl said in After upgrading to 23.01 Status/Monitoring Thermal Sensors not updating: I'm curious as to why corbuc_0 (which seemed to convey real information) is gone, but thermal_tz0 which is always 26.9 C remains. Sorry, I don't know the why, just the what.

@tiekoetter After upgrading to 23.01 I noticed some issues: The most of us all, more or less. I find out the best methods told around here and over the internet was the following; Fresh install 2.7 and upgrade to the 23.01 and then over CLI upgrade to the latest version 23.01 RC From 2.6 (zfs) to 2.7 and then to 23.01 and once more to 23.01 RC as now would be the best two ways to walk. Upgrade > reboot > update the packets and reboot again let went away many of the most problems of my box.

@stephenw10 Yep, going to look in to a noctua cpu fan.

@stephenw10 I guess I just removed and pasted and didn't really pay attention to what was before. But confirmed on another 23.01 and indeed it is. So I have no idea about what 'fixed it'. I repeat the same steps as before when I got the error, and I can't replicate.

@stephenw10 Thank you! I went back and downloaded the correct version. That didn't fix my core issue, but it did clear up why I was not seeing those choices.

@steveits thank you. I don't know if my lastpass is trying to log me in, but this is the first time I have even heard of CSRF. I was going to clear cookies and try again, but on Ubuntu 22.04 Vivaldi and Firefox time out getting to the appliance (192.168.1.1). It works fine on Windows and Ubuntu 20.04.

@nrgia Im not worried at all. I perfectly understood what @rcoleman-netgate said. Also, im in no rush to upgrade. I have zero issues with 2.6.

@markusboberg When you get the connection up, come back and I can help you with IPv6. One thing you'll want to ask your ISP about is prefix size.

Yup, sorry, I tested from a box that is using our internal repo. Since it has been built and is there now it's probably only a matter of syncing them.

So the pfSense webgui on the remote pfSense at the client? Or some web server behind it? Seeing a bad cert like that implies either the cert has expired or it's not the expected cert for the site. It also implies you must be using https not http. Steve

@rcoleman-netgate thanks for help. I opened a ticket and attaeched xml-file. I will inform you, when I got solution.

Changing to FreeBSD 14 and to PHP 8.1 may be more work as we all imagine of. But the effect to spare out FreeBSD 13 and the gain for us all may be then greater as we will ever find out.

@jonathanlee said in Missing package repository after failed upgrade to 23.01. Please help: For me the fresh install solved all my issues so far. I'm happy to hear that. I am still in the midst of things, but one of these days I'll get it. :)

I've occasionally seen a session end earlier than expected but not consistently. Any events in the logs around the time the session unexpectedly expired?

@stephenw10 so is there a tiktok should be following to look for these dances hehehe @deanfourie to your update to 14 possible question - yes it is possible, just upgrade to 23.01.. 2.7 is also 14, so you could run one of the snaps of that. [image: 1676823118810-14.jpg]

@steveits said in BandwidthD not capturing any toptalkers: @jarhead said in BandwidthD not capturing any toptalkers: have it open in a new tab instead of the current tab. It defaults to a framed view when accessed from the Diagnostics menu. Are you clicking the "click to remove frame" link? or maybe going to that page directly? I didn't realize it was accessible directly without logging in. (in our case, the firewall blocks that anyway) @michmoor I suppose it's relative, we get useful info for our limited purposes as we have only one subnet to watch. There is also the Darkstat package but I haven't had a reason to look at that. You're right, I was thinking of Darkstat, that one opens in the current window and should be a tab.