Messages

Is upgrading to "18.7.r1" supposed to work?  Every time I get the notification in the GUI, hit "Unlock this upgrade", then "Unlock", and then "Upgrade now", I get:

***GOT REQUEST TO UPGRADE: maj***
Fetching packages-18.7.r1-LibreSSL-amd64.tar: .. failed
***DONE***

Same thing if I switch back to OpenSSL.

Hah, no rush.  Is there a better/more preferred way to handle this then?

I'm sure I have a somewhat weird setup for home/SMB, but it's probably fairly common in large environments..

I don't have machines directly attached on the 'internal'/'trust'/whatever side of OPNsense.  I have multiple interfaces, each one attached to a different L3 switch, which static routes set for each one.  Everything works great, but obviously since each interface has its own IP, it would be nice to use a loopback address for administration/management.  This is pretty common even for routing protocols in larger environments.

So I used Firewall: Virtual IPs: Settings to add a Virtual IP to the Loopback interface.  That loopback now works correctly everywhere, yay!  The only problem is in System: Settings: Administration, under HTTPS & SSH, Loopback isn't available as an interface to bind to.  I'm sure it's fairly easy to fix and I'm going to look at the code, but I'm curious if there's a reason not to other than "nobody has ever done it before"?

This is how I access all of my other networking gear (Extreme switch, HPe/H3C switch, Juniper SRX, etc), so I'm just trying to make it similar.