Comment 0 for bug 352600

Binary package hint: network-manager-pptp

I'm using Jaunty.
I wonder if the default options for VPN connections in network-manager-pptp might be set to something that's more likely to work out of the box than that which is currently set.

PPTP is perhaps most commonly used in the Windows world, and for other simple-to-configure road-warrior type setups, e.g. Draytek routers and what not.

The defaults out of the box on Jaunty do not appear to work with a typical Microsoft Routing and Remote Access Sever (RRAS) setup.

It seems that the following needs to be changed before a connection can be made:

EAP needs to be de-selected as an authentication method, else we see something like this from pppd:
EAP: unknown authentication type 13; Naking
LCP terminated by peer (+M-`^BM-4^@<M-Mt^@^@^BM-3)

MPPE needs to be enabled, else we see something like this:
Mar 31 19:33:31 mediaxp kernel: [ 7008.521609] PPP BSD Compression module registered
Mar 31 19:33:31 mediaxp kernel: [ 7008.548198] PPP Deflate Compression module registered
Mar 31 19:33:31 mediaxp pppd[9687]: LCP terminated by peer (4M-vXM-2^@<M-Mt^@^@^BM-f)
Mar 31 19:33:34 mediaxp pppd[9687]: Connection terminated.

It seems that with MPPE enabled, we no longer get the BSD Compression or PPP Deflate messages from the kernel, but instead we get "MPPE 128-bit stateless compression enabled", and the connection works as it should, bar the routing issues which are sorted by manually entering the network/mask in the IPv4 settings tab - I beleive this is a known issue.

So I wonder if it would make sense to set these options as default.

I can do some testing against Draytek routers (2600, 2800 & 3100) if this would be of any use. I seem unable to get a connection to a pfSense box in Leeds.