This is a follow-up to a remark I made about posts with problems that were
cured by using xonxoff. One of the people that posted this solution posted
another solution today: Set the asyncmap.
I wish I'd paid more attention to the symptoms, although they weren't what
I've come to expect as typical. But he also said that he failed to make a
good connection to a friend's ISP when he used copies of the friend's pppd
configuration files, even though the friend had the same make and model
modem and didn't have a problem. It's hard to understand how this could
have happened, in retrospect.
Asyncmap problems are almost always (I can't remember any that weren't.)
caused by a slightly broken ISP PPP implementation that doesn't use the
default ACCM (ffffffff) when the ACCM is not requested.
On Tue, 9 Feb 1999, Clifford Kite wrote:
|On Tue, 9 Feb 1999 [EMAIL PROTECTED] wrote:
|
||are there any known problems in using an Zyxel-omni.net external ISDN-TA?
|
|A probably unrelated comment: I've seen two posts recently both involving
|a Zyxel TA, both claimed to have a problem that was cured by using the pppd
|option xonxoff instead of crtscts. One of them believes it's a bug in
|ppp-2.3.5 because ppp-2.2.0 worked with the Zyxel and crtscts. But a
|friend of his with the same Zyxel model and ppp-2.3.5 didn't have the
|problem, so that conjecture is rather doubtful. The problem was not that
|the Zyxel didn't respond, it was that nothing got through from the Internet
|after making the connection.
---
Clifford Kite Not a guru. (tm)
[EMAIL PROTECTED] Not even close.
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
