On Wed, 20 Oct 1999, Richard B. Johnson wrote:
|Oct 19 19:48:58 quark pppd[3266]: pppd 2.3.10 started by root, uid 0
|Oct 19 19:48:58 quark pppd[3266]: Using interface ppp0
|Oct 19 19:48:58 quark pppd[3266]: Connect: ppp0 <--> /dev/ttyS0
|Oct 19 19:48:58 quark pppd[3266]: found interface eth0 for proxy arp
|Oct 19 19:48:58 quark pppd[3266]: local IP address 204.178.40.236
|Oct 19 19:48:58 quark pppd[3266]: remote IP address 204.178.40.100
|Oct 19 19:48:58 quark pppd[3266]: IPCP terminated by peer
| (Unauthorized remote IP address)
|Oct 19 19:48:58 quark pppd[3266]: LCP terminated by peer
| (No network protocols running)
The problem isn't the new pppd on your box (if I understand where this is
coming from). Pppd offers the addresses to the peer and the peer won't
accept the address 204.178.40.236 as pppd's IP address. There's nothing
that pppd can do about that.
If the 2.3.10 pppd was installed at the workplace box and the only
authentication is login/password on callback then add the pppd option
"noauth" to that box. The reason for the behavior is found in the
explanation of the "auth" option in man pppd (authentication means PAP or
CHAP there since login/password is outside the PPP specification).
---
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]
