wcrowder last edited by
Upgrade to 2.2-Release went flawlessly!!!! 3 routers, but I planed ahead. :-*
BeerBelli last edited by
I installed the upgrade today on my Netgate FW 7541. Working just fine here. Thanks pfSense!
mikeisfly last edited by
upgraded 6 boxes 5 of the Dell PCs and 1 Atom based machine. All is well so far.
Venlaw last edited by
Did a fresh install, changed some partitions, restored backup from 2.1.5. Everything working perfect.
phil.davis last edited by
Mix of 10 Alix 2D13 and APU.1C systems running 2.2-RELEASE with no problems. All upgraded remotely across OpenVPN.
1 more to do at a remote site that seems to be powered off this weekend.
But I already new these hardware worked because I also had them at home with similar configs and upgraded at home first and checked all OK.
bmeeks last edited by
Although it was only a single home firewall, my upgrade from 2.1.5 to 2.2 was also pretty much flawless. I run the OpenVPN Client, Snort and NUT packages. The only semi-weird thing I noticed was 2.2 seems to have attempted an auto IPv4 Dynamic Gateway setup for my Hurricane Electric IPv6 tunnel along with the expected IPv6 Dynamic Gateway. I had never seen that behavior with the 2.1.x upgrades.
Cino last edited by
I saw that too Bill… I disabled the monitor for that gateway in Routing.
kejianshi last edited by
"The only semi-weird thing I noticed was 2.2 seems to have attempted an auto IPv4 Dynamic Gateway setup for my Hurricane Electric IPv6 tunnel along with the expected IPv6 Dynamic Gateway."
Same here on 2 boxes. I just deactivated it. No harm done. Just don't like looking at ugly blue colors on my dashboard.
wbond last edited by
Running 2.2 for about 24 hours here. I played it safe and installed to a spare SSD on a second machine, swapped drives and restored the 2.1.5 configuration backup. Only running a few packages, snort, nut, avahi and they reinstalled fine after the restore reboot.
The only minor thing I've noticed is that the gateway dashboard widget is showing impossibly low RTT values, on average about 5ms when it should really be about 25ms, which is what 2.1.5 was showing (ping shows about the same, mid 20's).
Thanks to those involved in this release!