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
You may also need to enable proxy-ARP on each interface if you're assigning local Ethernet LAN addresses, as well as configuring DNS and NBNS server information for client bundles using the
# # Act like a PPTP server allowing clients to connect # Pptp0: set link type pptp set pptp enable incoming set pptp disable originate
set ipcp dnsand
set ipcp nbnscommands.
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 220.127.116.11/32 18.104.22.168/32 ... Pptp2: new -i ng1 Pptp2 Pptp2 ... set ipcp ranges 22.214.171.124/32 126.96.36.199/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
is the local IP address and
188.8.131.52 is the remote
On the remote machine, you'd have the same entry with the
# # Tunnelling PPP traffic over a PPTP connection with peer 184.108.40.206 # Pptp1: set link type pptp set pptp self 220.127.116.11 set pptp peer 18.104.22.168 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