Arch Linux

Description:
VPNs that have a routing rule with an IP prefix of 0 (e.g. 0.0.0.0/0) to route all traffic be default currently have the routing rule ignored. As a result, these VPN connections will fail to connect.

Additional info:
* Upstream issue: https://gitlab.gnome.org/GNOME/NetworkManager-openconnect/-/issues/52
* Upstream commit that fixes the issue: https://gitlab.gnome.org/GNOME/NetworkManager-openconnect/-/commit/ca4187c54b4b86a5557ca9464ee6a694e86ab344

I noticed that the current package points to a specific commit rather than the last official release, likely due to the very lengthy and inconsistent release schedule of the upstream package. I'd like to request that the commit be updated to include this patch.

The core networkmanager package has a similar issue and fix. (issue: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/711, commit: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8acad5a20cc61081438294efc634c0e245452e35) Based on the tags for their release, it looks like it will probably be part of the next major release. (1.32) The core networkmanager package seems to have a much more regular release schedule, so I'm not sure if it's worth creating a separate ticket to explicitly bring in that fix in Arch.

Steps to reproduce:
1. Connect to a VPN that has a routing rule of 0.0.0.0/0.
2. Connection fails to work as the routing rule is rejected.