OpenVPN routes on 21.7.2_1

[md0]

Hi,

I have an OpenVPN server running on version OPNsense 21.7.2_1.
After updating to the latest firmware my OpenVPN routes for external clients are no longer added to the routing table. I can see them in the OpenVPN connection status page, but not on the main routing table. As such, no traffic is being routed towards the external VPN networks. Is this a known problem? Is there any workaround for it?

Thank you!

[chemlud]

Have here for long time now

Code: [Select]

OPNsense 21.7.2_1-amd64
FreeBSD 12.1-RELEASE-p20-HBSD
LibreSSL 3.3.4
and different openVPN tunnels (s2s), no problems with routes or routing in general...

[md0]

Found the problem: the "IPv4 Local Network" and "IPv4 Remote Network" fields in the OpenVPN configuration page contained spaces after the commas, which made the settings fail to apply silently. Removing the extra spaces and restarting the VPN server made everything go back to normal.

[Mad-Onion]

Damn! Had the same problem here after an upgrade to 21.7.2_1 - thank you very much!

The OpenVPN-GUI validates the field correctly and warns about spaces in the list of networks, but if you have those spaces migrated from a previous version, the routing won't work anymore.

[GaardenZwerch]

Have here for long time now

Code: [Select]

OPNsense 21.7.2_1-amd64
FreeBSD 12.1-RELEASE-p20-HBSD
LibreSSL 3.3.4
and different openVPN tunnels (s2s), no problems with routes or routing in general...

Thanks, that's it.... It's unfortunate that this is not corrected in the upgrade process. My appliances are managed through a tunnel, so this could potentially lock me out. I will have to be very careful.
Thanks!

[JohnDoe17]

This post deserves a thousand "likes!"

I just upgraded from 21.1.x and ran into this issue.  Thank you so much for the solution!

It does seem like something the upgrade process ought to 1) fix or 2) not introduce - it's unclear to me where exactly the issue lies.

JD17