Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Jul 2000 11:10:33 -0400 (EDT)
From:      Barney Wolff <barney@databus.com>
To:        freebsd-net@freebsd.org
Subject:   Re: Win2000 -> FreeBSD PPPoE daemon
Message-ID:  <200007181510.LAA33088@mx.databus.com>
In-Reply-To: <200007180751.IAA19521@hak.lan.Awfulhak.org> from Brian Somers at "Jul 18, 2000 08:51:21 am"

next in thread | previous in thread | raw e-mail | index | archive | help
I have a vague memory that Win95 (and therefore probably Win98) allowed
a single dial-IN to itself, and contained ppp server functionality for
that one connection.  Perhaps w2k-pro has removed it.  It is normal for
a ppp client to send the ipcp conf-req asking for 0.0.0.0, expecting to
get a conf-nak with the ip address assigned by the server.  The client
then sends another conf-req with the server-assigned ip address, which
the server acks.

Why is the fbsd box acting as a client, rather than a server?  Who
initiated the "connection"?

One side or the other is going to have to assign ip addresses to each
side of the connection.

Have you tried connecting two w2kpro boxes this way?  Does it work?

Barney Wolff  <barney@databus.com>

> > Hi Brian,
> > 
> > Thanks for the quick response (it's late where you live,
> > isn't it? :-)
> > 
> > > It sounds like you haven't done a
> > > 
> > >   set ifaddr something hisnumber
> > > 
> > > in your config.  Without this, if the peer asks for 0.0.0.0, ppp will
> > > just say ``yeah, fine, I don't know any better''.  Make ``hisnumber''
> > > whatever you want him to use and make ``something'' whatever you want
> > > to use locally - probably just your NIC iface IP address (dups are ok
> > > as long as only one is a broadcast device).
> > 
> > We'll try that tomorrow (the test equipment is 65 miles away
> > and my testing buddy has gone home :).
> 
> Looking at things a bit more carefully, it looks like the 
> ``something'' bit is what's missing.  ppp(8) is sending REQs with 
> 0.0.0.0 (saying ``I'd like to have IP 0.0.0.0 please'').
> 
> Perhaps you've got ``set ifaddr 0 0'' in your config ?  If so, you 
> can probably get away with just removing that line.  The default is 
> ``set ifaddr MYADDR 0''.
> 
> > But the curious thing(s) is that this *same* setup, with no
> > changes on the FreeBSD end, works as-is with Win98 (with the
> > same Windows settings).
> 
> This is strange.  Win98 must be assigning ppp(8) an IP number, or 
> maybe it's letting it have 0.0.0.0 and is managing to route through 
> it.  ppp(8) doesn't care about it's local interface address (although 
> I would have guessed that things would go wrong if it ended up with 
> 0.0.0.0).
> 
> > Also, did you see the part in the trace where we asked for
> > the specific IP address and FreeBSD did ack that configuration?
> 
> Not until now :-/  It looks like the problem is that ppp(8) is 
> requesting 0.0.0.0 and Win2000 is (correctly) saying ``don't be 
> silly''.
> 
> > If it's just a server setup problem, that's fine, we'll change
> > it.  But I'm just curious as to what's going on...
> > 
> > BTW, just out of curiousity, why does FreeBSD reject the
> > identification packets?  Does it really not understand them?
> 
> Never heard of them...  I take it these are Multi-link Procedure 
> options ?  I'll stick this on my todo list I guess :-)
> 
> > Thanks,
> > Gary
> 
> Cheers.
> 
> -- 
> Brian <brian@Awfulhak.org>                        <brian@[uk.]FreeBSD.org>
>       <http://www.Awfulhak.org>;                   <brian@[uk.]OpenBSD.org>
> Don't _EVER_ lose your sense of humour !
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007181510.LAA33088>