net_gateway adds route on wrong interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager-OpenVPN |
Unknown
|
Unknown
|
|||
network-manager-openvpn (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
When using push route on server side to bypass the vpn for a specific subnet :
push "route 1.2.3.0 255.255.255.0 net_gateway"
The network manager registers the route on tun0 instead of net_gateway interface :
NetworkManager[
See the route in kernel :
1.2.3.0 192.168.0.1 255.255.255.0 UG 0 0 0 tun0
192.168.0.1 is on eth2
but route is registered on tun0
and traffic to 1.2.3.0/24 is sent to tun0 instead of eth2
When I launch openvpn in command line I get the correct route :
us=482299 PUSH: Received control message: 'PUSH_REPLY,
us=490292 /sbin/route add -net 1.2.3.0 netmask 255.255.255.0 gw 192.168.0.1
and the route appears on eth2
1.2.3.0 192.168.0.1 255.255.255.0 UG 0 0 0 eth2
then traffic to 1.2.3.0/24 flows through eth2 as expected
description: | updated |
Changed in network-manager-openvpn (Ubuntu): | |
status: | Expired → Confirmed |
Confirm: I have the same issue here.
Can't add new users easily for roaming. We stick to previous solutions for now (pptp or windows platforms).
Cheers,