Invalid host route to default gateway set with net_gateway option

Bug #1528537 reported by Robert Sander
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-openvpn (Ubuntu)
New
Undecided
Unassigned

Bug Description

We are pushing routes from our OpenVPN server as follows:

push "route 203.0.113.0 255.255.255.0"
push "route 203.0.113.64 255.255.255.248 net_gateway"

i.e. we want 203.0.113.0/24 routed through the VPN tunnel but not 203.0.113.64/29 which shoould be routed via the default gateway of the client.

The client does not set a default route through the VPN tunnel.

When running openvpn from the command line everything works as expected, a separate route for 203.0.113.64/29 is created.

With NetworkManager odd behaviour is observed:

The default gateway (e.g. 192.168.1.1) gets a host route through the tunnel. In the end that disables all network traffic because OpenVPN is not able to route its own packets.

Something in the combination of OpenVPN and NetworkManager gets confused when it sees a route pushed with "net_gateway".

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.