[openbeosnetteam] Re: PPP up/opened

> > > Then I do not understand the section "3.4. Link Establishment 
> > > Phase".
> > > It
> > > first says that there is an exchange of Configure packets. Then 
> > > it
> > > says this
> > > exchange is "complete" (does this mean an Ack is needed?) and the
> > > "LCP
> > > Opened state entered, once a Configure-Ack packet [...] has been 
> > > both
> > > sent
> > > and received.". So, what does this "sent and received" mean then? 
> > > Is
> > > this
> > > referring to the same machine or does the peer receive the 
> > > packet?
> > > How does
> > > the sender know that his packet was received? Through another Ack
> > > from the
> > > receiver?
> >
> > Yes, it's talking about the peer. It works like this:
> >
> > conf-req produces: conf-ack/conf-nack/conf-req
> > conf-ack/conf-nack/conf-req produce new conf-req
> > repeat until nothing but conf-ack is returned
> > -Nathan
> 
> The server sends a conf-req and the client can reply with conf-ack. 
> Then the
> client sends a conf-req and the server can respond with a conf-nak. 
> Then the
> client sends another conf-req and if the server replies with a conf-
> ack the
> connection is established. Is that right?
> Why should the client respond with a conf-req? This is confusing. Is 
> it just
> that both (client and server) can handle their requests in parallel?

The client does not send a conf-req, ever. (more or less) It only 
replies to them, and the server modifies its conf-req each round until 
the client accepts them. Upon receipt of a conf-ack, the server assumes 
that those options are in effect. Upon transmission of one, the client 
does the same thing. conf-ack packets are *only* sent as the last step 
of the process.
-Nathan

--
Fortune Cookie Says:

"Well, if you can't believe what you read in a comic book, what *___can*
you believe?!"
                -- Bullwinkle J. Moose [Jay Ward]

Other related posts: