network-manager-pptp forgets to add a route when connecting to (split) VPN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-pptp (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
What I expected to happen:
Connect successfully to company VPN, use company resources normally.
What happened instead:
Connect successfully to company VPN, can not do anything, network is dead.
The company VPN is set up only for some services, so in the VPN-settings,
"Use this connection only for resources on its network" is checked.
It is working on Windows without any problems, so i looked at the routing table
and saw that a route is missing on ubuntu:
original routing table, vpn enabled:
$ route
Kernel-
Ziel Router Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
10.20.40.100 * 255.255.255.255 UH 0 0 0 ppp0
link-local * 255.255.0.0 U 1000 0 0 eth0
192.168.1.0 * 255.255.255.0 U 1 0 0 eth0
193.XXX.XXX.XXX 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
193.XXX.XXX.XXX 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
"fixed" (in my case) routing table, vpn enabled and fully working:
$ route
Kernel-
Ziel Router Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
10.0.0.0 * 255.0.0.0 U 0 0 0 ppp0
10.20.40.100 * 255.255.255.255 UH 0 0 0 ppp0
link-local * 255.255.0.0 U 1000 0 0 eth0
192.168.1.0 * 255.255.255.0 U 1 0 0 eth0
193.XXX.XXX.XXX 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
193.XXX.XXX.XXX 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
The workaround is to add a route manually, targeting the company network, using ppp0
Windows adds this route automatically.
Please fix this bug, this was very time-consuming and annoying to find out the root cause of the problem.
$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
$ apt-cache policy network-
network-
Installiert: 0.9.2.0-1ubuntu1
Kandidat: 0.9.2.0-1ubuntu1
Versionstabelle:
*** 0.9.2.0-1ubuntu1 0
500 http://
100 /var/lib/
This bug appears in Ubuntu 11.10 too.
Status changed to 'Confirmed' because the bug affects multiple users.