Network Manager unable to connect to PPTP VPN (bad NT-Domain escaping)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-pptp (Ubuntu) |
Fix Released
|
High
|
Alexander Sack | ||
Intrepid |
Fix Released
|
High
|
Alexander Sack | ||
pptp-linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Intrepid |
Invalid
|
Undecided
|
Unassigned |
Bug Description
To verify:
1. check that you cannot connect to pptp and you are using a NT-Domain in the conncetion config
2. verify that this is your bug: leave the NT-Domain field empty; instead encode it in username like:
NT_
3. upgrade to fixed package and see that it works without the trick in 2.
Binary package hint: network-
Package version: 0.7~~svn2008081
uname -a: Linux jim-d620 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux
I am testing the SVN version of network-manager 0.7. I am attempting to connect to my employer's Windows PPTP VPN. Each time I try, the connection fails, displaying a pop-up message that says: The VPN connection 'Connection Name' failed because the VPN service stopped unexpectedly.
The relevant section of /var/log/syslog is:
Aug 18 15:15:13 jim-d620 NetworkManager: <info> Starting VPN service 'org.freedeskto
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
Aug 18 15:15:13 jim-d620 NetworkManager: nm_vpn_
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN plugin state changed: 3
Aug 18 15:15:13 jim-d620 pppd[16602]: Plugin /usr/lib/
Aug 18 15:15:13 jim-d620 pppd[16602]: pppd 2.4.4 started by root, uid 0
Aug 18 15:15:13 jim-d620 pppd[16602]: Using interface ppp1
Aug 18 15:15:13 jim-d620 pppd[16602]: Connect: ppp1 <--> /dev/pts/1
Aug 18 15:15:13 jim-d620 pptp[16603]: nm-pptp-
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN connection 'Connection Name' (Connect) reply received.
Aug 18 15:15:15 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:17 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:17 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:18 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:18 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:18 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:19 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:19 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:19 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:19 jim-d620 pppd[16602]: LCP terminated by peer (wM-(?"
Aug 18 15:15:19 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:22 jim-d620 pppd[16602]: Connection terminated.
Aug 18 15:15:22 jim-d620 pppd[16602]: Modem hangup
Aug 18 15:15:22 jim-d620 pptp[16603]: nm-pptp-
Aug 18 15:15:22 jim-d620 pptp[16603]: nm-pptp-
Aug 18 15:15:22 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:22 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:22 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:22 jim-d620 pppd[16602]: Exit.
Aug 18 15:15:22 jim-d620 NetworkManager: <info> VPN plugin state changed: 6
Aug 18 15:15:22 jim-d620 NetworkManager: <WARN> connection_
My internet connection is via a Sierra AC 595 PCMCIA aircard, which is managed by Network Manager and seems to work fine. The VPN connection worked using wired and wireless connections and NM 0.6.6. I switched to 0.7 because I couldn't use the VPN with the aircard under 0.6.6, I think because of this bug: https:/
Related branches
Severin H (severinh) wrote : | #1 |
Morten Holmstrup (robotjox) wrote : | #2 |
just confirming this bug. Trying to connect to pptp vpn on intrepid - exactly the same errors.
janrikard (janrikard) wrote : | #3 |
I think I have the same bug.
Pptp works when i connect to a win 2003 server.
And it does NOT work when i connect to a win 2000 server.
f1anker (ianspigeon) wrote : | #4 |
- syslog extract Edit (4.1 KiB, text/plain)
Hey guys, Is there any further information I can supply to help get this bug confirmed? I can establish a connection successfully without NM via the command line just not using the new NM 0.7 Applet. syslog extract attached but is the same as reporter.
Client Configuration: MSCHAPv2/
network-
VPN Server: Win2k3 RAS/PPTP
Christoph Burgdorf (christoph-burgdorf) wrote : Re: [Bug 259168] Re: Unable to connect to PPTP VPN | #5 |
Hello there,
can you tell me what commands to type in order to get it connected on
the command line. I would like to try if that works for me, too...
Bye
Christoph
Am Sonntag, den 14.09.2008, 17:42 +0000 schrieb f1anker:
> Hey guys, Is there any further information I can supply to help get this
> bug confirmed? I can establish a connection successfully without NM via
> the command line just not using the new NM 0.7 Applet. syslog extract
> attached but is the same as reporter.
>
> Client Configuration: MSCHAPv2/
> network-
> VPN Server: Win2k3 RAS/PPTP
>
> ** Attachment added: "syslog extract"
> http://
>
> --
> Unable to connect to PPTP VPN
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “network-
>
> Bug description:
> Binary package hint: network-
>
> Package version: 0.7~~svn2008081
> uname -a: Linux jim-d620 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux
>
> I am testing the SVN version of network-manager 0.7. I am attempting to connect to my employer's Windows PPTP VPN. Each time I try, the connection fails, displaying a pop-up message that says: The VPN connection 'Connection Name' failed because the VPN service stopped unexpectedly.
>
> The relevant section of /var/log/syslog is:
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> Starting VPN service 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: nm_vpn_
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN plugin state changed: 3
> Aug 18 15:15:13 jim-d620 pppd[16602]: Plugin /usr/lib/
> Aug 18 15:15:13 jim-d620 pppd[16602]: pppd 2.4.4 started by root, uid 0
> Aug 18 15:15:13 jim-d620 pppd[16602]: Using interface ppp1
> Aug 18 15:15:13 jim-d620 pppd[16602]: Connect: ppp1 <--> /dev/pts/1
> Aug 18 15:15:13 jim-d620 pptp[16603]: nm-pptp-
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN connection 'Connection Name' (Connect) reply received.
> Aug 18 15:15:15 jim-d620 pptp[16607]: nm-pptp-
> Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
Changed in network-manager-pptp: | |
status: | New → Confirmed |
Christoph Burgdorf (christoph-burgdorf) wrote : Re: Network Manager unable to connect to PPTP VPN | #6 |
Is there anything I could supply to get this bug closed before the final release comes out?
Alexander Sack (asac) wrote : | #7 |
please also attach the vpn log of a usccessful connect attempt.
Christoph Burgdorf (christoph-burgdorf) wrote : AW: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #8 |
Where can I find this log?
-----Ursprüngliche Nachricht-----
Von: <email address hidden> [mailto:<email address hidden>] Im Auftrag von Alexander Sack
Gesendet: Donnerstag, 25. September 2008 14:24
An: Christoph Burgdorf
Betreff: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN
please also attach the vpn log of a usccessful connect attempt.
--
Network Manager unable to connect to PPTP VPN
https:/
You received this bug notification because you are a direct subscriber
of the bug.
Status in "network-
Bug description:
Binary package hint: network-
Package version: 0.7~~svn2008081
uname -a: Linux jim-d620 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux
I am testing the SVN version of network-manager 0.7. I am attempting to connect to my employer's Windows PPTP VPN. Each time I try, the connection fails, displaying a pop-up message that says: The VPN connection 'Connection Name' failed because the VPN service stopped unexpectedly.
The relevant section of /var/log/syslog is:
Aug 18 15:15:13 jim-d620 NetworkManager: <info> Starting VPN service 'org.freedeskto
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
Aug 18 15:15:13 jim-d620 NetworkManager: nm_vpn_
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN plugin state changed: 3
Aug 18 15:15:13 jim-d620 pppd[16602]: Plugin /usr/lib/
Aug 18 15:15:13 jim-d620 pppd[16602]: pppd 2.4.4 started by root, uid 0
Aug 18 15:15:13 jim-d620 pppd[16602]: Using interface ppp1
Aug 18 15:15:13 jim-d620 pppd[16602]: Connect: ppp1 <--> /dev/pts/1
Aug 18 15:15:13 jim-d620 pptp[16603]: nm-pptp-
Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN connection 'Connection Name' (Connect) reply received.
Aug 18 15:15:15 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:17 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:17 jim-d620 pptp[16607]: nm-pptp-s...
Fernando Miguel (fernandomiguel) wrote : Re: Network Manager unable to connect to PPTP VPN | #9 |
I failed to connect
Sep 25 16:50:01 blubug /USR/SBIN/
Sep 25 16:50:01 blubug /USR/SBIN/
Sep 25 16:50:02 blubug NetworkManager: <info> Starting VPN service 'org.freedeskto
Sep 25 16:50:02 blubug NetworkManager: <info> VPN service 'org.freedeskto
Sep 25 16:50:02 blubug NetworkManager: <info> VPN service 'org.freedeskto
Sep 25 16:50:02 blubug NetworkManager: <info> VPN plugin state changed: 1
Sep 25 16:50:09 blubug NetworkManager: <info> VPN plugin state changed: 3
Sep 25 16:50:09 blubug NetworkManager: <info> VPN connection 'matir' (Connect) reply received.
Sep 25 16:50:09 blubug pppd[13712]: Plugin /usr/lib/
Sep 25 16:50:09 blubug pppd[13712]: pppd 2.4.4 started by root, uid 0
Sep 25 16:50:09 blubug pptp[13714]: nm-pptp-
Sep 25 16:50:09 blubug pppd[13712]: Using interface ppp0
Sep 25 16:50:09 blubug pppd[13712]: Connect: ppp0 <--> /dev/pts/3
Sep 25 16:50:09 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:09 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:09 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:10 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:10 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:10 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:10 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:10 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:10 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:10 blubug pppd[13712]: CHAP authentication succeeded
Sep 25 16:50:10 blubug kernel: [27894.122099] PPP BSD Compression module registered
Sep 25 16:50:10 blubug kernel: [27894.221588] PPP Deflate Compression module registered
Sep 25 16:50:12 blubug pppd[13712]: LCP terminated by peer (,?8^Y^
Sep 25 16:50:12 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:12 blubug pptp[13721]: nm-pptp-
Sep 25 16:50:12 ...
Fernando Miguel (fernandomiguel) wrote : | #10 |
Enabling P2P Encryption (MPPE) makes this work.
Sep 25 16:55:01 blubug /USR/SBIN/
Sep 25 16:55:11 blubug dhclient: DHCPREQUEST of 10.0.0.139 on eth0 to 10.0.0.138 port 67
Sep 25 16:55:11 blubug dhclient: DHCPACK of 10.0.0.139 from 10.0.0.138
Sep 25 16:55:11 blubug NetworkManager: <info> DHCP: device eth0 state changed bound -> renew
Sep 25 16:55:11 blubug NetworkManager: <info> address 10.0.0.XXX
Sep 25 16:55:11 blubug NetworkManager: <info> prefix 24 (255.255.255.0)
Sep 25 16:55:11 blubug NetworkManager: <info> gateway 10.0.0.XXX
Sep 25 16:55:11 blubug NetworkManager: <info> nameserver '10.0.0.XXX'
Sep 25 16:55:11 blubug NetworkManager: <info> domain name 'router.XXXXX'
Sep 25 16:55:11 blubug NetworkManager: <info> (eth0): removing resolv.conf from /sbin/resolvconf
Sep 25 16:55:11 blubug dhclient: bound to 10.0.0.139 -- renewal in 17542 seconds.
Sep 25 16:55:11 blubug avahi-daemon[6152]: Withdrawing address record for 10.0.0.139 on eth0.
Sep 25 16:55:11 blubug avahi-daemon[6152]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.0.139.
Sep 25 16:55:11 blubug avahi-daemon[6152]: Interface eth0.IPv4 no longer relevant for mDNS.
Sep 25 16:55:11 blubug avahi-daemon[6152]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.0.139.
Sep 25 16:55:11 blubug avahi-daemon[6152]: New relevant interface eth0.IPv4 for mDNS.
Sep 25 16:55:11 blubug avahi-daemon[6152]: Registering new address record for 10.0.0.139 on eth0.IPv4.
Sep 25 16:55:12 blubug NetworkManager: <info> (eth0): writing resolv.conf to /sbin/resolvconf
Sep 25 16:55:12 blubug NetworkManager: <info> Policy set (eth0) as default device for routing and DNS.
Sep 25 16:58:57 blubug NetworkManager: <info> Starting VPN service 'org.freedeskto
Sep 25 16:58:57 blubug NetworkManager: <info> VPN service 'org.freedeskto
Sep 25 16:58:57 blubug NetworkManager: <info> VPN service 'org.freedeskto
Sep 25 16:59:03 blubug NetworkManager: <info> VPN plugin state changed: 3
Sep 25 16:59:03 blubug NetworkManager: <info> VPN connection 'XXXXX' (Connect) reply received.
Sep 25 16:59:03 blubug pppd[17344]: Plugin /usr/lib/
Sep 25 16:59:03 blubug pppd[17344]: pppd 2.4.4 started by root, uid 0
Sep 25 16:59:03 blubug pptp[17346]: nm-pptp-
Sep 25 16:59:03 blubug pppd[17344]: Using interface ppp0
Sep 25 16:59:03 blubug pppd[17344]: Connect: ppp0 <--> /dev/pts/3
Sep 25 16:59:03 blubug pptp[17353]: nm-pptp-
Sep 25 16:59:03 blubug pptp[17353]: nm-pptp-
Sep 25 16:59:03 blubug pptp[17353]: nm-pptp-
Sep 25 16:59...
Alexander Sack (asac) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #11 |
On Thu, Sep 25, 2008 at 04:11:46PM -0000, BUGabundo wrote:
> Enabling P2P Encryption (MPPE) makes this work.
OK, appears to be a config issue and not a bug then
status invalid
- Alexander
Changed in network-manager-pptp: | |
status: | Confirmed → Invalid |
kaman (kaman120) wrote : Re: Network Manager unable to connect to PPTP VPN | #12 |
My ISP doesn't support MPPE encryption and I cannot connect to PPTP VPN using Network Manager. I posted logs at https:/
Fernando Miguel (fernandomiguel) wrote : | #13 |
Alex with previous versions it worked out of the box.
This is, the very least, a serious regressions, since the menu is very well hidden and deselect by default.
Either we enable it by default (i'm not sure what this option is used for), or make/visible it clear for users to enable it.
Changed in network-manager-pptp: | |
status: | Invalid → Confirmed |
f1anker (ianspigeon) wrote : | #14 |
MPPE is enabled on my connection so maybe i'm hitting a different issue. Having said that, if I disable MPPE via nm applet the change isnt saved so maybe all is not how it should be. gconf shows the MPPE option is enabled.
All is good if I downgrade to nm 0.6 in Intrepid. Network Manager 0.7 failure attempt below;
Sep 29 19:38:37 laptop pppd[9971]: Connect: ppp0 <--> /dev/pts/0
Sep 29 19:38:37 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:37 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:37 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pppd[9971]: LCP terminated by peer (^C^R2Q^
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:38 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:41 laptop pppd[9971]: Connection terminated.
Sep 29 19:38:41 laptop pppd[9971]: Modem hangup
Sep 29 19:38:41 laptop pptp[9973]: nm-pptp-
Sep 29 19:38:41 laptop pptp[9973]: nm-pptp-
Sep 29 19:38:41 laptop pppd[9971]: Exit.
Sep 29 19:38:41 laptop pptp[9980]: nm-pptp-
Sep 29 19:38:41 laptop pptp[9980]: nm-pptp-
Stef Walter (stefw) wrote : | #15 |
I've tried every combination of options (MPPE enabled etc...) and cannot get my VPN connection (which used to work under Hardy) to work with the new network manager.
Logs follow:
Sep 29 16:52:11 stef-laptop NetworkManager: <info> Starting VPN service 'org.freedeskto
Sep 29 16:52:11 stef-laptop NetworkManager: <info> VPN service 'org.freedeskto
Sep 29 16:52:11 stef-laptop NetworkManager: <info> VPN service 'org.freedeskto
Sep 29 16:52:11 stef-laptop NetworkManager: <info> VPN plugin state changed: 1
Sep 29 16:52:11 stef-laptop NetworkManager: <info> VPN plugin state changed: 3
Sep 29 16:52:11 stef-laptop NetworkManager: <info> VPN connection 'Home' (Connect) reply received.
Sep 29 16:52:11 stef-laptop pppd[17650]: Plugin /usr/lib/
Sep 29 16:52:11 stef-laptop pppd[17650]: pppd 2.4.4 started by root, uid 0
Sep 29 16:52:11 stef-laptop pptp[17652]: nm-pptp-
Sep 29 16:52:11 stef-laptop pppd[17650]: Using interface ppp0
Sep 29 16:52:11 stef-laptop pppd[17650]: Connect: ppp0 <--> /dev/pts/3
Sep 29 16:52:11 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:11 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:11 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:12 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:12 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:12 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:12 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:12 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:12 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:13 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:13 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:13 stef-laptop pptp[17659]: nm-pptp-
Sep 29 16:52:13 stef-laptop pppd[17650]: LCP terminated by peer (M@^MM-
Sep 29 16:52:13 stef-laptop pptp[17659]: nm-pptp-
Stef Walter (stefw) wrote : | #16 |
BTW, connecting via the command line works, using the following instructions:
http://
The command being executed by network-
/usr/sbin/pppd pty /usr/sbin/pptp 10.10.10.10 --nolaunchpppd --logstring nm-pptp-
Stef Walter (stefw) wrote : | #17 |
After looking at the source code, I got this to work by adding a gconf setting. This setting cannot be properly set from the new network-
I added a string type gconf key called 'refuse-eap' under the gconf path of /system/
/system/
Obviously the '1' number there may be different for different users.
Christoph Burgdorf (christoph-burgdorf) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #18 |
This works for me, too!!! great!
Am Montag, den 29.09.2008, 22:35 +0000 schrieb Stef Walter:
> After looking at the source code, I got this to work by adding a gconf
> setting. This setting cannot be properly set from the new network-
> manager-pptp UI.
>
> I added a string type gconf key called 'refuse-eap' under the gconf path
> of /system/
>
> /system/
>
> Obviously the '1' number there may be different for different users.
>
> --
> Network Manager unable to connect to PPTP VPN
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “network-
>
> Bug description:
> Binary package hint: network-
>
> Package version: 0.7~~svn2008081
> uname -a: Linux jim-d620 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux
>
> I am testing the SVN version of network-manager 0.7. I am attempting to connect to my employer's Windows PPTP VPN. Each time I try, the connection fails, displaying a pop-up message that says: The VPN connection 'Connection Name' failed because the VPN service stopped unexpectedly.
>
> The relevant section of /var/log/syslog is:
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> Starting VPN service 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: nm_vpn_
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN plugin state changed: 3
> Aug 18 15:15:13 jim-d620 pppd[16602]: Plugin /usr/lib/
> Aug 18 15:15:13 jim-d620 pppd[16602]: pppd 2.4.4 started by root, uid 0
> Aug 18 15:15:13 jim-d620 pppd[16602]: Using interface ppp1
> Aug 18 15:15:13 jim-d620 pppd[16602]: Connect: ppp1 <--> /dev/pts/1
> Aug 18 15:15:13 jim-d620 pptp[16603]: nm-pptp-
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN connection 'Connection Name' (Connect) reply received.
> Aug 18 15:15:15 jim-d620 pptp[16607]: nm-pptp-
> Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
> Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
> Aug 18 15:15:16 jim-d620 pptp[16607]: nm-pptp-
f1anker (ianspigeon) wrote : Re: Network Manager unable to connect to PPTP VPN | #20 |
Thanks Stef, adding the gconf key manually did the trick!. On a separate note, "ignore-auto-dns" doesnt seem to be taking affect.
Billy Macdonald (billymacdonald) wrote : | #21 |
I would like to confirm that refuse-eap in the %gconf.xml worked for me as well. I had to restart the PC for it to take effect though as there appears to be some sort of caching of that file that caused my changes to not be recognized. This was verified by looking at the pppd string via ps. The options wouldn't change just by editing the file, I had to reboot too.
Billy Macdonald (billymacdonald) wrote : | #22 |
- Adds EAP and fixes other Advance settings behaviour Edit (5.6 KiB, text/plain)
Looking into this further it turns out that most of the options in the Advanced dialog do not set and unset properly. I've attached a patch that adds the EAP authentication option to the settings and also fixes the other options so they can be set and unset.
I'm not sure how to default to EAP off on a new connection, so it's not the best fix as that should usually default to off as it's for smart cards I believe.
Billy Macdonald (billymacdonald) wrote : | #23 |
Alexander Sack (asac) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #24 |
On Tue, Oct 14, 2008 at 12:44:09AM -0000, Billy Macdonald wrote:
> Upstream seems to have fixed most the options not saving properly.
> Attached is a patch to just add EAP as an authentication option to the
> Advance dialog (if I made the patch properly). I'm not sure how to
> directly submit this to upstream.
>
> ** Attachment added: "EAP.patch"
> http://
>
openvpn package was updated to latest a few days ago. is that fixed there?
- Alexander
Billy Macdonald (billymacdonald) wrote : | #25 |
On Wed, Oct 15, 2008 at 12:52 PM, Alexander Sack <email address hidden> wrote:
> On Tue, Oct 14, 2008 at 12:44:09AM -0000, Billy Macdonald wrote:
>> Upstream seems to have fixed most the options not saving properly.
>> Attached is a patch to just add EAP as an authentication option to the
>> Advance dialog (if I made the patch properly). I'm not sure how to
>> directly submit this to upstream.
>>
>> ** Attachment added: "EAP.patch"
>> http://
>>
>
> openvpn package was updated to latest a few days ago. is that fixed
> there?
>
> - Alexander
>
Yes, I just verified that I'm updated to the latest
network-
the connection to fail. The EAP.patch applies to
network-
the authentication section of the configuration so that it can be
disabled.
I can submit this to upstream, if I knew where that was, but I've been
unable to determine where this package comes from.
Billy
Alexander Sack (asac) wrote : | #26 |
On Thu, Oct 16, 2008 at 12:09:29AM -0000, Billy Macdonald wrote:
> On Wed, Oct 15, 2008 at 12:52 PM, Alexander Sack <email address hidden> wrote:
> > On Tue, Oct 14, 2008 at 12:44:09AM -0000, Billy Macdonald wrote:
> >> Upstream seems to have fixed most the options not saving properly.
> >> Attached is a patch to just add EAP as an authentication option to the
> >> Advance dialog (if I made the patch properly). I'm not sure how to
> >> directly submit this to upstream.
> >>
> >> ** Attachment added: "EAP.patch"
> >> http://
> >>
> >
> > openvpn package was updated to latest a few days ago. is that fixed
> > there?
> >
> > - Alexander
> >
>
> Yes, I just verified that I'm updated to the latest
> network-
> the connection to fail. The EAP.patch applies to
> network-
> the authentication section of the configuration so that it can be
> disabled.
>
> I can submit this to upstream, if I knew where that was, but I've been
> unable to determine where this package comes from.
So its not fixed in the build i uploaded today?
- Alexander
Billy Macdonald (billymacdonald) wrote : Re: Network Manager unable to connect to PPTP VPN | #27 |
Correct, still not fixed in the one that installed this afternoon via update manager.
pulling the current source and recompiling with the EAP.patch allows me to disable EAP auth so that I can connect.
Fernando Miguel (fernandomiguel) wrote : | #28 |
I'm experience a different thing now:
Before, I needed to enable MPPE, but now, not even turning that on will connect to a VPN PPTP server.
Tried again yesterday on two laptops (one ubuntu and one Kubuntu) will all updates and both failed.
Not even sure that this a bug on NM, but on PPTP, since that even with kvpn it failed to connect.
Fernando Miguel (fernandomiguel) wrote : | #29 |
$ apt-cache show network-manager
Package: network-manager
Priority: optional
Section: net
Installed-Size: 2044
Maintainer: Ubuntu Core Dev Team <email address hidden>
Original-
Architecture: amd64
Version: 0.7~~svn2008101
$ apt-cache show network-
Package: network-
Priority: optional
Section: universe/net
Installed-Size: 1052
Maintainer: Ubuntu MOTU Developers <email address hidden>
Original-
Architecture: amd64
Version: 0.7~~svn2008101
$ apt-cache show pptp-linux
Package: pptp-linux
Priority: optional
Section: net
Installed-Size: 192
Maintainer: Ubuntu Core Developers <email address hidden>
Original-
Architecture: amd64
Version: 1.7.2-1
Attaching a syslog of a failed attempt WITHOUT MPPE
Fernando Miguel (fernandomiguel) wrote : | #30 |
Tim (tim-barlotta) wrote : | #31 |
@BUGabundo
The problem you are seeing (in my opinion) is a problem with NetworkManager trying to get the password from the keyring. In this post someone mentions that clearing tha password gets you passed this "secrets" issue.
http://
However, if you read on in the thread there are still other issues...in particular someone opened a new bug about the CHAP format:
https:/
Fernando Miguel (fernandomiguel) wrote : | #32 |
Thanks for the sugestion
Not saving the password also seems to fail, on a quick test:
Oct 17 16:26:00 blubug NetworkManager: <info> Starting VPN service 'org.freedeskto
Oct 17 16:26:00 blubug NetworkManager: <info> VPN service 'org.freedeskto
Oct 17 16:26:00 blubug NetworkManager: <info> VPN service 'org.freedeskto
Oct 17 16:26:00 blubug NetworkManager: <info> VPN plugin state changed: 1
Oct 17 16:26:01 blubug NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: vpn-password-
Oct 17 16:26:01 blubug NetworkManager: <info> (eth0): writing resolv.conf to /sbin/resolvconf
Oct 17 16:26:01 blubug NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Oct 17 16:26:12 blubug NetworkManager: <info> VPN plugin state changed: 3
Oct 17 16:26:12 blubug NetworkManager: <info> VPN connection 'DEI MSVPN' (Connect) reply received.
Oct 17 16:26:12 blubug pppd[29888]: Plugin /usr/lib/
Oct 17 16:26:12 blubug kernel: [37163.021096] PPP generic driver version 2.4.2
Oct 17 16:26:12 blubug pppd[29888]: pppd 2.4.4 started by root, uid 0
Oct 17 16:26:12 blubug pptp[29903]: nm-pptp-
Oct 17 16:26:12 blubug pppd[29888]: Using interface ppp0
Oct 17 16:26:12 blubug pppd[29888]: Connect: ppp0 <--> /dev/pts/1
Oct 17 16:26:12 blubug pptp[29916]: nm-pptp-
Oct 17 16:26:12 blubug pptp[29916]: nm-pptp-
Oct 17 16:26:12 blubug pptp[29916]: nm-pptp-
Oct 17 16:26:13 blubug pptp[29916]: nm-pptp-
Oct 17 16:26:13 blubug pptp[29916]: nm-pptp-
Oct 17 16:26:13 blubug pptp[29916]: nm-pptp-
Oct 17 16:26:23 blubug pppd[29888]: MS-CHAP authentication failed:
Oct 17 16:26:23 blubug pppd[29888]: CHAP authentication failed
Oct 17 16:26:23 blubug pppd[29888]: Connection terminated.
Oct 17 16:26:23 blubug NetworkManager: <info> VPN plugin failed: 1
Oct 17 16:26:23 blubug pptp[29916]: nm-pptp-
Oct 17 16:26:23 blubug pptp[29916]: nm-pptp-
Oct 17 16:26:23 blubug pptp[29916]: nm-pptp-
Oct 17 16:26:23 blubug pptp[29916]: nm-pptp-
houstonbofh (leesharp) wrote : | #33 |
- Logs.tar.gz Edit (2.7 KiB, application/x-tar)
Another "Me Too..."
This is connecting to m0n0wall VPN's. They have worked from Dapper on with default settings, and are very stable. With Intrepid, no joy. (This is after deleting the password from the keyring)
Enclosed are the syslogs from a Intrepid box failing, and logs from m0n0wall with a failed Intrepid, and a successful Gutsy.
Alexander Sack (asac) wrote : | #34 |
I made a test package out of the proposed patch from https:/
Its currently building in the NM team PPA: https:/
Thanks for testing.
Changed in pptp-linux: | |
status: | New → Invalid |
Changed in network-manager-pptp: | |
milestone: | none → intrepid-updates |
importance: | Undecided → High |
Andrey Beljakov (andvalb) wrote : | #35 |
I have tested given on "https:/
In configuration options selected only MSCHAPv2, MPPE (statefull or stateless with no sense) PPP headers compression and echo.
if only EAP selected network manager use client host name as user name and fail authentification with wrong password message on server side (I can add this user (with host name login) on server side). if with EAP i select other options (PAP CHAP ... etc) authentification success but connection continue using client host name as user name and this connection without MPPE.
Sorry for bad English.
In Russian:
Я попробовал предоставленное на "https:/
Если же указать использование EAP, то в качестве имени пользователя нетворк менеджер использует имя хоста (пользователь с таким логином (с именем хоста) был мною специально добавлен на сервер) но если кроме EAP ничего не выбрано то все равно получаем ошибку аутентификации - но уже по причине неверного пароля - если же выбрать вместе с EAP другие методы, то аутентификация проходит успешно но все равно продолжает использовать имя хоста в качестве имени кользователя (что собственно и было до патча отключения EAP).
Ну и естественно в брелке пароли не сохраняются. Ошибка уже старая и когда ее поправят неизвестно.
Да и собственно хоть в логах клиента и появляется сообщение о том что 128битное сжатие MPPE включено на стороне сервера в состоянии соединения процент сжатия все равно 0 - не работает?
Fernando Miguel (fernandomiguel) wrote : | #36 |
On Monday 27 October 2008 18:24:13 andvalb wrote:
> I have tested given on "https:/
> In configuration options selected only MSCHAPv2, MPPE (statefull or stateless with no sense) PPP headers compression and echo.
Lastest updates from LP~NM and PPTP fails with and without MPPE
--
BUGabundo :o)
Fernando Miguel (fernandomiguel) wrote : | #37 |
This is what I get when I connect to a PPTP VPN:
*** glibc detected *** /usr/lib/
======= Backtrace: =========
/lib/libc.
/lib/libc.
/usr/lib/
/lib/libc.
/usr/lib/
======= Memory map: ========
00400000-00407000 r-xp 00000000 08:01 326914 /usr/lib/
00606000-00607000 r--p 00006000 08:01 326914 /usr/lib/
00607000-00608000 rw-p 00007000 08:01 326914 /usr/lib/
0243f000-02505000 rw-p 0243f000 00:00 0 [heap]
7f4e7c000000-
7f4e7c021000-
7f4e820c4000-
7f4e820da000-
7f4e822da000-
7f4e822db000-
7f4e822dc000-
7f4e822eb000-
7f4e824ea000-
7f4e824eb000-
7f4e824ec000-
7f4e824f2000-
7f4e826f1000-
7f4e826f2000-
7f4e826f3000-
7f4e826f8000-
7f4e828f8000-
7f4e828f9000-
7f4e8294e000-
7f4e82b4e000-
7f4e82b53000-
7f4e82b5f000-
7f4e82b66000-
Alexander Sack (asac) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #38 |
On Mon, Oct 27, 2008 at 10:17:05PM -0000, BUGabundo wrote:
> This is what I get when I connect to a PPTP VPN:
please install the -dbgsym packages to get a symbolized backtrace.
- Alexander
Fernando Miguel (fernandomiguel) wrote : Re: Network Manager unable to connect to PPTP VPN | #39 |
I would like to do that asac, but following https:/
$ sudo apt-get install network-
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
network-
E: Broken packages
Alexander Sack (asac) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #40 |
On Wed, Oct 29, 2008 at 02:14:21PM -0000, BUGabundo wrote:
> I would like to do that asac, but following
> https:/
unfortunately, there are no -dbgsym packages for versions installed
from PPA. you need to downgrade to the "official" intrepid version to
make this work.
Sorry for the confusion.
- Alexander
Marius Gedminas (mgedmin) wrote : Re: Network Manager unable to connect to PPTP VPN | #41 |
BUGabundo: see the patch I attached to https:/
Alexander Sack (asac) wrote : | #42 |
I found a bug in how pptp assembles the name to authenticate from domain+username and uploaded a proposed fix for network-
Please test. At least BUGabundo's issues should be fixed there.
Changed in network-manager-pptp: | |
status: | Confirmed → Triaged |
Fernando Miguel (fernandomiguel) wrote : | #43 |
Just to let everyone know that after some debug and chat on IRC asac got it fixed for me!
Now to see this go into Repo updates
--
BUGabundo :o)
(``-_-´´) http://
Linux user #443786 GPG key 1024D/A1784EBB
My new micro-blog @ http://
chadeldridge (chadeldridge) wrote : | #44 |
Any news on when this will make the repos?
/
Alexander Sack (asac) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #45 |
On Fri, Oct 31, 2008 at 03:19:01AM -0000, chadeldridge wrote:
> Any news on when this will make the repos?
> /
>
The more feedback we get on the proposed package the earlier we can
pursue this.
- Alexander
Andris Sprūds (aspruds) wrote : Re: Network Manager unable to connect to PPTP VPN | #46 |
Today I installed the latest NetworkManager from "deb http://
Alexander Sack (asac) wrote : | #47 |
John Brown, thanks for the info. Please don't add new bugs here. Just say: "the packages fix this, but I found a new issue: bug XXXX" (after you opened a new bug for other individual issues. Thanks!
houstonbofh (leesharp) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #48 |
John Brown Jr. wrote:
> Today I installed the latest NetworkManager from "deb
> http://
> now finally connect to my VPN network! However, if I try to save the
> password in the keyring, I still get a VPN error about 'shared secrets'.
> And I am also having some DNS issues while connected to my VPN, although
> these might as well be unrelated to NetworkManager.
Just post this to the keyring bug as well so they know it still is not
fixed... https:/
this last week.
mklebel (mklebel) wrote : Re: Network Manager unable to connect to PPTP VPN | #49 |
/var/log/syslog:
Nov 1 12:23:42 mitchell-laptop NetworkManager: <info> Starting VPN service 'org.freedeskto
Nov 1 12:23:42 mitchell-laptop NetworkManager: <info> VPN service 'org.freedeskto
Nov 1 12:23:42 mitchell-laptop NetworkManager: <info> VPN service 'org.freedeskto
Nov 1 12:23:51 mitchell-laptop NetworkManager: <info> VPN plugin state changed: 3
Nov 1 12:23:51 mitchell-laptop NetworkManager: <info> VPN connection 'BrokerBin' (Connect) reply received.
Nov 1 12:23:51 mitchell-laptop pppd[7213]: Plugin /usr/lib/
Nov 1 12:23:51 mitchell-laptop pppd[7213]: pppd 2.4.4 started by root, uid 0
Nov 1 12:23:51 mitchell-laptop pptp[7215]: nm-pptp-
Nov 1 12:23:51 mitchell-laptop pppd[7213]: Using interface ppp0
Nov 1 12:23:51 mitchell-laptop pppd[7213]: Connect: ppp0 <--> /dev/pts/1
Nov 1 12:23:51 mitchell-laptop pptp[7222]: nm-pptp-
Nov 1 12:23:51 mitchell-laptop pptp[7222]: nm-pptp-
Nov 1 12:23:51 mitchell-laptop pptp[7222]: nm-pptp-
Nov 1 12:23:52 mitchell-laptop pptp[7222]: nm-pptp-
Nov 1 12:23:52 mitchell-laptop pptp[7222]: nm-pptp-
Nov 1 12:23:52 mitchell-laptop pptp[7222]: nm-pptp-
Nov 1 12:23:52 mitchell-laptop pppd[7213]: MS-CHAP authentication failed: I don't like you. Go 'way.
Nov 1 12:23:52 mitchell-laptop pppd[7213]: CHAP authentication failed
Nov 1 12:23:52 mitchell-laptop NetworkManager: <info> VPN plugin failed: 1
Nov 1 12:23:52 mitchell-laptop pppd[7213]: Connection terminated.
Nov 1 12:23:52 mitchell-laptop NetworkManager: <info> VPN plugin failed: 1
Nov 1 12:23:52 mitchell-laptop pptp[7215]: nm-pptp-
Nov 1 12:23:52 mitchell-laptop pptp[7215]: nm-pptp-
Nov 1 12:23:52 mitchell-laptop pptp[7222]: nm-pptp-
I have tried all the suggestions listed here. Still no glory. I am running Intrepid, downloaded it last night.
Nov 1 12:23:52 mitchell-laptop pptp[7222]: nm-pptp-
Nov 1 12:23:52 mitchell-laptop pptp[7222]: nm-pptp-
Nov 1 12:23:52 mitchell-laptop pppd[7...
Alexander Sack (asac) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #50 |
On Sat, Nov 01, 2008 at 05:30:49PM -0000, mklebel wrote:
> I have tried all the suggestions listed here. Still no glory. I am
> running Intrepid, downloaded it last night.
Did you also test the latest packages in the ~network-manager PPA
(mentioned above)?
- Alexander
Tuomo Lesonen (tuomo-lesonen) wrote : Re: Network Manager unable to connect to PPTP VPN | #51 |
After updating from Hardy to Intrepid, I was no longer able to connect to a Windows 2000 server using PPTP (worked out-of-box with 8.04). After installing the latest packages (mentioned above), still had no luck. But then I checked "Use Point-to-Point encryption (MPPE)" under "Advanced" button, and I was able to connect.
-Tuomo
houstonbofh (leesharp) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #52 |
Tuomo Lesonen wrote:
> After updating from Hardy to Intrepid, I was no longer able to connect
> to a Windows 2000 server using PPTP (worked out-of-box with 8.04). After
> installing the latest packages (mentioned above), still had no luck. But
> then I checked "Use Point-to-Point encryption (MPPE)" under "Advanced"
> button, and I was able to connect.
Thank you! I tried that before with no luck, but with the current repo
versions, a m0n0wall VPN now works again. WooHoo!
chadeldridge (chadeldridge) wrote : Re: Network Manager unable to connect to PPTP VPN | #53 |
After doing the refuse-eap and upgrading to the module above I am also working. I assume that the final fix will include the refuse-eap as a check option in the pptp config?
mklebel (mklebel) wrote : | #54 |
Works now. upgrading to the PPA version fixed it.
Another issue,
but I'm not sure if this is a bug or I'm uneducated with network-manager but it rewrites my /etc/resolv.conf to use the remote VPN gateway instead of my local gateway. I tail syslog and it sets ppp0 as default for routing and DNS, I want it to go all through eth1.
Changed in network-manager-pptp: | |
assignee: | nobody → asac |
assignee: | nobody → asac |
Bill Loucks (biloucks) wrote : | #55 |
This affects me seriously. The workaround of manually adding "refuse-eap" to the file ~/.gconf/
mklebel (mklebel) wrote : | #56 |
Ok, so I finally figured this out. If you don't set any routes, network-manager will assume all traffic gets routed through the VPN. I just put in a few entries, and it routed it through eth1, which is exactly what I wanted. Works great now.
Thanks everyone for all your help!
Sami Nybacka (sapeny) wrote : | #57 |
Many thanks! After installing PPA version (network-
UI is still very much buggy, reliable configuration must be done/checked with gconf-editor:
- config option for refuse-EAP still missing, must be set with gconf-editor
- after 1) selecting point-to-point encryption (MPPE) and Security: 128 bit, 2) editing vpn configuration again later, MPPE is now shown as unchecked, with Security: All Available (Default) => only gconf-editor shows the real state
- after setting some ipv4 addresses they can't be removed without gconf-editor (they are back when editing vpn config again)
IMO: route setup would require some examples or explaining. It was surprisingly confusing to set routes so that only addressses behind vpn'ed network were accessed via vpn gateway.
Fernando Miguel (fernandomiguel) wrote : | #58 |
Fernando Miguel (fernandomiguel) wrote : | #59 |
Jeremy Cantrell (jmcantrell) wrote : | #60 |
The updates from the PPA fixed the issues that I was having. I can even save the password to the keyring. I did have to alter some of the settings in gconf myself, as the GUI for vpn appears to be broken for altering some advanced settings.
houstonbofh (leesharp) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #61 |
BUGabundo wrote:
> Fully updated at this time, NM from PPA, no passwords on keyring, new
> VPN configurarion, and I fail to connect to all my 3 test case servers
Have you tried checking "Use Point-to-Point encryption (MPPE)" under the
"Advanced" button? It fixed an issue for me. Seems that it used to be
default.
Alexander Sack (asac) wrote : | #62 |
On Thu, Nov 06, 2008 at 07:11:40PM -0000, jmcantrell wrote:
> The updates from the PPA fixed the issues that I was having. I can even
> save the password to the keyring. I did have to alter some of the
> settings in gconf myself, as the GUI for vpn appears to be broken for
> altering some advanced settings.
>
Could you please evaluate which advanced settings are broken and open
new bugs for them?
Thanks,
- Alexander
Jeremy Cantrell (jmcantrell) wrote : Re: Network Manager unable to connect to PPTP VPN | #63 |
the things i was describing appear to be described, for the most part, in this bug:
https:/
In addition, the EAP option is not available in the list of authentication methods.
Fernando Miguel (fernandomiguel) wrote : | #64 |
On Thursday 06 November 2008 23:02:01 houstonbofh wrote:
> Have you tried checking "Use Point-to-Point encryption (MPPE)"
Forgot to mention that.
Yes it was enabled.
--
BUGabundo :o)
(``-_-´´) http://
Marius Gedminas (mgedmin) wrote : | #65 |
I enabled MPPE *and* selected 128-bit encryption, and after that my VPN started working.
Bill Loucks (biloucks) wrote : | #66 |
This affects me seriously. The workaround of manually adding "refuse-eap" to the file ~/.gconf/
If fixing Version 0.7 in Intrepid is going to take more than a few weeks, can someone tell me if Version 0.6.5 could be compiled in Intrepid, and a binary package made available?
Steve Romanow (slestak989) wrote : RE: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #67 |
Could this affect ppl differently based on whether they dist-upgraded or fresh installed?
Marek Grzenkowicz (chopeen) wrote : Re: Network Manager unable to connect to PPTP VPN | #68 |
If you can see no /system/
dmandell (dmandell) wrote : | #69 |
I'd like to reiterate what William said, 0.7 is a major regression in terms of features and in terms of the number of bugs introduced.
William Loucks and those who might prefer the old version:
I decided it was better to just use the Hardy version of network manager... if you're using pptp you need to install the following packages from the Hardy repository:
libnm-glib0
libnm-util0
network-manager
network-
network-
These packages work fine with Intrepid, and the former route functionality (which I also used) has returned.
James House (poenitentia-tranquilitas) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #70 |
Will installing those packages overwrite the 8.10 packages automatically, or
should the Intrepid packages be removed first? What about when updates come
out that fix this issue? Do we need to watch for them, or will they
automatically be installed with apt-get?
On Mon, Nov 10, 2008 at 1:17 PM, dmandell <email address hidden> wrote:
> I'd like to reiterate what William said, 0.7 is a major regression in
> terms of features and in terms of the number of bugs introduced.
>
> William Loucks and those who might prefer the old version:
>
> I decided it was better to just use the Hardy version of network
> manager... if you're using pptp you need to install the following
> packages from the Hardy repository:
>
> libnm-glib0
> libnm-util0
> network-manager
> network-
> network-
>
> These packages work fine with Intrepid, and the former route
> functionality (which I also used) has returned.
>
> --
> Network Manager unable to connect to PPTP VPN
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "network-
> Status in "pptp-linux" source package in Ubuntu: Invalid
> Status in network-
> Status in pptp-linux in Ubuntu Intrepid: Invalid
>
> Bug description:
> Binary package hint: network-
>
> Package version: 0.7~~svn2008081
> uname -a: Linux jim-d620 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC
> 2008 i686 GNU/Linux
>
> I am testing the SVN version of network-manager 0.7. I am attempting to
> connect to my employer's Windows PPTP VPN. Each time I try, the connection
> fails, displaying a pop-up message that says: The VPN connection 'Connection
> Name' failed because the VPN service stopped unexpectedly.
>
> The relevant section of /var/log/syslog is:
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> Starting VPN service
> 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service
> 'org.freedeskto
> (org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service
> 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN service
> 'org.freedeskto
> Aug 18 15:15:13 jim-d620 NetworkManager: nm_vpn_
> assertion `nm_vpn_
> NM_VPN_
> Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN plugin state changed:
> 3
> Aug 18 15:15:13 jim-d620 pppd[16602]: Plugin
> /usr/lib/
> Aug 18 15:15:13 jim-d620 pppd[16602]: pppd 2.4.4 started by root, uid 0
> Aug 18 15:15:13 jim-d620 pppd[16602]: Using interface ppp1
> Aug 18 15:15:13 jim-d620 pppd[16602]: Connect: ppp1 <--> /dev/pts/1
> Aug 18 15:15:13 jim-d620 pptp[16603]: nm-pptp-
> log[main:
> Aug 18 15:15:13 jim-d620 Netwo...
Matthew (matthew-isaacs) wrote : | #71 |
Simply adding the hardy repositories is probably not the best idea. You can
pin the version, but future upgrades MAY be problematic; at least I've had
trouble in the past with this. Additionally library dependencies are
different.
A better way is to grab the 0.6.x source package from hardy and rebuild it
for Intrepid. It could be hosted in someone's PPA on launchpad. I may do
this once I get some time.
Additionally, there appear to be workarounds by editing the gconf database
to configure the settings for the connection and not using the NM applet
GUI.
This has recently cause us some problems at my place of employment, so I may
have some time to generate the packages and/or document the workaround in
more detail later this week (if someone doesn't beat me to it).
The only regression I'm aware of is in PPTP VPN support. 0.7 adds many
features otherwise. Additionally, PPTP support in NM is, and AFAIK always
has been, a universe component and therefore does not quite have the
support/review that components in main do.
On Mon, Nov 10, 2008 at 1:37 PM, James House <
<email address hidden>> wrote:
> Will installing those packages overwrite the 8.10 packages automatically,
> or
> should the Intrepid packages be removed first? What about when updates come
> out that fix this issue? Do we need to watch for them, or will they
> automatically be installed with apt-get?
>
> On Mon, Nov 10, 2008 at 1:17 PM, dmandell <email address hidden> wrote:
>
> > I'd like to reiterate what William said, 0.7 is a major regression in
> > terms of features and in terms of the number of bugs introduced.
> >
> > William Loucks and those who might prefer the old version:
> >
> > I decided it was better to just use the Hardy version of network
> > manager... if you're using pptp you need to install the following
> > packages from the Hardy repository:
> >
> > libnm-glib0
> > libnm-util0
> > network-manager
> > network-
> > network-
> >
> > These packages work fine with Intrepid, and the former route
> > functionality (which I also used) has returned.
> >
> > --
> > Network Manager unable to connect to PPTP VPN
> > https:/
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in "network-
> > Status in "pptp-linux" source package in Ubuntu: Invalid
> > Status in network-
> > Status in pptp-linux in Ubuntu Intrepid: Invalid
> >
> > Bug description:
> > Binary package hint: network-
> >
> > Package version: 0.7~~svn2008081
> > uname -a: Linux jim-d620 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC
> > 2008 i686 GNU/Linux
> >
> > I am testing the SVN version of network-manager 0.7. I am attempting to
> > connect to my employer's Windows PPTP VPN. Each time I try, the
> connection
> > fails, displaying a pop-up message that says: The VPN connection
> 'Connection
> > Name' failed because the VPN service stopped unexpectedly.
> >
> > The relevant section of /var/log/syslog is:
> > Aug 18 15:15:13 jim-d620 NetworkManager: <i...
bim (mng-kingston) wrote : Re: Network Manager unable to connect to PPTP VPN | #72 |
I wonder if there is a way someone could be asked to give us beginners some step-by-step instructions how to get the network manager from Hardy and install it in Intrepid.
Alberto (apedraza) wrote : | #73 |
There is no need to change to 6.5 from 0.7. 0.7 is better in many ways. If you are still having problems with pptp. Just install KVpnc. It works very well.
Jasey (jason-rivers) wrote : | #74 |
I've already downgraded the entirity of Network-manager back to 0.6.6 - VPN to me, means I can work from home, I don't have to drive to the office when there's a problem at 3AM, network manager 0.7 (all components) has been the biggest let down for me in Ubuntu in 3 years, and has almost driven me away. just look at how many bugs are associated with it, and how many were even looked at before release, IMHO it should have stayed with 0.6.6 until 0.7 was more stable, it's really not like Ubuntu to have SVN builds in their release - though I guess last time it was the Firefox 3 beta issue. now where near as bad as not letting people access VPN's to their place of work, or even set a static IP Address and have the machine actually remember what it is after it's been reset.
0.7 might be better in many ways, but IMHO more has been broken than has been fixed.i'll stick with 0.6.6 until my VM works as it should, I will also never install a KDE app to get around a bug that has been created in a gnome application, I will take the regression on the gnome application to the point the bug is not there. even Gentoo doesn't have 0.7 and they mark things as stable when they compile!
James P Michels III (james-p-michels) wrote : | #75 |
@Alberto
Telling people that 0.7 is "better in many ways" is not very compelling considering that application is missing critical functionality. 0.7 is not ready for a release environment.
There is no "almost" about it for me. I am using Vista x64 for the next few months until all of this get sorted out. I am sorry to be so negative. I really appreciate the work you guys are doing, but this really cuts into Ubuntu's credibility.
houstonbofh (leesharp) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #76 |
Kamujin wrote:
> @Alberto
>
> Telling people that 0.7 is "better in many ways" is not very compelling
> considering that application is missing critical functionality. 0.7 is
> not ready for a release environment.
More troubling to me is how this is happening more and more often...
Major bugs that go thought the entire beta, AND the entire life cycle
with no fix!
Lets start with QEMU on Gutsy.
https:/
Found to be BOCH BIOS
https:/
Fixed in Intrepid... Gutsy is still broken.
Hard Drive cycles?
https:/
Broken since Gutsy, and still having issues... Only Bug 1 is longer
running.
It seems to me that regressions are coming faster with every release.
Every other bug I have subscribed to has bee fixed in the lifecycle of
that release. But we are getting more and more that are only fixed with
an upgrade. (Like the Intrepid Kernel locks) How do we bug this problem?
Jeremy Cantrell (jmcantrell) wrote : Re: Network Manager unable to connect to PPTP VPN | #77 |
Folks, I think we all need to take a deep breath and come to some painful realizations.
If you're looking for the most rock-solid Ubuntu experience, then you should stick with the LTS releases. The last one was Hardy Heron. Using the non-LTS releases, you have to understand that they're going to be a bit more bleeding edge. At the very least, you should wait to verify that packages which are critical to you are not broken before upgrading.
I've personally been using Ubuntu since Warty Warthog (4.10) for both my desktop environment and several servers. I've used every version since. My experience has been that Ubuntu has done nothing but improve with every version. Sure, there are some regressions, but the overall trend is upward.
Bottom line: If you want the latest and greatest, you should be prepared for some headaches.
James P Michels III (james-p-michels) wrote : | #78 |
Please, this isn't a beta. This is released software with a large number of regressions. If these were new "bleeding edge" features, you might have a point.
houstonbofh (leesharp) wrote : [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #79 |
jmcantrell wrote:
> If you're looking for the most rock-solid Ubuntu experience, then you
> should stick with the LTS releases. The last one was Hardy Heron. Using
> the non-LTS releases, you have to understand that they're going to be a
> bit more bleeding edge. At the very least, you should wait to verify
> that packages which are critical to you are not broken before upgrading.
The "fix" for the Hardy Heron kernel freeze is to upgrade to the
Intrepid kernel, or regress to Gutsy. Also the broken mjpeg streaming
in Firefox that will not be fixed until 3.05. My entire enterprise is
frozen a Gutsy right now as it is stable, and Hardy is not. And since
the fixes to the two major bugs for me are version changes, they can not
happen within Hardy.
Which sidesteps the point of how these bugs are surviving through
extensive betas, and 6 months of production. There is a very good
chance that the "fix" for this bug will be regression to Intrepid
network manager, or the next version that can't ship in Intrepid. My
point is that this is getting far too common. I too have been around
since the Badger, and Gutsy BOCH BIOS was the first time I saw this. But
I have been seeing more lately.
And this is way off topic. What is on topic is will there be a fix, a
regression, or a backport type "fix?" And how can we better QC the beta
so that the regression can happen before the freeze?
Alberto (apedraza) wrote : Re: Network Manager unable to connect to PPTP VPN | #80 |
I have to admit that 0.7 has many bugs that should have been addressed before release. I do use 0.7 since hardy because I depend on my sprint card to connect and 0.7 handles it very well. As nm 0.7 pptp is kind of broken, I can see how people are upset. I myself, am surprised that pptp still has bugs. Maybe the developers are underestimating the amount of people that use pptp. I don't know.
There are two ways to make pptp work today:
A. Install kvpnc, configure and you are good to go. I used this myself when I was testing 0.7 in Hardy and pptp was non-existant. It works very solidly.
or
B. Force pptp to work in nm 0.7 via hacks & teaks via the gconfig editor.
here are workarounds for these problems.
1. You need to add a refuse-eap key in gconfig and set it to yes. If you don't do this, the pptp client will send the host-name instead of your user name to the server. This will cause your connection to be rejected.
2. If you are using a domain name to log in, don't put it in the domain box. Instead, put your domain name and your user-name together in the name field. domain\login
3. This is my gconf setup:
gateway xxx.xxx.xxx.xxx -- put in the ip of your server here
lcp-echo-failure 5
lcp-echo-interval 30
mppe-stateful yes
no-vj-comp yes
refuse-chap yes
refuse-eap yes -- new key you must put in.
refuse-mschap yes
refuse-pap yes
require-mppe yes
require-mppe-128 yes
service-type org.freedesktop
user domain\userlogin -- you have to do it like this otherwise it won't work. on the gui, leave the domain name blank.
And finally, the keys must be added in system\
The refuse-eap key trick was found by somebody else so I don't take credit for it.
Hope this helps....
lordfoul (lordfoul) wrote : | #81 |
As Alberto says just use kvpnc until this is really fixed it works flawlessly.
gergul (gokhan-ergul) wrote : | #82 |
Just a small reminder for those using the gconf hack: every time you use the NM VPN config gui and save changes, you'll need to re-add refuse-eap key in gconf again, since NM GUI will wipe out existing keys.
As for the regressions in Intrepid, I should say that the sheer number of them and the fact that most regressions are around basic stuff that should just work is, to say the least, alarming. I've been using ubuntu since 6.04, and I've never seen a dist upgrade break so many things. The only reason I've upgraded was to get suspend/resume working on my MacBook Pro after hearing (admittedly) rumors that *.27 kernel was much better at it, I ended up spending countless hours reading launchpad & working around things just to get it up and running. And now, suspend/resume still doesn't work, and my session is not restored after boot/login due to gnome session restore regression (https:/
Alexander Sack (asac) wrote : | #83 |
we use this bug to track the bogus NT-Domain encoding. The lack of essential ppp options part is tracked in bug 268667.
If you have other issues, we need a new bug.
Alexander Sack (asac) wrote : | #84 |
this means: if it still doesnt work for you with the current network-manager PPA packages, we need a new/different bug.
Alexander Sack (asac) wrote : | #85 |
initiating intrepid sru.
description: | updated |
Changed in network-manager-pptp: | |
status: | Triaged → In Progress |
Alexander Sack (asac) wrote : | #86 |
uploading network-
uploading network-
Launchpad Janitor (janitor) wrote : | #87 |
This bug was fixed in the package network-
---------------
network-
* LP: #259168 Network Manager unable to connect to PPTP VPN (bad NT-Domain
escaping); we improve ppp domain in username encoding
- add debian/
* LP: #268667 MASTER - not all required ppp options get set on command line
which makes ppp use bad values from /etc/ppp/options*; we explicitly set
good values for: nodefaultroute, lcp-echo-failure and lcp-echo-interval
- add debian/
* LP: #292681 crash when running auth-dialog and secret in keyring;
we use the proper memory functions in this patch (dupe-of LP: #284212
VPN connection fails: "unable to find valid VPN secrets")
- add debian/
* LP: #290468 VPN fails, "/usr/bin/
obsolete conffiles in .preinst now
- add debian/
-- Alexander Sack <email address hidden> Thu, 30 Oct 2008 00:22:51 +0100
Changed in network-manager-pptp: | |
status: | Triaged → Fix Released |
Changed in network-manager-pptp: | |
milestone: | intrepid-updates → none |
Martin Pitt (pitti) wrote : | #88 |
Accepted into intrepid-proposed, please test and give feedback here. Please see https:/
Changed in network-manager-pptp: | |
milestone: | intrepid-updates → none |
status: | In Progress → Fix Committed |
neilyalowitz (neilyalowitz) wrote : | #89 |
Any fix for this?
Many users have experienced this bug, Google around and see the numerous forums. VPN connections were working fine until I upgraded from Ubuntu 8.04 to 8.10.
VERY disappointing to find bugs for important services after an upgrade.
I have the exact same output in /var/log/syslog as in this bug description:
Aug 18 15:15:18 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:18 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:18 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:19 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:19 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:19 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:19 jim-d620 pppd[16602]: LCP terminated by peer (wM-(?"
Aug 18 15:15:19 jim-d620 pptp[16607]: nm-pptp-
Aug 18 15:15:22 jim-d620 pppd[16602]: Connection terminated.
Aug 18 15:15:22 jim-d620 pppd[16602]: Modem hangup
houstonbofh (leesharp) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN (bad NT-Domain escaping) | #90 |
1longtime wrote:
> Any fix for this?
>
> Many users have experienced this bug, Google around and see the numerous
> forums. VPN connections were working fine until I upgraded from Ubuntu
> 8.04 to 8.10.
>
> VERY disappointing to find bugs for important services after an upgrade.
While I agree, we do have a fix in "proposed" and it could use a lot of
testing. Grab it and post back. (Under Software Sources, enable
"proposed" and find the update. Update only it {unless you want to test
everything} and disable proposed to make normal updates easier.)
neilyalowitz (neilyalowitz) wrote : | #91 |
Excuse me, I just read the comments RE: package fix, but it does not fix the problem.. As a separate forum suggestion, I previously added to my sources.list (but this did not fix the bug):
deb http://
...and after reading the above comments, I also added the intrepid-proposed to sources.list (but I did not see network-manager updated, I assume the above network-manager source entry already did that?).
THIS BUG STILL EXISTS. What can I provide to help fix this? This VPN connection worked for half a year until I updated to 8.04 to 8.10. It should be marked with high importance, I suspect that many users are affected.
Martin Pitt (pitti) wrote : | #92 |
Sorry, the update isn't built yet, our buildds are clogged. I bumped the priority of this now, it should be available on archive.ubuntu.com in about 3 hours, and on the mirrors some hours later.
Bill Loucks (biloucks) wrote : | #93 |
We have been asked that if we are having troubles other than "Bad NT-Domain escaping", to create another bug. I am fully willing to do that, because I do indeed have other problems, but I see there are 4 duplicates of THIS bug, plus at least half a dozen other bugs for network-
network-
The Dialog window labeled "Edit VPN Connection", a multi-tabbed dialog:
Tab labeled "Connection"
Free-form text entry labeled "Connection Name"
Checkbox: "Requires existing network connection"
Drop-down list with only one entry: "Windows VPN (PPTP)"
Free-form text entry labeled "Gateway"
Tab labeled "Authentication"
Checkbox: "Authenticate Peer"
Checkbox: "Refuse EAP"
Checkbox: "Refuse CHAP"
Checkbox: "Refuse MS CHAP"
Tab labeled "Compression & Encryption"
Group labeled "Compression"
Checkbox: "Require MPPC Compression"
Checkbox: "Allow Deflate compression"
Checkbox: "Allow BSD Compression"
Group labeled "Encryption"
Checkbox: "Require MPPE encryption"
Checkbox: "Require 128 bit MPPE encryption"
Checkbox: "Enable stateful MPPE"
Tab labeled "PPP Options"
Free-form text entry labeled "Custom PPP options"
Group labeled "IP Options"
Checkbox: "Use Peer DNS"
Checkbox: "Require explicit IP Addr"
Checkbox: "Exclusive device access (UUCP-style lock)"
Checkbox: "Debug output"
Group labeled "Packet Parameters"
Drop-down list with up/down arrows AND free-form text entry labeled "MTU"
Drop-down list with up/down arrows AND free-form text entry labeled "MRU"
Group labeled "Delays and TImeouts"
Drop-down list with up/down arrows AND free-form text entry labeled "connect-delay"
Drop-down list with up/down arrows AND free-form text entry labeled "lcp-echo-failure"
Drop-down list with up/down arrows AND free-form text entry labeled "lcp-echo-interval"
Tab labeled "Routing"
Checkbox: "Peer DNS through tunnel"
Checkbox: "Only use VPN connections for these addresses"
Free-form text entry below which is the text, "example: 172.16.0.0/16 10.11.12.0/24"
Alexander Sack (asac) wrote : | #94 |
1longtime, your issue is most likely bug 268667 ... the proposed fix should be available in intrepid-proposed. please test that package and report bug (at best in the bug above). Also double check that you have MPPE encryption enabled.
Jeremy Cantrell (jmcantrell) wrote : | #95 |
I just updated from proposed. I'm not sure what I'm supposed to be seeing. The EAP option is still missing from the list, as well.
Bill Loucks (biloucks) wrote : | #96 |
Mr. Sack,
You wrote, "Longtime, your issue is most likely bug 268667". I mean no disrespect, but when I point my browser at https:/
Let me state my issue as clearly as I can: (My issue is both eap and custom routing, but I'll just state the most critical of the two):
network-
Nov 21 08:35:10 hostname pppd[5949]: EAP: peer reports authentication failure
Jeremy Cantrell (jmcantrell) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN (bad NT-Domain escaping) | #97 |
I have a patch for the EAP interface bug. I'm trying to figure out the MPPE
interface bug, as well. I'll post here when I'm done.
--
:wq
On Fri, Nov 21, 2008 at 10:40, William Loucks <email address hidden> wrote:
> Mr. Sack,
>
> You wrote, "Longtime, your issue is most likely bug 268667". I mean no
> disrespect, but when I point my browser at
> https:/
> and search within the page for the 3-character string, "eap", THE SEARCH
> FAILS. So I ask: How can you possibly in your wildest imagination
> suggest that bug 268667 is my issue?
>
> Let me state my issue as clearly as I can: (My issue is both eap and
> custom routing, but I'll just state the most critical of the two):
>
> network-
> set, which results in eap being enabled, which results in the following
> in /var/log/syslog :
>
> Nov 21 08:35:10 hostname pppd[5949]: EAP: peer reports authentication
> failure
>
> --
> Network Manager unable to connect to PPTP VPN (bad NT-Domain escaping)
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Jeremy Cantrell (jmcantrell) wrote : | #98 |
- Fix for EAP interface bug Edit (1.6 KiB, text/plain)
This patch fixes the EAP interface bug for me. I'm still looking at the MPPE interface bug. I would add the package itself to my PPA, but I'm not sure how. If anyone can help me with that, I'd be glad to upload it.
Jeremy Cantrell (jmcantrell) wrote : | #99 |
I should also mention that this patch was done against the latest package from proposed.
Jeremy Cantrell (jmcantrell) wrote : | #100 |
- Fix for EAP and MPPE interface bugs Edit (2.2 KiB, text/plain)
This patch fixes both the EAP and MPPE interface bugs for me. Again, if someone can help me get familiar with working with my PPA, I'll upload a package. Until then, here's the patch.
Bill Loucks (biloucks) wrote : | #101 |
I'm so desperate, that I just installed Jaunty Alpha 1 to see if there's any improvement in network-
Jeremy Cantrell (jmcantrell) wrote : | #102 |
@William Loucks:
I'm assuming you didn't even try my patch. I'm not sure what made you think that installing Jaunty would improve anything. If a fix was available, don't you think someone would have mentioned it somewhere?
The bottom line is that your whining isn't helping anything. People are aware that there's a problem. Like I've said before, if stability was anywhere near as critical an issue as you're proclaiming, then you should have stuck with an LTS version.
Maybe it's time for you to whip out your editor and start contributing something other than noise.
Tim (tim-barlotta) wrote : | #103 |
@Alexander Sack
Finally installed the network-
With all the complaining going on here, just wanted to thank you for the hard work.
bim (mng-kingston) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN (bad NT-Domain escaping) | #104 |
FYI
Similarly, (even though I don't know what PPTP is
- only that I can't understand how to get a wired
connection to a router with intrepid) -----
I have now given up on Intrepid and am starting
my Linux experience with Hardy.
"bim"
At 2008/11/22 15:32, you wrote:
>I'm so desperate, that I just installed Jaunty Alpha 1 to see if there's
>any improvement in network-
>feces network-
>pardon my colorful language, but this is unacceptable. I did some poking
>around on debian.org, and I see that even Debian EXPERIMENTAL, which is
>out there beyond UNSTABLE, has network-
>give up. I'll keep the Jaunty Alpha 1 on a non-critical machine, and
>keep an eye on what happens, if anything, with network-
>Jaunty. But at this point, I'm not holding my breath.
>
>--
>Network Manager unable to connect to PPTP VPN (bad NT-Domain escaping)
>https:/
>You received this bug notification because you are a direct subscriber
>of the bug.
>
>Status in ânetwork-
>Status in âpptp-linuxâ source package in Ubuntu: Invalid
>Status in network-
>Status in pptp-linux in Ubuntu Intrepid: Invalid
>
>Bug description:
>To verify:
> 1. check that you cannot connect to pptp and
> you are using a NT-Domain in the conncetion config
> 2. verify that this is your bug: leave the
> NT-Domain field empty; instead encode it in username like:
> NT_DOMAIN\USERNAME (e.g. mydomain\myuser)
> 3. upgrade to fixed package and see that it works without the trick in 2.
>
>
>Binary package hint: network-
>
>Package version: 0.7~~svn2008081
>uname -a: Linux jim-d620 2.6.24-19-generic #1
>SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux
>
>I am testing the SVN version of network-manager
>0.7. I am attempting to connect to my employer's
>Windows PPTP VPN. Each time I try, the
>connection fails, displaying a pop-up message
>that says: The VPN connection 'Connection Name'
>failed because the VPN service stopped unexpectedly.
>
>The relevant section of /var/log/syslog is:
>Aug 18 15:15:13 jim-d620 NetworkManager:
><info> Starting VPN service 'org.freedeskto
>Aug 18 15:15:13 jim-d620 NetworkManager:
><info> VPN service
>'org.freedeskt
>(org.freedeskt
>Aug 18 15:15:13 jim-d620 NetworkManager:
><info> VPN service
>'org.freedeskt
>Aug 18 15:15:13 jim-d620 NetworkManager:
><info> VPN service
>'org.freedeskt
>Aug 18 15:15:13 jim-d620 NetworkManager:
>nm_vpn_
>`nm_vpn_
>NM_VPN_
>Aug 18 15:15:13 jim-d620 NetworkManager: <info> VPN plugin state changed: 3
>Aug 18 15:15:13 jim-d620 pppd[16602]: Plugin
>/usr/lib/
neilyalowitz (neilyalowitz) wrote : | #105 |
@Alexander Sack RE: "1longtime, your issue is most likely bug 268667"
This was the first one I tried and bug 268667 fixed my problem. Thanks Alexander. After trying the suggested fix in that bug, my VPN connects successfully.
Oddly, when I tried to "undo" the fix, it continued to connect properly.
@Martin Pitt RE: intrepid-proposed updates
I did an "apt-get upgrade" with entrepid-proposed sources several days ago, before verified the source had updated (and accidentally updated quite a bit more than I expected... oops). I just did another apt-get update/upgrade and found updates for a number of packages, including a couple of pptp packages.
The VPN problem is still fixed, but because I couldn't rollback the fixes from bug 268667 we can't be certain that the updates fixed my issue.
@jmcantrell
Could not find advanced-dialog.c. I'm not sure how to apply your patch.
Another side-note: manually adding "refuser-eap" to ppp options fixed ONE of my Ubuntu boxes but not the other (the one I've been fighting with in this thread). Strange.
Thanks all for the help, but it was a very disruptive bug. Kinda shakes the faith a bit...
Jeremy Cantrell (jmcantrell) wrote : | #106 |
- Patch with correct paths Edit (2.3 KiB, text/plain)
To build your own version of network-
apt-get source network-
apt-get install autotools-dev fakeroot dh-make build-essential
apt-get build-dep network-
cd network-
patch -p0 </path/
dpkg-
Assuming all went well, the deb should be in the parent directory.
I've attached a patch with the corrected paths so patch will recognize it.
Bill Loucks (biloucks) wrote : | #107 |
Regarding refuse-eap: As I stated 2008-11-04 , the manual workaround of using your favorite text editor to add "refuse-eap" to the file ~/.gconf/
1. In 0.7, if you use the gui again, it overwrites your manual workarounds, like refuse-eap.
2. I still cannot modify routes so that only some traffic goes through the vpn while all other traffic goes through my internet gateway.
3. There are still dozens of other parameters which were configurable in 0.6.5 but which are not in 0.7. I don't know how many people here have ever used 0.6.5 under Hardy, but that is why, in my previous post, I showed a text equivalent of the gui for 0.6.5.
Does anyone know where 0.7 came from, and why it was the version which was put in Intrepid, given the fairly large amount of bugs in 0.7, and given the fact (please correct me if I'm wrong) that, according to my understanding, each new release of Ubuntu starts with the latest Debian "unstable", and if I search within Unstable at debian.org ( http://
network-manager: 0.6.6-2
network-
network-
network-
and if I search within Experimental (http://
network-manager: 0.7.0~svn4191-1
network-
network-
network-
I'm wondering if network-
"* Due to misscomprehension with original maintainer, my previous svn sync was a regression, as I synched with 0.6.5 branch while he did with 0.7 beta and backported the sources for 0.6.x.
Reverting the packaging for the moment as we are late in the dev cycle to resync from svn and get potentially something unstable.
* Applyed patch 01_no_icon.dpatch
* Removed network-
* Added missing build-dep libnm-util-dev"
Final note: I used aptitude, in Intrepid, to downgrade the five related packages (network-manager, network-
kalyp (kalyp) wrote : | #108 |
@jmcantrell: I just followed your instructions, I've been able to build the package and it works perfectly fine now, thank you so much! I don't know why but I couldn't make it work even by setting refuse-eap in gconf-editor. But with the patched version it worked at first try. Thanks!!
Alexander Sack (asac) wrote : | #109 |
jmcantrell, I moved your refulse-eap issue to bug 301593 ... lets continue discussion there. will subscribe you.
Bill Loucks (biloucks) wrote : | #110 |
For those of you who can answer "yes" to all five of the following questions:
* Are you still using Intrepid?
* Do you neither use nor require the new features of NetworkManager 0.7 such as "Mobile Broadband" and "DSL"?
* Do you want to stay with Intrepid?
* Do you want to revert Intrepid's network-
* Are you willing to take risks and not blame me if something goes wrong?
I've created "new" versions of the five related packages with version numbers such that they are "newer" than 0.7, but are actually the same packages and versions which were in Hardy. These are only for the i386 architecture. I've tested them as well as I can and would like volunteers for additional testing. I did not sign these packages, so you will have to understand what that means. To become a volunteer tester, do these steps:
1. Add the following to Software Sources:
deb http://
2. Use update-manager or synaptic to check the software channels for new updates or reload the package information.
3. For your information, the "new" versions of the five packages are:
libnm-glib0 0.7+0.6.6
libnm-util0 0.7+0.6.6
network-manager 0.7+0.6.6
network-
network-
4. Install all five of the packages shown in #3 above, after verifying that the "new" version is as listed in #3 above.
5. Reboot, just be safe
6. If you previously used network-
7. Set up your favorite pptp connection and test it.
ironfisher (dgvalde) wrote : | #111 |
Everything work for me now without doing anything special. I just tried choosing others protocols and parameters (and not those which my university said me)
Sorry for my bad English.
description: | updated |
Bill Loucks (biloucks) wrote : | #112 |
Bug 278309 is, so far, the most inclusive of all the various bugs I've found yet for network-
Alexander Sack (asac) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN (bad NT-Domain escaping) | #113 |
On Thu, Nov 27, 2008 at 01:46:14AM -0000, William Loucks wrote:
> For those of you who can answer "yes" to all five of the following
> questions:
Please display a big warning: when you instlal these packages you will
never upgrade to any NetworkManager 0.7 ... if you provide these
packages, please do so outside of bugs. Thanks!
- Alexander
Bill Loucks (biloucks) wrote : | #114 |
@Mr. Sack: the updated document is here: http://
My sincere apologies for any trouble this may have caused.
Launchpad Janitor (janitor) wrote : | #115 |
This bug was fixed in the package network-
---------------
network-
* LP: #259168 Network Manager unable to connect to PPTP VPN (bad NT-Domain
escaping); we improve ppp domain in username encoding
- add debian/
* LP: #268667 MASTER - not all required ppp options get set on command line
which makes ppp use bad values from /etc/ppp/options*; we explicitly set
good values for: nodefaultroute, lcp-echo-failure and lcp-echo-interval
- add debian/
* LP: #292681 crash when running auth-dialog and secret in keyring;
we use the proper memory functions in this patch (dupe-of LP: #284212
VPN connection fails: "unable to find valid VPN secrets")
- add debian/
* LP: #290468 VPN fails, "/usr/bin/
obsolete conffiles in .preinst now
- add debian/
-- Alexander Sack <email address hidden> Thu, 30 Oct 2008 00:22:51 +0100
Changed in network-manager-pptp: | |
status: | Fix Committed → Fix Released |
Craig (candrews-integralblue) wrote : | #116 |
Network manager upstream's bug tracker is http://
Alexander Sack (asac) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN | #117 |
On Mon, Nov 03, 2008 at 11:35:34PM -0000, chadeldridge wrote:
> After doing the refuse-eap and upgrading to the module above I am also
> working. I assume that the final fix will include the refuse-eap as a
> check option in the pptp config?
>
Yes, next update round will fix that. we have bug 301593 for
this. There are also some routing issues I want to sort out before
that upload. So please be just a bit more patient. Thanks!
- Alexander
Alexander Sack (asac) wrote : | #118 |
On Tue, Nov 04, 2008 at 03:28:28PM -0000, mklebel wrote:
> Works now. upgrading to the PPA version fixed it.
>
> Another issue,
> but I'm not sure if this is a bug or I'm uneducated with network-manager but it rewrites my /etc/resolv.conf to use the remote VPN gateway instead of my local gateway. I tail syslog and it sets ppp0 as default for routing and DNS, I want it to go all through eth1.
>
You should be able to configure your pptp IP4Settings to not use the
DNS server that ppp gives you ... just look in connection editor.
But remember that we have bug 303165 ... so in case that doesnt work
also be a bit patient. The fix for that is in the pipelin for the
network-manager package.
- Alexander
Alexander Sack (asac) wrote : Re: [Bug 259168] Re: Network Manager unable to connect to PPTP VPN (bad NT-Domain escaping) | #119 |
jmcantrell wrote:
> This patch fixes both the EAP and MPPE interface bugs for me. Again, if
> someone can help me get familiar with working with my PPA, I'll upload a
> package. Until then, here's the patch.
>
> ** Attachment added: "Fix for EAP and MPPE interface bugs"
> http://
>
>
can yo uplease post this to the proper bug?
I'm trying to connect to my university's VPN and keep getting the same libnotify error message with Intrepid (up-to-date packages): "The VPN connection 'Connection Name' failed because the VPN service stopped unexpectedly."
Sep 4 12:23:45 newton NetworkManager: <info> Starting VPN service 'org.freedeskto p.NetworkManage r.vpnc' ... p.NetworkManage r.vpnc' started (org.freedeskto p.NetworkManage r.vpnc) , PID 8299 p.NetworkManage r.vpnc' just appeared, activating connections manager[ 6340]: DEBUG(+): GsmXsmpServer: accept_ ice_connection( ) manager[ 6340]: DEBUG(+): GsmXSMPClient: Setting up new connection manager[ 6340]: DEBUG(+): GsmXSMPClient: New client '0x8bd6298 []' manager[ 6340]: DEBUG(+): GsmStore: Adding object id /org/gnome/ SessionManager/ Client17 to store manager[ 6340]: DEBUG(+): GsmManager: Client added: /org/gnome/ SessionManager/ Client17 manager[ 6340]: DEBUG(+): GsmXSMPClient: Initializing client 0x8bd6298 [] manager[ 6340]: DEBUG(+): GsmXSMPClient: Client '0x8bd6298 []' received RegisterClient( 109202a053a1142 db1122052314346 339000000634000 22) manager[ 6340]: DEBUG(+): GsmManager: Adding new client 109202a053a1142 db1122052314346 339000000634000 22 to session manager[ 6340]: DEBUG(+): GsmXSMPClient: Sending RegisterClientReply to '0x8bd6298 [109202a053a114 2db112205231434 633900000063400 022]' manager[ 6340]: DEBUG(+): GsmXSMPClient: Set properties from client '0x8bd6298 [109202a053a114 2db112205231434 633900000063400 022]' manager[ 6340]: DEBUG(+): GsmXSMPClient: CurrentDirectory = '/home/lantash' manager[ 6340]: DEBUG(+): GsmXSMPClient: Set properties from client '0x8bd6298 [109202a053a114 2db112205231434 633900000063400 022]' manager[ 6340]: DEBUG(+): GsmXSMPClient: ProcessID = '8302' manager[ 6340]: DEBUG(+): GsmXSMPClient: Set properties from client '0x8bd6298 [109202a053a114 2db112205231434 633900000063400 022]' manager[ 6340]: DEBUG(+): GsmXSMPClient: Program = 'nm-vpnc- auth-dialog' manager[ 6340]: DEBUG(+): GsmXSMPClient: Set properties from client '0x8bd6298 [nm-vpnc- auth-dialog 109202a053a1142 db1122052314346 339000000634000 22]' manager[ 6340]: DEBUG(+): GsmXSMPClient: CloneCommand = 'nm-vpnc- auth-dialog' manager[ 6340]: DEBUG(+): GsmXSMPClient: Set properties from client '0x8bd6298 [nm-vpnc- auth-dialog 109202a053a1142 db1122052314346 339000000634000 22]' manager[ 6340]: DEBUG(+): GsmXSMPClient: Re...
Sep 4 12:23:45 newton NetworkManager: <info> VPN service 'org.freedeskto
Sep 4 12:23:45 newton NetworkManager: <info> VPN service 'org.freedeskto
Sep 4 12:23:45 newton NetworkManager: <info> VPN plugin state changed: 1
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-
Sep 4 12:23:45 newton x-session-