pptp client
 getting started
 try it
 fedora core 1
 fedora core 2
 fedora core 3
 fedora core 4
 fedora core 5
 fedora core 6
 mandrake 9.0
 mandrake 10.0
 mandrake 10.1
 red hat 9
 red hat 8.0
 red hat 7.3
 suse 10.0
 suse 9.2
 suse 9.1
 suse 8.2
 support faq
 contact us

PPTP Client


by Ross Beveridge, James Cameron & others
3rd September 2004


With the default install, PPTP Client 1.4.0 and PPP 2.4.2 are included, as packages pptp-1.4.0-39 and ppp-2.4.2-39 respectively.

However, SUSE packaged the older format options file. A bug has been raised. To workaround this, edit the /etc/ppp/options.pptp file and change the MPPE options like this:



If you are using SuSE firewall in it's default state, you will not be able to make a connection. You must either turn it off by typing SuSEfirewall2 off, or reconfigure it as follows:

  1. open YaST,
  2. click on System which is on the left hand side,
  3. open the /etc/sysconfig Editor,
  4. click +Network then +Firewall then +SuSEfirewall2,
  5. add "1723" to FW_SERVICES_EXT_TCP,
  6. add "GRE" to FW_SERVICES_EXT_IP, FW_SERVICES_DMZ_IP, FW_SERVICES_INT_IP and FW_SERVICES_QUICK_IP (we're not sure if all four are required, it depends on where the server is in relation to your client, as far as the network interfaces are concerned),
  7. click FINISH.

Minimal Effort Installation

  1. download the configuration program pptp-php-gtk rpm (mirror link) and install it like this:

    # rpm --install --nodeps pptp-php-gtk-20040102-rc1.i386.rpm

    Note: RPM will issue warnings and errors about the Red Hat specific /etc/security/console.apps directory, but we found that it works fine otherwise.

Maximising Versions Installation

(Thanks to N715DP in the IRC channel.)

  1. remove the existing PPTP client program supplied by SUSE:

    rpm --erase pptp

  2. download the PPTP client program pptp-linux rpm (mirror link) and install it like this:

    # rpm --install --nodeps pptp-linux-1.5.0-1.i386.rpm

  3. download the configuration program interpreter php-pcntl rpm (mirror link) and install it like this:

    # rpm --install --nodeps php-pcntl-4.3.7-2.i386.rpm

  4. download the configuration program GTK+ interface php-gtk-pcntl rpm (mirror link) and install it like this:

    # rpm --install --nodeps php-gtk-pcntl-1.0.0-2.i386.rpm

  5. download the configuration program pptpconfig rpm (mirror link) and install it like this:

    # rpm --install --nodeps pptpconfig-20040619-0.noarch.rpm

  6. run pptpconfig, set up IP address of VPN and so forth, enable "all to tunnel" and hit start ...


  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 pptp-php-gtk.php or 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.


If you have comments on this document, please send them to the author at quozl at laptop.org. But if you need help, use the mailing list so that we can share the load.


2004-09-03 Revision following IRC discussion.
2004-06-11 First draft from author.