On Sat, 10 Jul 1999, John Logsdon wrote:
|The system will dial OK, negotiate dynamic IPs etc but I can't ping
|anything remote *even* by IP numbers, let alone pull my mail etc. I can
|ping the local (dynamic) IP number until the line drops out. Since it
|returns the dynamic IP number, I presume the logon procedure has gone OK
|(I note that 2.3.x ppp requires you to have at least a * for the IP
|numbers in the pap-secrets and chap-secrets files).
|
|The options file is:
|
|lock
|defaultroute
|noipdefault
|modem
|/dev/modem
|115200
|crtscts
|debug
|passive
|name "j.logsdon"
I'd try adding the option "asyncmap 0" and if that didn't work then try
"asyncmap a0000" or match what the ISP requests, found in the pppd debug
log messages. You show RX errors in the new setup's ifconfig output and an
ISP with a broken PPP implementation could be sending data without all the
control characters escaped. There seem to be a lot of ISPs with this
particular PPP fracture.
I think that ppp-2.2.0 defaulted to "asyncmap 0" to negotiate the ACCM
while ppp-2.3.5 uses the initial link negotiation default ACCM (ffffffff)
and uses it - without negotiation - if there is no asyncmap specified. You
could also get the latest, ppp-2.3.8, which is back to negotiating with
"asyncmap 0" when no asyncmap is specified.
If that doesn't help you'll likely need to send us pppd debug log messages
to look at.
The routing and the interface configuration looked OK.
---
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]
