Re: IPCP Negotiation Failure

amyng wrote:
> Apology if this is not the correct forum, but I'm on my last straw.
>
It's not, unless a serious bug in the specification.  But we sometimes
help each other a bit....


> I'm running 2.4.4 pppd on Solaris trying to connect to a device (which I can
> get to by window rasppp btw).
>
What device?


> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0>]
> rcvd [IPCP ConfReq id=0x10 <addr 192.168.129.1>]
> sent [IPCP ConfAck id=0x10 <addr 192.168.129.1>]
> rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01> <addr 0.0.0.0>]


> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.129.2>]
> rcvd [IPCP ConfReq id=0x11 <addr 192.168.129.1>]
> sent [IPCP ConfAck id=0x11 <addr 192.168.129.1>]
> rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01> <addr 192.168.129.2>]


> I have an output of a successful ppp connection from the same pppd connected
> to a similar device using the same options:

Again, what device?


> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.129.2>]
> rcvd [IPCP ConfReq id=0x3 <addr 192.168.129.1>]
> sent [IPCP ConfAck id=0x3 <addr 192.168.129.1>]
> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.129.2>]
> rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]

Remember, ConfReject means the device doesn't implement the option.

The former rejects both header compression and IP addresses.

The latter rejects only header compression.  So, it must be a different
device, as it seems to have the IP option implemented.

Or the two devices are differently configured, assuming they can be
configured to pretend they don't implement an option.

The difficulty is the peer, not Solaris.

_______________________________________________
Pppext mailing list
Pppext@...
https://www1.ietf.org/mailman/listinfo/pppext