Hi, I believe it is a modem programming problem. On the modem I use the following AT commands are associated with hangup or RTS. Check your modem manual as they vary between different modems. AT&D3 - DTR options - This controls forced hangup AT&K3 - flow control AT&R1 - RTS/CTS options S38 register - Delay before forced hangup I would examine the above AT commands and try these options in the chat script or initialisation string or set them as default (AT&V0) I hope this helps. Regards, Graham Smith ---------------------------------------------------- On 23-Mar-2000 Brevsville Administrator wrote:
I posted this the other day but didn't get a single comment.
Suse 6.3 running as a PPP server. The user dials in fine and can use the system for as long as they like. The problem occurs when they hang up, rts stays low which means when the next user dials in, the modem will answer but cannot receive any authentication, since with rts low the modem won't receive.
There must be a way to force rts to go high, since if when rts is still low, I start minicom, it raises rts and works fine. When I exit minicom rts goes low again so clearly this rts is not stuck, it is just being left low by pppd.
I know it is not the modem since I have tried 3 different modems (and cables) and each exhibit the same problem, also I use the same modems on another unix system and all works correctly.
The init-chat is sending a rest to the modem so I know it is in good shape, also switching off the modem and back on again in 30secs does not raise rts, hence it is safe to say the operating system is on some way holding rts low.
init q, init 1, then init 2 or 3 do not fix the problem, only a reboot fixes it.
Anyone have any ideas where next I should look?
Thanx
Chris
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/