We had exactly the same problem with a new OPNsense setup. I settled with using the legacy Tunnel Settings.
Having the same worries, that the legacy Interface will be deprecated at some point, it would be great to have a Azure Basic SKU compatible proposal available in Connections.
Is there a reason why it was changed from the more flexible way of setting the parameters (encryption, hash, dh) seperatly to these predefined combinations?
Besides missing combinations, I personally find it more inconvenient to find the desired combination in that huge list of options.
Having the same worries, that the legacy Interface will be deprecated at some point, it would be great to have a Azure Basic SKU compatible proposal available in Connections.
Is there a reason why it was changed from the more flexible way of setting the parameters (encryption, hash, dh) seperatly to these predefined combinations?
Besides missing combinations, I personally find it more inconvenient to find the desired combination in that huge list of options.