vpn configuration requires to enter a gateway

Bug #1810660 reported by Efthymios
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)

Bug Description

After upgrading to 18.04 I can no longer create a vpn with a static route unless a gateway is specified.

Before (with 16.04) I could add 1 or more destination networks without a gateway for each. Once the VPN connection was established, all static routes defined would have a gateway the VPN device (e.g ppp0, tun0, etc), as below.

192.168.xxx.0/24 is the local network
10.0.xxx.0/24 are remote networks accessible through the VPN.

Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.xxx.254 UG 20100 0 0 enp0s25 UH 50 0 0 ppp0 UH 50 0 0 ppp0 UH 50 0 0 ppp0

Efthymios (efthymiosc)
affects: ubuntu-docs (Ubuntu) → network-manager (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :
affects: network-manager (Ubuntu) → gnome-control-center (Ubuntu)
summary: - vpn static route
+ vpn configuration requires to enter a gateway
Revision history for this message
Efthymios (efthymiosc) wrote :

Yes, seems to be the same. Running nm-connection-editor instead allows to save the configuration without a specific gateway.


Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in gnome-control-center:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.