On Sat, 5 Feb 2000, vuqpham wrote:
|I am using ppp 2.3.11 on Caldera 2.3 About 50% of connection it give me
|error of "could not determine remote IP address". I enclose the log file.
|If I connect to the same isp by Windows NT, it is ok.
[snip]
[CCP negotiations stripped from the log below for clarity]
|Feb 5 23:31:18 bighope pppd[1026]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0>
|<compress VJ 0f 01>]
You request that the ISP supply an IP address for the PPP link by sending
0.0.0.0. This is the standard way to ask the other side of the connection
to provide the IP address that your side can use.
|Feb 5 23:31:18 bighope pppd[1026]: rcvd [IPCP ConfReq id=0x3 <addr
|0.0.0.0>]
Ugh! The ISP requests that *you* provide an address that *it* can use for
the PPP link.
|Feb 5 23:31:18 bighope pppd[1026]: sent [IPCP ConfRej id=0x3 <addr
|0.0.0.0>]
Pppd doesn't have an IP address for the ISP and so rejects the 0.0.0.0. If
it had an IP address it would have sent a configure-nak with that address.
|Feb 5 23:31:18 bighope pppd[1026]: rcvd [IPCP ConfRej id=0x1 <compress VJ
|0f 01>]
|Feb 5 23:31:18 bighope pppd[1026]: sent [IPCP ConfReq id=0x2 <addr
|0.0.0.0>]
Pppd tries again to get an IP address to use for the PPP connection.
|Feb 5 23:31:18 bighope pppd[1026]: rcvd [IPCP ConfReq id=0x5 <addrs 0.0.0.0
|192.168.2.122>]
The ISP uses an outdated option in hopes of getting an IP address. Note
the difference: "addrs" as opposed to "addr" .
|Feb 5 23:31:18 bighope pppd[1026]: sent [IPCP ConfRej id=0x5 <addrs 0.0.0.0
|192.168.2.122>]
The 0.0.0.0 is still a request that pppd supply the IP address for the ISP
again and causes pppd to reject this too.
|Feb 5 23:31:18 bighope pppd[1026]: rcvd [IPCP ConfNak id=0x2 <addr
|192.168.2.122>]
The ISP Naks the 0.0.0.0 in the pppd request and provides an IP address,
which is what it's supposed to do. It's a private (non-routable) IP
address though, and if this works then the ISP has to be doing NAT. If
that is the case then the ISP is providing low quality PPP service.
|Feb 5 23:31:18 bighope pppd[1026]: sent [IPCP ConfReq id=0x3 <addr
|192.168.2.122>]
Here pppd requests the IP address that was provided by the ISP in the
configure-nak.
|Feb 5 23:31:18 bighope pppd[1026]: rcvd [IPCP ConfReq id=0x7]
|Feb 5 23:31:18 bighope pppd[1026]: sent [IPCP ConfAck id=0x7]
Pppd and the ISP agree that the ISP won't negotiate an address for the ISP
to use for the PPP link. :(
|Feb 5 23:31:18 bighope pppd[1026]: rcvd [IPCP ConfAck id=0x3 <addr
|192.168.2.122>]
The ISP Acks the pppd request for the IP address that the ISP supplied in
the earlier Nak.
|Feb 5 23:31:18 bighope pppd[1026]: Could not determine remote IP address
|Feb 5 23:31:18 bighope pppd[1026]: sent [IPCP TermReq id=0x4 "Could not
|determine remote IP address"]
Pppd realizes there's no hope and sends a IPCP terminate-request.
|Feb 5 23:31:19 bighope pppd[1026]: rcvd [IPCP TermAck id=0x4]
|Feb 5 23:31:19 bighope pppd[1026]: sent [LCP TermReq id=0x2 "No network
|protocols running"]
And then, properly, terminates the LCP negotiations and thus the
connection.
|Feb 5 23:31:19 bighope pppd[1026]: rcvd [LCP TermAck id=0x2]
|Feb 5 23:31:19 bighope pppd[1026]: Connection terminated.
What to do? You can *try* specifying an IP address for the ISP to use for
the pppd connection by using the pppd option to specify IP addresses. For
example, using " 192.168.0.1: " lets pppd offer the (private) IP address
192.168.0.1 for the ISP to use for the connection and also ask the ISP to
supply an IP address that pppd can use for the connection.
Since you said that NT could connect with no problem this may what it does
to get the connection to work. This should work *provided* the private IP
address that the ISP gave you for the connected is NATed at the ISP.
---
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]
