dialup and extended info,
Gert Doering (gert@greenie.muc.de)
Mon, 17 May 1999 09:14:09 +0200
Hi,
On Mon, May 17, 1999 at 09:15:40AM -0900, Greg wrote:
> 05/17 04:56:21 yS1 send: ATA[0d]
> 05/17 04:56:21 yS1 waiting for ``CONNECT''
> 05/17 04:56:21 yS1 got: ATA[0d]
> 05/17 04:56:21 yS1 CND: OKATA[0d][0a]CARRIER 33600[0d]
> 05/17 04:56:34 yS1 CND: CARRIER 33600
> 05/17 04:56:34 yS1 CND: found: 33600[0a][0d][0a]PROTOCOL:
> LAP-M[0d]
> 05/17 04:56:34 yS1 CND: PROTOCOL: LAP-M
> 05/17 04:56:34 yS1 CND: found: LAP-M[0a][0d][0a]CONNECT **
> found **
> 05/17 04:56:34 yS1 send:
> 05/17 04:56:34 yS1 waiting for ``_''
> 05/17 04:56:34 yS1 got: 57600[0d]
> 05/17 04:56:34 yS1 CND: CONNECT 57600
ok, this is how it should look like - there are some CARRIER / PROTOCOL /
... messages, and then the CONNECT string.
> 05/17 04:56:35 yS1 getlogname (no opts), read:[0a]
> 05/17 04:56:35 yS1 tio_set_flow_control( HARD )
> 05/17 04:56:35 yS1 print welcome banner (/etc/issue)
> 05/17 04:56:35 yS1 getlogname (no opts), read:PROTOCOL:
> LAP-M[0d]
But this is very weird. AFTER the CONNECT, there is yet another
"PROTOCOL:" message - which mgetty interprets as login name, because there
MUST NOT be any further message after CONNECT.
There could be two reasons for that:
- the client side (caller) is echoing some messages back to the modem,
and thus their "PROTOCOL" message is coming back to you. Try with a
different client modem and client software.
- your modem is very braindead. Try going into "minicom", waiting for
an incoming call, send ATA, and look what happens. There should not
be any message after "CONNECT" (except what the user at the calling
side is typing).
- something very weird is going on - try different modems at both ends,
different serial cables, different serial ports, etc.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert@greenie.muc.de
fax: +49-89-35655025 gert.doering@physik.tu-muenchen.de