[pptp-server] (no subject)

[robert]

Actually, it *CAN* be a range.  However, this just wastes IP addresses.  Only 
one is NEEDED.  Also, the internal IP and localip should not be the same 
address, but should be in the same subnet unless you want to do fancy routing 
tricks.  In any case, the original problem looks like a missing variable in 
the pptpd.conf file.  localip is not set.

On Monday 15 April 2002 03:16 am, Richard wrote:
> check if your internal interface and the variable "localip" in
> /etc/pptpd.conf are the same. Also "localip" MUST be one IP, and NOT
> something like 192.168.0.1-[some other number]
>
>
> Regards,
> Richard
>
> > On Sun, 14 Apr 2002 sfesta at spidermite.net wrote:
> >
> > [...]
> >
> > > Apr 14 15:01:51 argon pptpd[2504]: CTRL: Client 192.168.0.252 control
> > > connection
> > > started
> > > Apr 14 15:01:51 argon pptpd[2504]: CTRL: Starting call (launching pppd,
> > > opening GRE)Apr 14 15:01:51 argon pppd[2505]: pppd 2.4.1 started by
> > > root, uid 0
> > > Apr 14 15:01:51 argon pppd[2505]: Using interface ppp0
> > > Apr 14 15:01:51 argon pppd[2505]: Connect: ppp0 <--> /dev/pts/2
> > > Apr 14 15:01:51 argon /etc/hotplug/net.agent: assuming ppp0 is already
> > > up Apr 14 15:01:54 argon pppd[2505]: MSCHAP-v2 peer authentication
> > > succeeded for
> > > sfestaApr 14 15:01:54 argon pppd[2505]: Could not determine local IP
> > > address
> > > Apr 14 15:01:54 argon pppd[2505]: Connection terminated.
> > > Apr 14 15:01:54 argon pppd[2505]: Connect time 0.1 minutes.
> > > Apr 14 15:01:54 argon pppd[2505]: Sent 140 bytes, received 100 bytes.
> > > Apr 14 15:01:54 argon pppd[2505]: Exit.