To 2.6.0 and => 22.01 or not ? that is the question :)
-
Hi,
updated 2 machines (Intel and APU2 AMD) without any issues. (one had 2.6.0 RC). Unspectacular ... :-)
Intel from 2.5.2 -> 2.6.0
APU2 from 2.6.0RC -> 2.6.0Regards,
fireodo -
From 2.6rc to 2.6 on kvm virtual.
For some reason, after upgrade dpinger and dhcp server didn't start.Rebooting once more fixed the "issue"
So far so good.
-
@chudak said in To 2.6.0 or not ? that is the question :):
I have not done it yet and assuming that packages are to be updated AFTER this upgrade.
Packages will be updated as part of the upgrade.
You should not try to update any packages before upgrading unless you set the update branch to 2.5.2-deprecated.
Steve
-
I have been running 2.6 development snapshots and then 2.6-RC. Updated to 2.6-Release this morning. The update took a little longer than I expected and things were a little slow to start up after the reboot, but nothing broke.
Everything is working with no problems to report.
-
My uptime before the upgrade was 200 odd days, so I did a pre-emptive clean reboot first before I went to 2.6.
It then upgraded to 2.6, no problems at all.
Then subsequently upgraded to Pfsense Plus 22.01- again, no problems. In fact, it's actually fixed a couple of things which were broken and I hadn't got round to fixing (mail reports) - so that's a bonus!
All in that process took about 10 mins, can't complain about that. Spot on.
I have one of those dedicated Protectli devices.
-
I saved my configuration just in case, and manually rebooted the unit. I started update process, and once it was done, machine rebooted automatically. System came up as usual, no problems at all.
-
No issues here. From 2.6.0RC to 2.6.0 to 22.01.
Using pfBlockerNG-devel, Wireguard, OpenVPN, IPSec, 2 WANs, 5 LAN interfaces, Hybrid NAT on VMware ESXi and dedicated hw (Supermicro SYS E200-8D, SYS E50-9AP-N5). -
I got problems on Hyper-V, had to go back to 2.5.2.
-
Not ready yet....
NAT not working inbound on non-standard ports and update check fails. NAT between VLANS not working.
-
Hi,
I updated a ZOTAC ZBOX CI325 nano Mini PC (the ones with the re0 NICs) from 2.5.2 > 2.6.0. Everything went well except that my Wireguard tunnels didn't come up automatically. I had to perform a reboot of the box as a restart of the tunnels from VPV>Wireguard did not bring them up.
-
Upgraded to 2.6.0 with no glitch, very smooth process this time!
Stopped short to do => 22.01 upgrade.
The main reason I am not sure why I should do it.Wonder what other users do/think?
Note - I am thinking to get a Nergate appliance just to support them, so far did not find a good option for my 4 port custom I5 mini PC replacement.
-
@bob-dig What sort of problems? Slow WAN? I updated to 2.6 on Hyper-V (2022) and WAN speeds tanked (2Mb/1Mb down from 1Gb/200Mb). Unusably slow after an in-place upgrade or vanilla install. LAN speeds are normal.
-
@boelter WAN-Speed is ok for me (full 250 MBits/s), inter (V)Lan communication is not usable. But someone else seems to have your problem, see here.
@boelter said in To 2.6.0 and => 22.01 or not ? that is the question :):
or vanilla install.
Good to know, thanks.
-
@boelter It's probably not your case, but I checked WAN speed on the wired box and a Windows VM on 1GB fiber and it seems actually better on 2.6.0
FYI -
Snort failed to update, maybe unrelated to this topic
Just FYIhttps://forum.netgate.com/topic/169929/snort-upgrade-stuck-on-2-6-0
-
Just went from 2.5.latest to 2.6.0 then 22.01with no apparent issues.
Hardware is a Dell Optiplex Desktop with a 1TB SSD (it's what I had at the time ¯\_(ツ)_/¯ so... )
Other than forgetting to input my GELI password on the console during reboot it went fast and smooth.
ZFS widget is nifty!
Bunch of packages:
Name Version
acme 0.6.10_1
arping 1.2.2_2
arpwatch 0.2.0_6
Backup 0.5_6
bandwidthd 0.7.4_5
Cron 0.3.7_5
Filer 0.60.6_5
iperf 3.0.2_5
mtr-nox11 0.85.6_2
nmap 1.4.4_2
nut 2.7.4_10
openvpn-client-export 1.6_4
pfBlockerNG 2.1.4_26
RRD_Summary 2.0_1
Service_Watchdog 1.8.7_1
Status_Traffic_Totals 2.3.2_2
sudo 0.3_6
tftpd 0.1.3_3
WireGuard 0.1.6_1Wireguard was actually installed after upgrade.
Houston, everything appears nominal...
-
Finally did 2.6.0 => 22.01 with no issues :)
I am still "afraid" to switch to ZFS, need to become brave and bite the bullet.
-
Hmmm, missing an indicator on the ZFS widget for individual filesystems that are RAM based. You know, non-critical ones like /var... Did I miss something?
-
@daplumber said in To 2.6.0 and => 22.01 or not ? that is the question :):
...missing an indicator on the ZFS widget for individual filesystems that are RAM based...
On the dashboard page, scroll down to "Disks" and click the "
>/" icon. You should see/tmpand/varusing filesystemtmpfs. -
@bpsdtzpw I have a ZFS root, what "Disks" section?
Here's my "zfs list":
[22.01-RELEASE][USER@MYSYSTEM]/home/USER: zfs list NAME USED AVAIL REFER MOUNTPOINT zroot 88.0G 772G 96K /zroot zroot/ROOT 1.95G 772G 96K none zroot/ROOT/default 1.95G 772G 1.95G / zroot/reservation 96K 858G 96K /zroot/reservation zroot/tmp 120K 772G 120K /tmp zroot/var 6.82M 772G 6.82M /varI've tried to upload a screenshot, but it keep erroring on post.
