Re: [opensuse] Does PPTP VPN actually work in SUSE 10.2?



James Knott wrote:
Sylvester Lykkehus wrote:
James Knott wrote:
I have been trying unsuccessfully to use PPTP VPN to connect to a couple of remote networks. One requires a domain name and the other doesn't. I have been following some advice in this forum as well as google searching. I have tried webmin, kvnc, the knetworkmanager mods etc., but cannot find any method that allows me to set up what should be a simple VPN connection. This makes me wonder if the pptp client in SUSE actually works! Has anyone come up with a simple, reliable method for configuring a PPTP VPN? I have a valid username, host address, domain name and password for doing this. What else do I need??? What about clear instructions for just using the pptp command???


tnx jk

Hi James,

As I have not upgraded to 10.2 just yet, I wouldn't know of any problems with PPTP in it.

I do however, have both the PPTP server and client running and working on 10.0, and the procedures should be the same.

The company I am connection to is running MS vpn, with mschap-v2 auth and 128bit mppe encryption.

This is how I configured it:
I did not have much luck with the rpm's available for the pptpclient, therefore i used the tar.gz version

1. Get the latest pptpclient from http://pptpclient.sourceforge.net/ (direct link: http://mesh.dl.sourceforge.net/sourceforge/pptpclient/pptp-1.7.1.tar.gz)

2. Unpack, compile (make), and install (make install (as root))

3. You should now have a decent /etc/ppp/options.pptp file, configured for mschap-v2.
If you need mppe encryption, uncomment the line thats says "#require-mppe-128".

4. Create a file under /etc/ppp/peers/, e.g. /etc/ppp/peers/company, which contains your username and specific options for this peer.
My /etc/ppp/peers/company looks like this:
name DOMAIN\\USERNAME
remotename DOMAIN\\USERNAME
file /etc/ppp/options.pptp
Remember, there has to be 2 backslashes at the domain/username seperation.

5. You have to insert you username and password to /etc/ppp/chap-secrets in the format:
client hostname <password> IP addresses
My /etc/ppp/peers/chap-secrets looks like this:
"DOMAIN\\USERNAME" "*" mypassword

6. You should be able to connect to the VPN server with the pptp command:
pptp <host/ip> call <name of peer file>, in this case:
pptp vpn.company.net call company


Hope this helps, it works for me in 10.0

Well, I'm getting a bit further. Now, I get the following error message. (I've changed remote system name, to protect the guilty. <g>)

/usr/sbin/pppd: The remote system (xxxxxx) is required to authenticate itself
/usr/sbin/pppd: but I couldn't find any suitable secret (password) for it to use to do so.
/usr/sbin/pppd: (None of the available passwords would let it use an IP address.)

tnx jk


Hi James,

If you followed my directions, you would have added 3 columns to the /etc/ppp/chap-secrets file, for each entry.
As noted on http://pptpclient.sourceforge.net/howto-diagnosis.phtml#required_to_auth_ip
some version of pppd requires 4 items for an entry. You should be fine just adding "*" as the fourth item of your entry, e.g.:
"DOMAIN\\USERNAME" "*" mypassword "*"

Feel free to keep me posted on your progress.

Best regards
Sylvester Lykkehus
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx



Relevant Pages

  • Re: PPC VPN woes
    ... When you connect with PPTP is the connection dropping when you try to access ... but when using movian you shouldn't see that same problem cause movian ... > past week have been trying to get VPN to play nicely. ... With the exception of remote ...
    (microsoft.public.pocketpc.wireless)
  • Re: Question about Remote Administration (XP) over VPN
    ... Using a VPN with L2TP will ... use and require a user certificate smart card for logon to the PPTP. ... we only allow Remote Administration and Offer Remote Assistance ...
    (microsoft.public.security)
  • Re: VPN Limit
    ... This is from one remote IP address, ... The PPTP specification allows for multiple VPN tunnels between the same two IP addresses, but with one TCP/IP control channel common to all. ... The SBS can accept more than one VPN, but it relies on matching remote IP addresses in order to associate the VPN control and data channels, and if there are two of each channel, both claiming to come from the same remote IP address, there's no way of doing that. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN without Firewall?!
    ... > PPTP is also cheap because from remote side you can simply use the VPN ... > client distributed with Micro$oft OSs. ... PPTP has been broken and shouldn't be used anymore. ...
    (comp.security.misc)
  • Re: VPN without Firewall?!
    ... > PPTP is also cheap because from remote side you can simply use the VPN ... > client distributed with Micro$oft OSs. ... PPTP has been broken and shouldn't be used anymore. ...
    (comp.security.firewalls)