pfSense Plus software version 22.05 is now available for upgrades!
-
Upgraded to 22.05. Everything is working just fine.
FYI - this bug #13280 seems like a rather simple fix, but still lingers...
-
After upgrading from 22.01 to 22.05 squid will not restart my hardware is
Netgate 7100
Serial: 1437180160
Netgate Device ID: cbb6503caf8accb0bedd -
@dgall Neither will snort 4.1.6, it gives the following error message:
Jun 27 19:42:23 php 50858 /tmp/snort_igc2_startcmd.php: The command '/usr/local/bin/snort -R _34675 -D --daq pcap --daq-mode passive --treat-drop-as-alert -l /var/log/snort/snort_igc234675 --pid-path /var/run --nolock-pidfile --no-interface-pidfile -G 34675 -c /usr/local/etc/snort/snort_34675_igc2/snort.conf -i igc2' returned exit code '1', the output was 'ERROR version 28 < 29' -
@pfsjap Reinstall made it downgrade to 4.1.5_3, which started ok.
-
3 hours, 2 minutes to download the installation image provided for me SG5100. 38KB/sec! I swear I didn’t hear the dial up modem sound when I turned on the computer. And no one told me I’ve got mail.
-
@gabacho4 said in pfSense Plus software version 22.05 is now available for upgrades!:
I swear I didn’t hear the dial up modem sound when I turned on the computer. And no one told me I’ve got mail.
-
Updated a 6100, 4100, 2100, and older 2220 so far with no issues.
OpenVPN site to site, client servers, and IPsec site to site tunnels no issues so far. Have a bunch more to upgrade over the next while but wanted to get the 4100 and 6100 updated because the 4100 is being sent out soon to a remote location with an OpenVPN back to 6100 and I would rather download and test update here first rather than remotely. -
@pfsjap I had to uninstall and reinstall. Then Squid came up.
-
@reberhar I also had some problems with pfblocker not working.
-
I ended up doing a reinstall on my SG1100 so that I could get access to “ZFS boot environments”. Personally I think this is an amazing feature and had to have it. So far everything restored cleanly and has been stable for the last couple hours.
-
Upgrade a 22.01 to 22.05 on a 4100.
Checked the upgrade logs and now checking all the logs.
Can't find any issue .what so ever ... really ?!
I use :
The "patches" list shows
Nice
-
@dgall uninstalled squid and 2 reboots later everything is working
-
I upgraded from 22.01 to 22.05 and I now have 100% CPU usage for the last day. When I disable pfBlockerNG it goes back to normal. As soon as I re-enable it the CPU goes back to 100% it was working fine on 22.01, what is the best way to diagnose why pfBlockerNG is now using 100% CPU usage?
Thanks
Rockyuk
-
Reminder: If you have issues, start a new thread in an appropriate category (e.g. General pfSense Questions).
This thread is an announcement and not intended for diagnosing problems.
-
@rockyuk I don't know why you are at 100% cpu usage with pfBlocker. For me it was the downloading and installing of the UTI adult category. I watched the processes on TOP and they pretty well told the story. Dropping to the command line and running
top -aSH
helps to understand the processes that are using up the cycles.
Roy
-
Upgrade from 22.01 to 22.05 on my SG-1000 was successful (only Bandwidthd package installed). It always takes 15+ minutes to reboot and come back up, but it's working.
Mark
-
I have upgraded main Router and two of my smaller router to 22.05. With this in mind I ran a test on a small router first. The upgrade went perfect and the upgrade did install perfectly. Now for the problem. If you run openvpn's new version on both router for a site to site vpn I can not get them to stay up at all. They connect fine then drop. I currently run it as TCP. but here is what I have tried all while taking down smaller sites all day yesterday to try to fix this issue.
- I change the connection to UDP instead of TCP (added the firewall rule)
- I changed the SHA to SHA512
- I created a TLS KEY for HMAC Auth and Shared that between the 2
- I removed all Encryption Algos except AES-256-GCM on both for main and fall back
- I remove DH
And it still will not stay connected...
However if you run 21.05 to 22.05 it will work fine.
Thank you
-
So what are your Ping settings set at?
I lost my network periodically and had to change my ping setting
Ping settings
Inactive
Causes OpenVPN to exit after n seconds of inactivity on the TUN/TAP device.
Activity is based on the last incoming or outgoing tunnel packet (not control or keep-alive packets).
A value of 0 disables this feature.WARNING: Use with caution. When triggered, the client process will exit and it will not automatically restart.
Ping method
keepalive helper uses interval and timeout parameters to define ping and ping-restart values as follows:
ping = interval
ping-restart = timeout
Interval
Timeout -
@reberhar cut and past didn't get it. I am at 10 and 300
-
@reberhar You can also set a service watchdog (install package) to keep the openvpn service running if disconnects. This has been an issue with OpenVPN site to site for a very long time - when disconnects seems it never reconnects by itself again.
