OPNsense Forum
Archive => 18.1 Legacy Series => Topic started by: elektroinside on March 05, 2018, 09:57:38 pm
-
I updated remotely. Everything seems to work well in my case (PPPoE, OpenVPN, IDPS etc).
Thank you for your hard work!
-
Gladly. More people helped test edge cases that lead to upcoming fixes, e.g. multi-WAN failover with default gateway switching. 18.1.4 will be out on Thursday already to address ongoing CVEs with StrongSwan and DHCP.
So: thank you!
-
Will the Firewall reboot after that upgrade?
That information would be placed well in the changelog.
With that info I can upgrade the Firewall during my work-time or I need to plan it for later that day.
-
I rebooted mine manually.
In production environments, my advice would always be to update when it is possible to reboot and to debug, not to disrupt operations in case things go south.
-
Flawless upgrade here too.
Rebooted manually,,, as always.
-
Will the Firewall reboot after that upgrade?
That information would be placed well in the changelog.
With that info I can upgrade the Firewall during my work-time or I need to plan it for later that day.
It will tell you when it needs to reboot with a text and a confirmation dialog. Been this way for a long time. :)
-
18.1.3 hasn't been totally flawless. Nor is any new release. Which is why we have updates.
Hats off to the OPNsense devs for their dedication and quick response to issues.
-
I said the upgrade was flawless. :)
-
Sadly not entirely successful for me as OpenVPN Server doesn't start, a reboot didn't solve it either: Cannot open TUN/TAP dev /dev/tun1: Device busy (errno=16)
-
I followed https://forum.opnsense.org/index.php?topic=6376.0 (https://forum.opnsense.org/index.php?topic=6376.0) which fixed the issue but a reboot should fix such an issue as well, so I'm not sure if someone else is also affected.
-
No issues here... not with gateways, monit or OpenVPN.