Gateway not working anymore in routed IPsec (Azure)

Started by alh, April 30, 2021, 07:08:26 PM

Previous topic - Next topic
After upgrading to 21.5 the gateway setup on the IPsec interface as described in this manual

https://docs.opnsense.org/manual/how-tos/ipsec-s2s-route-azure.html

does not work anymore. The error message is:

Cannot add IPv4 Gateway Address because no IPv4 address could be found on the interface.

However, I have access to the remote network and all but I do need the gateway for the static route no?






P1 use start immediate and check if the Tunnel comes up in general

The tunnel comes up fine and I can ping the virtual machines on Azure. In the route I find the linked gateway and the gateway itself a bit strange...


It does somehow work (did not dare to reboot) but why is my gateway "defunct" and why can I not add an IP address to it anymore?

I have the same issue with routed ipsec between two OPNSense Firewalls:

If I want add a IP to the Gateway for the Ipsec Interface I get only:

The following input errors were detected:

    Cannot add IPv4 Gateway Address because no IPv4 address could be found on the interface.

If I leave the IP empty the Gateway is defunct.

How can I add a Gateway for routed ipsec?





I can not add the Gateway.

See step 5 from https://docs.opnsense.org/manual/how-tos/ipsec-s2s-route.html#step-5-define-gateways

Possible it is only a problem in the GUI? Can I add a Gateway in the shell with a command?


solved by:
opnsense-revert -r 21.1 strongswan
opnsense-revert -r 21.1 opnsense   :(

Now I can add the gateway with ip again.  :)

It would more help to test reverting only opnsense and not strongswan and then go back version to version to see which one is affecting. Then the devs can find the commit and fix the error