On Mon, 20 Sep 1999, Thomas J Pinkl wrote:

|Clifford Kite wrote:
|> 
|> On Fri, 17 Sep 1999, Thomas J Pinkl wrote:
|> 
|> |    rcvd [IPCP ConfReq id=0x7 <compress VJ 0f 01> <addr 10.0.0.21>]
|> |    sent [IPCP ConfNak id=0x7 <addr 10.1.0.5>]
|> |    rcvd [IPCP ConfReq id=0x8 <compress VJ 0f 01> <addr 10.0.0.21>]
|> |    sent [IPCP ConfRej id=0x8 <addr 10.0.0.21>]
|> |    rcvd [IPCP ConfReq id=0x9 <compress VJ 0f 01>]
|> |    sent [IPCP ConfAck id=0x9 <compress VJ 0f 01>]
|> |    local  IP address 10.1.0.6
|> |    remote IP address 10.1.0.5
|> |
|> |The remote address, 10.1.0.5, is never Ack'd.  Yet pppd proceeds as if 
|> |everything is fine.  Of course, I cannot send packets to 10.1.0.5.
|> 
|> If you want to accept the IP address that the peer wants then use the pppd
|> option ipcp-accept-remote .  Otherwise I can't see anything wrong, the
|> remote proposed not negotiating IP addresses and pppd agreed.  You can't
|> force the peer to use an IP address that it doesn't want to use. 
|
|I definitely do not want to accept the remote's address.
|
|If my pppd and the peer cannot agree upon an IP address, why is the 
|link established?  What would be the point?

That's a question better asked on comp.protocols.ppp and is one that I
can't answer fully.  The peer did offer IPCP without the IP-address option
and one reason it might do this is when the peer wants IPCP to reach the
Open state so as to be able to terminate IPCP.  This doesn't seem to be the
case here since no IPCP Terminate request from the peer was forthcoming. 
There may be other reasons I don't know about though.

|I don't want to force a mis-configured peer to use my IP address.  
|However, since an IP address couldn't be negotiated, I would expect pppd 
|to fail the connection attempt and not establish a ppp# interface.

I've sometimes asked ISP peers to use a reserved IP address as the remote
IP address, e.g. 192.168.0.2, and the peers were agreeable.  They didn't
offer to complete the IPCP negotiation with *no* remote address, they
accepted the reserved IP address and the connection worked perfectly.  Good
PPP implementations will allow both local and remote IP addresses to be
configured, and can be configured to allow a peer to choose (within limits)
what it uses as the remote IP address at it's end of the connection. 

---
Clifford Kite                                               Not a guru. (tm)





-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]

Reply via email to