Public bug reported:
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".
** Affects: network-manager-openvpn (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528537
Title:
Invalid host route to default gateway set with net_gateway option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1528537/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
