Connectivity API does not allow routes to be set

[Jonas G. Drange]

There is no way to edit the route configuration in VPN connections, as required by [1] and [2] from [3], in the Connectivity.

[1] https://wiki.ubuntu.com/Networking?action=AttachFile&do=get&target=vpn-setup-routes.phone.png
[2] https://wiki.ubuntu.com/Networking?action=AttachFile&do=get&target=vpn-setup-routes-add.phone.png
[3] https://wiki.ubuntu.com/Networking#VPNs

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bill Filler (bfiller)]

we need this in order to land VPN support in system settings

[Bill Filler (bfiller)]

the reason this is needed is that without it when you make a vpn connection you can *only* connect to resources available within the vpn and nothing outside of it. That is very limiting and not what users will expect.

[Bill Filler (bfiller)]

if having full configuration of the route is difficult, a possible compromise for first release would be to support all networks by default. that is, all network resources should be available even when vpn is active

[Launchpad Janitor (janitor)]

This bug was fixed in the package indicator-network - 0.7.1+16.04.20160304-0ubuntu1

---------------
indicator-network (0.7.1+16.04.20160304-0ubuntu1) xenial; urgency=medium

  [ CI Train Bot ]
  * Resync trunk.

  [ Pete Woods ]
  * Add never default property (LP: #1546573)
  * Use a shared pending settings instance so we don't overwrite rapid
    incoming changes (LP: #1546559)

 -- Pete Woods <email address hidden> Fri, 04 Mar 2016 11:14:03 +0000