Package: network-manager Version: 0.9.10.0-4 Severity: important Tags: upstream
Dear Maintainer, Cannot establish VPN with pptp - any of the setting lead to the same result (default/split route, only resources..., automatic DNS). However, these settings do work on Ubuntu 12.04. After pptp connection is established, NM refuses to add IPv4 settings, noting: unspecific failure Log snippets: Dec 20 20:51:29 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' Dec 20 20:51:29 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... Dec 20 20:51:29 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (get_credentials): got credentials from NetworkManager-pptp Dec 20 20:51:31 pico pppd[2661]: CHAP authentication succeeded Dec 20 20:51:31 pico NetworkManager[659]: CHAP authentication succeeded Dec 20 20:51:31 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 8 / phase 'network' Dec 20 20:51:31 pico pppd[2661]: MPPE 128-bit stateless compression enabled Dec 20 20:51:31 pico NetworkManager[659]: MPPE 128-bit stateless compression enabled Dec 20 20:51:32 pico pppd[2661]: local IP address 192.168.221.2 Dec 20 20:51:32 pico pppd[2661]: remote IP address 192.168.221.1 Dec 20 20:51:32 pico pppd[2661]: primary DNS address 192.168.204.14 Dec 20 20:51:32 pico pppd[2661]: secondary DNS address 192.168.204.237 Dec 20 20:51:32 pico NetworkManager[659]: local IP address 192.168.221.2 Dec 20 20:51:32 pico NetworkManager[659]: remote IP address 192.168.221.1 Dec 20 20:51:32 pico NetworkManager[659]: primary DNS address 192.168.204.14 Dec 20 20:51:32 pico NetworkManager[659]: secondary DNS address 192.168.204.237 Dec 20 20:51:32 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 9 / phase 'running' Dec 20 20:51:32 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): ip-up event Dec 20 20:51:32 pico NetworkManager[659]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): sending Ip4Config to NetworkManager-pptp... Dec 20 20:51:32 pico NetworkManager[659]: <info> VPN connection 'Berlin' (IP4 Config Get) reply received from old-style plugin. Dec 20 20:51:32 pico NetworkManager[659]: <info> VPN Gateway: 212.144.118.2 Dec 20 20:51:32 pico NetworkManager[659]: <info> Tunnel Device: ppp0 Dec 20 20:51:32 pico NetworkManager[659]: <info> IPv4 configuration: Dec 20 20:51:32 pico NetworkManager[659]: <info> Internal Address: 192.168.221.2 Dec 20 20:51:32 pico NetworkManager[659]: <info> Internal Prefix: 32 Dec 20 20:51:32 pico NetworkManager[659]: <info> Internal Point-to-Point Address: 192.168.221.1 Dec 20 20:51:32 pico NetworkManager[659]: <info> Maximum Segment Size (MSS): 0 Dec 20 20:51:32 pico NetworkManager[659]: <info> Static Route: 192.168.192.0/20 Next Hop: 192.168.204.113 Dec 20 20:51:32 pico NetworkManager[659]: <info> Forbid Default Route: yes Dec 20 20:51:32 pico NetworkManager[659]: <info> Internal DNS: 192.168.204.12 Dec 20 20:51:32 pico NetworkManager[659]: <info> Internal DNS: 192.168.204.237 Dec 20 20:51:32 pico NetworkManager[659]: <info> DNS Domain: '(none)' Dec 20 20:51:32 pico NetworkManager[659]: <info> No IPv6 configuration Dec 20 20:51:32 pico NetworkManager[659]: <error> [1419105092.058788] [platform /nm-linux-platform.c:1714] add_object(): Netlink error adding 192.168.192.0/20 via 192.168.204.113 dev ppp0 metric 1024 mss 0 src user: Unspecific failure Dec 20 20:51:32 pico NetworkManager[659]: <warn> VPN connection 'Berlin' did not receive valid IP config information. Dec 20 20:51:32 pico pppd[2661]: Terminating on signal 15 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser 3.113+nmu3 ii dbus 1.8.12-1 ii init-system-helpers 1.22 ii isc-dhcp-client 4.3.1-5 ii libc6 2.19-13 ii libdbus-1-3 1.8.12-1 ii libdbus-glib-1-2 0.102-1 ii libgcrypt20 1.6.2-4+b1 ii libglib2.0-0 2.42.1-1 ii libgnutls-deb0-28 3.3.8-5 ii libgudev-1.0-0 215-7 ii libmm-glib0 1.4.0-1 ii libndp0 1.4-2 ii libnewt0.52 0.52.17-1+b1 ii libnl-3-200 3.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm-glib4 0.9.10.0-4 ii libnm-util2 0.9.10.0-4 ii libpam-systemd 215-7 ii libpolkit-gobject-1-0 0.105-8 ii libreadline6 6.3-8+b2 ii libsoup2.4-1 2.48.0-1 ii libsystemd0 215-7 ii libteamdctl0 1.12-1 ii libuuid1 2.25.2-4 ii lsb-base 4.1+Debian13+nmu1 ii policykit-1 0.105-8 ii udev 215-7 ii wpasupplicant 2.3-1 Versions of packages network-manager recommends: ii crda 3.13-1 ii dnsmasq-base 2.72-2 ii iptables 1.4.21-2+b1 ii iputils-arping 3:20121221-5+b2 ii modemmanager 1.4.0-1 ii ppp 2.4.6-3 Versions of packages network-manager suggests: ii avahi-autoipd 0.6.31-4+b2 pn libteam-utils <none> -- no debconf information _______________________________________________ Pkg-utopia-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
