nm-openconnect doesn't allow custom routes without a gateway
Bug #1801386 reported by
David Lawson
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-openconnect (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The OpenConnect VPN configuration page allows you to define manual routes rather than using pushed routes from the VPN server, however if you don't set a gateway for the route you can't apply the configuration. This should be a completely valid configuration, the route should be set up to route out the VPN interface (vpn0 typically) and routed automatically after going out that interface.
You can replicate this by setting up an openconnect VPN connection, turning off automatic route propagation and filling in the network and netmask in the route table, the apply button will be grayed out and the gateway field will be bordered in red until you fill the gateway field in.
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.