Hey everyone,

i'm sorry, i don't know about the current status of the initial bug
reported as several different workcases have mingled here since then,
and my nm7.0 has already become old (testing portage tree of gentoo)

the original bug was, as i understood:
the route to the PPTP server has to pass over a (local) gateway, f.ex. 
192.168.178.1 in my case. when nm-pptp is connected to the server it resets the 
default route to point to the pptp server (correct behaviour as no specific 
routing info is configured).

But doesn't set a host route to the pptp server which would use the
original (local) gateway, so that the connection between pptp-client and
server is severed and expires after a timeout.

This bug still applies to my nm-pptp installation (networkmanager pptp
0.7.0).

It can be solved, by a script in /etc/ppp/ip-up.d/50-nm-vpn.sh:

[ ${6:0:8} = "nm-pptp-" ] || exit 0     # makes sure we only touch nm-pptp- 
connections
VPNNAME=$(ps -C pppd -o args= | cut -d ' ' -f 4)    # obtains the hostname or 
ip of the pptp-server (will not work with multiple connections!!!)
VPNIP=$(ping -c1 $VPNNAME | grep PING | sed 's/^[^(]*(\([^)]*\)).*$/\1/')  # 
resolves its ip
ip route add $(ip route get $VPNIP | sed 's/^\(.*\)cache.*$/\1/')  # corrects 
the routing info

which uses 'ip route get <ip of the pptp server>' to find the correct
routing configuration to reach the server.

-- 
PPTP plugin for network manager sets wrong routing table entries
https://bugs.launchpad.net/bugs/113622
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to