[pptp-server] EMERGENCY!! Clients can't get in!! SOLVED!!

Eric H. Raskin eraskin at paslists.com
Thu Jun 15 11:29:38 CDT 2000


Hello all:

  I've got it working again, but it's a real hack!!

  For whatever reason, even though I never specified it, PPPD was behaving as if
the "noipdefault" option was specified.  There is a bug in PPPD that if
"noipdefault" is specified along with a local and remote ip address, it blows
away the local ip address.  Here is the patch I applied to pppd-2.3.11 to get it
to work.  Please be aware that this patch is probably not correct -- it just
gets my stuff working again!!  YMMV!!

-------------------------------------------------------

*** ipcp.c.orig Thu Jun 15 11:17:37 2000
--- ipcp.c      Thu Jun 15 11:06:51 2000
***************
*** 456,467 ****
--- 456,469 ----
      if (wo->hisaddr == 0)
        wo->accept_remote = 1;
      wo->req_dns1 = usepeerdns;        /* Request DNS addresses from the peer
*/
      wo->req_dns2 = usepeerdns;
      *go = *wo;
+ /*
      if (disable_defaultip)
        go->ouraddr = 0;
+ */
  }


  /*
   * ipcp_cilen - Return length of our CI.

-------------------------------------------------------------

So, it's not a routing problem or a kernel patch problem (thank the gods!).
Setting conditional routing on a remote Windows 98 box is a real killer!!

Question for everyone:  Does pppd always read the /etc/ppp/options file, even if
pptpd gives it a different options file to read?  If so, that would explain my
problem -- "noipdefault" *was* specified in there.  I always thought the
specifying a new options file on the command line would  override the original.
Maybe it just overlayed new settings on the old -- allowing the "noipdefault" to
get through.  That would trigger the pppd bug and give me all this grief!!

In any event, since I don't use pppd for anything else, I'll leave my hack in
there for now.  But, I'm commenting out the "noipdefault" in /etc/ppp/options
just in case!!

Thanks to everyone who responded.

   Eric Raskin



> -----Original Message-----
> From: pptp-server-admin at lists.schulte.org
> [mailto:pptp-server-admin at lists.schulte.org]On Behalf Of Eric
> H. Raskin
> Sent: Thursday, June 15, 2000 12:08 PM
> To: pptp-server at lists.schulte.org
> Subject: RE: [pptp-server] EMERGENCY!! Clients can't get in!!
>
>
> I'll try it, but I don't think so.  The remote network is
> using the *ugly*
> Windows Internet Sharing server.  They have to be on the
> 192.168.1.x network in
> order to work.  I don't know if it will route to 192.168.10.x
> at the Windows
> side.  Does anyone else?
>
> Besides, why would I have a problem with the *local* ip
> address if the *remote*
> ip address is on the wrong subnet?
>
>   Eric
>
> P.S.  I'm not trying to be difficult.  I'm just trying to
> understand the logic!
> :-)
>
> > -----Original Message-----
> > From: Andrew McRory [mailto:amacc at iron-bridge.net]
> > Sent: Thursday, June 15, 2000 11:45 AM
> > To: Eric H. Raskin
> > Cc: pptp-server at lists.schulte.org
> > Subject: Re: [pptp-server] EMERGENCY!! Clients can't get in!!
> >
> >
> > On Thu, 15 Jun 2000, Eric H. Raskin wrote:
> >
> > > Hello all:
> > >
> > > I've got an emergency here because clients can't get in.
> I've been
> > > (and continue to) look at the Usenet postings for any
> help on this,
> > > but I'm taking too long to find what I need.  Sorry ahead
> of time if
> > > this is a FAQ (although I didn't find anything about it in
> > the PoPToP
> > > FAQ or the PPP FAQ).
> > >
> > > I've had a working PoPToP v1.0.0 configuration (without MPPE) for
> > > about 1 month now.  After hearing about problems with security in
> > > kernel 2.2.14, I've just upgraded to 2.2.16, following
> the excellent
> > > instructions from Boris Reisig (boris at microtrader.com).
> > >
> > > Unfortunately, now my clients can't connect!!  I'm getting
> > the following in the
> > > log file:
> > >
> > >   pppd[2229]: Could not determine local IP address
> > >
> > > Here is my /etc/pptpd.conf file:
> > >
> > > speed 115200
> > > option /etc/ppp/pptpd.options
> > > debug
> > > localip 192.168.10.1
> > > remoteip 192.168.1.2-254
> >
> >                   ^^^
> >
> > ummm maybe should that be 192.168.10.2-254?
> >
> >
> > Andrew McRory - President/CTO     amacc at iron-bridge.net
> > ******************
> > Iron Bridge Communications, Inc.  www.iron-bridge.net
> > 850-575-0779 ***
> > The PC Doctor, Inc.               www.pcdr.com
> > 850-575-2713 ***
> > Caldera OpenLinux Contrib RPMS
> ftp.iron-bridge.net/pub/Caldera      ***
> **************************************************************
> ************
>
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> List services provided by www.schulteconsulting.com!




More information about the pptp-server mailing list