[pptp-server] Fixed IPs using PoPToP

Cowles, Steve Steve at SteveCowles.com
Mon Feb 19 16:30:22 CST 2001


> -----Original Message-----
> From: Giulio Orsero [mailto:giulioo at pobox.com]
> Sent: Monday, February 19, 2001 2:31 PM
> To: pptp-server at lists.schulte.org
> Subject: Re: [pptp-server] Fixed IPs using PoPToP
> 
> 
> On Mon, 19 Feb 2001 09:45:00 +0100, you wrote:
> 
> > 4.2 How can I assign IP addresses based on user names?
> > Configure PoPToP with the command:
> >   ./configure --with-pppd-ip-alloc
> >
> > Then build and install PoPToP as usual.  List the IP 
> > addresses as the last parameter on each chap-secrets
> > line.  For example:
> >
> >	tom	*	toms-pw	192.168.1.40
> >	dick	*	dicks-pw	192.168.1.41
> >	harry	*	harrys-pw	192.168.1.42
> 
> Will the above assign tom 192.168.1.40, or just allow tom to use
> 192.168.1.40?
> 
> I made a quick test, and I had to specify the ip in the dial-up
> networking properties, because pppd would not assign me the ip
> associated to my login automatically. pppd docs seem to suggest
> that field is for the ip the user is "allowed" to use; is there
> some pptpd magic that should "assign" the ip?

The only "magic" I'm aware of is to only specify the localip in
/etc/pptpd.conf. I commented the remoteip line. (see below)

At least the following worked for me. FYI: 192.168.9.3 is also the ip
address of my PPTP servers eth0 interface. I am also using pptp-1.1.2

Steve Cowles

####### /etc/pptpd.conf  ########
localip 192.168.9.3
# remoteip 192.168.9.100-105

###### /etc/ppp/chap-secrets #########
# Secrets for authentication using CHAP
# client          server     secret      IP addresses
scowles           voyager    password    192.168.9.107
pcowles           voyager    password    192.168.9.108

###### /etc/ppp/options #########
lock
auth
mru 1450
mtu 1450
name voyager
domain mydomain.com
ms-dns 192.168.9.3
ms-dns 192.168.9.2
ms-wins 192.168.9.2
require-chap
+chap
+chapms
+chapms-v2
mppe-40
mppe-128
mppe-stateless
proxyarp

I'm using W2K as the PPTP client and changing the username/password on each
connect. PPTP client's TCP/IP settings are configured to: Obtain an IP
address automatically

########## /var/log/messages ###############
Feb 19 16:14:29 voyager pppd[30016]: MSCHAP-v2 peer authentication
succeeded for scowles
Feb 19 16:14:29 voyager pppd[30016]: found interface eth0 for proxy arp
Feb 19 16:14:29 voyager pppd[30016]: local  IP address 192.168.9.3
Feb 19 16:14:29 voyager pppd[30016]: remote IP address 192.168.9.107

########## /var/log/messages ###############
Feb 19 16:15:07 voyager pppd[30045]: MSCHAP-v2 peer authentication
succeeded for pcowles
Feb 19 16:15:07 voyager pppd[30045]: found interface eth0 for proxy arp
Feb 19 16:15:07 voyager pppd[30045]: local  IP address 192.168.9.3
Feb 19 16:15:07 voyager pppd[30045]: remote IP address 192.168.9.108

########## /var/log/messages ###############
Feb 19 16:28:55 voyager pppd[32008]: MSCHAP-v2 peer authentication succeeded
for scowles
Feb 19 16:28:55 voyager pppd[32008]: found interface eth0 for proxy arp
Feb 19 16:28:55 voyager pppd[32008]: local  IP address 192.168.9.3
Feb 19 16:28:55 voyager pppd[32008]: remote IP address 192.168.9.107



More information about the pptp-server mailing list