On Tue, 9 Feb 1999 [EMAIL PROTECTED] wrote:
|are there any known problems in using an Zyxel-omni.net external ISDN-TA?
|i use a Suse 6.0 with Kernel 2.066 and the ppp 2.35. when i use a modem i do
|not have any probs, only the TA does make
|probs, because it does not response to the chatscript, i tested the script
|with minicom and it does not have any problems,
|when try to use it with ppp, the modem does not response to any AT-Command.
The modem not responding sounds like the port that is configured for Linux
isn't the one actually uses by the modem. Configuration is usually done in
one of the boot files in /etc/rc.* by setserial. DOS/MSWin to Linux port
mapping is com1=/dev/ttyS0, com2=/dev/ttyS1, ect. If minicom works though,
then you likely have the chat script configured correctly so this may not
help. You could check the minicom options for the port with Alt-o, select
Serial port setup, A - Serial device.
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.
----------------------------------------------------------------------------
"You're one of those condescending Unix computer users!"
"Here's a nickel, kid. Get yourself a better computer" - Dilbert.
----------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
