> I think I've almost got them working because they pass the LCP request - ack
> stage and enter the IPCP stage. In the IPCP stage, my IPCP-Req is Ack'd, so
> I'm halfway there. Their IPCP-Req is received by me with IP-addr=0.0.0.0
> and I respond with IPCP-Nak IP-addr=192.168.20.50. All this seems correct
> to me, but then the device doesn't accept my Nak and either re-sends its
> original IPCP-Req or goes back to the LCP-Req stage.
The peer is free to ignore your suggested IP address for any reason it
wants. You cannot make it accept an address that it doesn't want.
Assuming you can't get debug logs out of the peer (in order to find
out why it doesn't like that address), I think the only thing you
could do would be to refuse to negotiate the addresses by adding
... as does this. Are you sure that the underlying link works and is
relatively error-free? Excessive frame loss could _easily_ be the
cause of the kind of problem you're seeing. It can lead to