5.5.1. PPTP setup hints

If what you want to do is setup a PPTP server for remote clients to connect to your LAN, you would want something like this for each mpd.links entry:

#
# Act like a PPTP server allowing clients to connect
#
Pptp0:
    set link type pptp
    set pptp enable incoming
    set pptp disable originate

If you want multiple simultaneous clients to be able to connect, you should define (and load) multiple bundles, one for each potential client. Each bundle should negotiate a different peer proxy-ARP IP address to avoid conflicts. For example:

#
# mpd.conf: allow up to 2 clients
#
default:
    load Pptp1
    load Pptp2

Pptp1:
    new -i ng0 Pptp1 Pptp1
    ...
    set ipcp ranges 1.1.1.1/32 1.1.1.101/32
    ...

Pptp2:
    new -i ng1 Pptp2 Pptp2
    ...
    set ipcp ranges 1.1.1.1/32 1.1.1.102/32
    ...

If instead you want to set up a peer-to-peer symmetrical tunnelling arrangement (i.e., normal IP routing using PPP over PPTP), you might want something like this (here 1.1.1.1 is the local IP address and 2.2.2.2 is the remote IP address):

#
# Tunnelling PPP traffic over a PPTP connection with peer 2.2.2.2
#
Pptp1:
    set link type pptp
    set pptp self 1.1.1.1
    set pptp peer 2.2.2.2
    set pptp enable incoming originate

Note that if you are connecting to an NT server, your authentication name must include the NT domain name. For example:

    set auth authname "DOMAIN\\username"

For updating Windows 95 and 98 clients so they work properly, see VPN Update for Windows 98 and Dial-Up Networking 1.3 Available