Introduction

This briefly describes how to install PPTP Client on a Mandrake 10.0 system.

The Mandrake 10.0 installation kernel already has the MPPE module, the PPP package already has MPPE support, but doesn't work with some PPTP servers, and PPTP Client version 1.3.1 is included.

Thank you to Lindsay who sent us a Mandrake 10.0 CD set!

Minimal Effort Installation

1. if you don't have the full CD set, configure urpmi to use a mirror on the internet:

   urpmi.addmedia main \ ftp://distro.ibiblio.org/pub/Linux/distributions/\ mandrake/Mandrakelinux/official/10.0/i586/Mandrake/RPMS \ with ../base/synthesis.hdlist.cz

   Note: we used urpmi.org's Easyurpmi tool to derive the above.

2. install the pptp-linux package:

   urpmi pptp-linux

   Note: if you are more familiar with rpmdrake you may wish to use it instead of urpmi.

3. configure using the old pptp-command program:

   pptp-command

   Note: pptp-command is difficult to use for some people. If you would like to use a window instead, see our more completed installation script below.

   Note: when used against a pptpd running pppd 2.4.2, this may result in an error in /var/log/messages "LCP terminated by peer (MPPE required but peer refused)". Our solution was to use the more complete installation script below.

1. download the ppp mdk.i586.rpm from POPTOP project downloads and upgrade like this:

   rpm --upgrade ppp-2.4.3-4mdk10.1.i586.rpm

2. download the pptp-linux i386.rpm from PPTP Client downloads and upgrade like this:

   rpm --upgrade pptp-1.6.0-1.i386.rpm

3. download the php-pcntl, php-gtk-pcntl, and pptpconfig i386.rpm's from PPTP Client project downloads and install like this:

   rpm --upgrade php-pcntl-4.3.10-1.i386.rpm urpmi libglade libxml rpm --upgrade php-gtk-pcntl-1.0.1-2.i386.rpm rpm --upgrade pptpconfig-20040722-6mdk.noarch.rpm

   Note: change the file names to correspond to the versions available.

1. obtain from your PPTP Server administrator:
   • the IP address or host name of the server,
   • the authentication domain name, (e.g. WORKGROUP),
   • the username you are to use,
   • the password you are to use,
   • whether encryption is required.

2. run pptpconfig as root, and a window should appear,

   

3. enter the server, domain, username and password into the Server tab,

4. if you decided in Installation step 1 above that you would need MPPE, and if your administrator says encryption is required, then on the Encryption tab, click on Require Microsoft Point-to-Point Encryption (MPPE),

   

5. click on Add, and the tunnel will appear in the list,

6. click on the tunnel to select it, click on Start, and a window will appear with the tunnel connection log and status,

7. if the connection fails, you will need to gather more information, so on the Miscellaneous tab, click on Enable connection debugging facilities, click Update, try Start again, then look at the Diagnosis HOWTO for whatever error is displayed.

   

8. if the connection succeeded, you can try the Ping test button. If the ping fails, you should try to find out why before proceeding. If the ping works, then the tunnel is active and you may now work on routing.

9. decide whether all your network traffic should go via the tunnel or not. If so, Stop the tunnel, select it again, then on the Routing tab, click on All to Tunnel, then click Update and try Start again. Now try to access the network behind the server.

10. on the other hand, if only some of your network traffic should go via the tunnel, you will need to obtain from the server administrator or folk lore a series of network routes to enter. Stop the tunnel, select it again, then click on either Client to LAN or LAN to LAN on the Routing tab, use the Edit Network Routes button to enter the routes one by one, and then try Start again. Now try to access the network behind the server.

    

    For further help with Routing, read our Routing HOWTO.

Comments

ChangeLog