HI!!!
> On Mon, 28 Oct 1996 19:18:06 -0800 (PST), you wrote:
> >No, the PM is saying that the *remote's* address is 206.100.84.7.
>
> I've got to admit I'm a little puzzled by this.
Join the crowd. It took me awhile and I'm still not sure about it.
> I always thought that the PM assigned the client's IP addr with
> the value in an IPCP NAK of it's IP address option.
Only if the remote attempted to specific what it wanted as an IP address
in an IPCP request packet.
> Below is an (abridged) example of what takes place when
> I connect. Can you help me understand where I'm going wrong?
I'll try. Hopiefully I'`ll have it correct.
> >Sending IPCP_CONFIGURE_REQUEST to port S20 of 16 bytes containing:
> >01 01 00 10 02 06 00 2d 0f 00 03 06 ce a8 12 f1
> Sent to port S20: 18 bytes IPCP Request-1
> IP Comp Proto = Van Jacobson 15 0
> IP Address = 206.168.18.241
>
> Are you saying that the PM wants me to take 206.168.18.1?
> As far as I know this is the IP address of my ISP's PM.
Typo, I think. The PM is sending an IPCP request telling the remote that
it should be the IP address 206.168.18.241, not 206.168.18.1.
> >Received IPCP_CONFIGURE_REQUEST on port S20 of 36 bytes containing:
> >01 01 00 28 02 06 00 2d 0f 01 03 06 00 00 00 00
> >81 06 00 00 00 00 82 06 00 00 00 00 83 06 00 00
> >00 00 84 06 00 00 00 00
> Fixed #bytes to match #found...
> Recvd from port S20: 42 bytes IPCP Request-1
> IP Comp Proto = Van Jacobson 15 1
> IP Address = 0.0.0.0
> Pri DNS = 0.0.0.0
> Pri Netbios NS = 0.0.0.0
> Sec DNS = 0.0.0.0
> Secy Netbios NS = 0.0.0.0
>
> I had always taken it that by announcing 0's the client was making
> a request for assignment.
I think you are right about the 0's for the 80's options. I've haven't
considered what a 0's request for the IP address means. I tend to think
that a 0's request fo an IP addrress is nonsense. (I'll admit I'm biased
here, I think A LOT of what M$ does is nonsense.)
> >Received IPCP_CONFIGURE_ACK on port S20 of 12 bytes containing:
> >02 01 00 10 02 06 00 2d 0f 00 03 06 ce a8 12 f1
> Fixed #bytes to match #found...
> Recvd from port S20: 18 bytes IPCP Accept-1
> IP Comp Proto = Van Jacobson 15 0
> IP Address = 206.168.18.241
>
> I thought that this was the client agreeing the the PM knew who it was.
No, this is the client/remote agreeing that it will use the IP address
206.168.18.241.
> >Sending IPCP_CONFIGURE_NAK to port S20 of 16 bytes containing:
> >03 04 00 10 03 06 ce a8 12 86 81 06 ce a8 12 01
> Sent to port S20: 18 bytes IPCP Refuse-4
> IP Address = 206.168.18.134
> Pri DNS = 206.168.18.1
>
> This is where I thought the PM assigns the IP address to the client.
> (the NAK meaning I might accept your req if it looked more like this).
> It does seem to be the address that I end up with (winipcfg).
The NAK packet is used to tell the client that in the same sequence number
request the following options have been refused/nak'd and these are the
values that the PM is suggesting to be used instead.
In this case the 0's IP address is replaced with the 206.168.18.134
address and the 0's primary dns entry is replaced with the actual dns
nameserver from the global setup.
> >Received IPCP_CONFIGURE_REQUEST on port S20 of 24 bytes containing:
> >01 05 00 1c 02 06 00 2d 0f 01 03 06 ce a8 12 86
> >81 06 ce a8 12 01 83 06 cc f8 a8 f0
> Fixed #bytes to match #found...
> Recvd from port S20: 30 bytes IPCP Request-5
> IP Comp Proto = Van Jacobson 15 1
> IP Address = 206.168.18.134
> Pri DNS = 206.168.18.1
> Sec DNS = 204.248.168.240
>
> Finally the client comes back with the converged set of options
> and values.....
>
>
> >Sending IPCP_CONFIGURE_ACK to port S20 of 28 bytes containing:
> >02 05 00 1c 02 06 00 2d 0f 01 03 06 ce a8 12 86
> >81 06 ce a8 12 01 83 06 cc f8 a8 f0
> Sent to port S20: 30 bytes IPCP Accept-5
> IP Comp Proto = Van Jacobson 15 1
> IP Address = 206.168.18.134
> Pri DNS = 206.168.18.1
> Sec DNS = 204.248.168.240
>
> And the PM approves!
Yes.
JGT
-- John G. Thompson Livingston Enterprises Inc. Phone: (800) 458-9966 JOAT(MON) 6920-220 Koll Centre Pkwy. Fax: (510) 426-8951 support@livingston.com Pleasanton, CA 94566 http://www.livingston.com