• mgetty issue, waiting for '_'

    From Nick Young@21:4/145 to All on Wed Mar 17 18:54:23 2021
    Hi All,

    Hoping someone on here knows something about mgetty because I can't find the answer online...

    Here's a paste of my log:

    03/17 18:49:25 SB0 send: ATA[0d]
    03/17 18:49:25 SB0 waiting for ``CONNECT''
    03/17 18:49:25 SB0 got: [0a]
    03/17 18:49:25 SB0 CND: OKATA[0d]
    03/17 18:49:25 SB0 CND: ATA[0d][0a]CONNECT ** found **
    03/17 18:49:36 SB0 send:
    03/17 18:49:36 SB0 waiting for ``_''
    03/17 18:49:36 SB0 got: 33600/ARQ[0d]
    03/17 18:49:36 SB0 CND: CONNECT 33600/ARQ
    03/17 18:49:36 SB0 CND: found: 33600/ARQ[0a] ** found **
    03/17 18:49:36 SB0 waiting for line to clear (VTIME=3), read:
    03/17 18:49:36 SB0 looking for utmp entry... (PID: 2347)
    03/17 18:49:36 SB0 no utmp/wtmp entry, expect issues
    03/17 18:49:37 SB0 tio_set_flow_control( HARD )
    03/17 18:49:37 SB0 print welcome banner (/etc/issue.mgetty)
    03/17 18:49:37 SB0 getlogname (FIDO AUTO_PPP), read:
    03/17 18:49:42 SB0 select returned 0<*>
    03/17 18:49:47 SB0 select returned 0<*>
    03/17 18:49:52 SB0 select returned 0<*>
    03/17 18:49:57 SB0 select returned 0<*>

    Sorry about the length, but it is important that you see the "send: ATA[0d]". Cool, the modem answers and it finds the 'CONNECT' string. But all it does is print those "select returned 0<*>" and then times out with the error "03/17 18:22:10 SB0 timeout in chat script, waiting for `_'".

    What the hell is this "waiting for ``_''". Anyone know anything at all? Could it be an 'answer-chat' thing?


    ANY help appreciated!!


    Nick
    --- SBBSecho 3.13-Linux
    * Origin: TFSI - tfsi.synchronetbbs.org (21:4/145)
  • From Spectre@21:1/101 to Nick Young on Thu Mar 18 12:08:48 2021
    Well I did reply, but its stuck at TLP with some weird FD issues, no traffic
    in or out at the moment. Short answer waiting for '_' is part of a script where its waiting for a username/password that it would then forward to login which is normal. Only other thing I've come across is mention that it
    doesn't play well with PAM authentication.

    Spec

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Spectre@21:3/101 to Nick Young on Thu Mar 18 07:46:00 2021
    03/17 18:49:36 SB0 send:
    03/17 18:49:36 SB0 waiting ``_''
    03/17 18:49:36 SB0 got: 33600/ARQ[0d]

    Would have to see your answer script. I've guessing you've got something odd ìin there, off hand. It shouldn't be looking for anything you haven't asked ìfor, might even just be a typo.

    Spec


    *** THE READER V4.50 [freeware]
    --- SuperBBS v1.17-3 (Eval)
    * Origin: Scrawled in haste at The Lower Planes (21:3/101)
  • From Spectre@21:3/101 to Nick Young on Thu Mar 18 08:12:00 2021
    If I read right in the following its looking for a username/password. Which ìit would then hand off to login. I have also seen references to it not ìbehaving very well with PAM authentication.

    Spec

    login.config

    This is where the PPP call is configured. After mgetty answers the incoming ìcall and decides what to do with it, we want it to pass the call onto the PPP ìdaemon. There are two choices for the PPP configuration, one is to place it ìin the PPP configuration files the other to place it in the mgetty's ì"login.config" file's PPP command line call. In this situation it is ìrequiring very specific incoming connection configurations that if placed in ìthe PPP configurations files would conflict with an outbound PPP connection. ìThe following line being added to mgetty's "login.config" file:

    /pppd -chap +pap 10.4.4.230:10.4.4.20 login auth debug proxyarp

    -chap +pap = pap is the method used for the making the ppp connectivity

    10.4.4.230:10.4.4.20 = the Local and Remote IP addresses that will be ìallocated during the connection. These are very different from those used ìinside the Private Network, which would be in the range 192.168.1.x

    login auth = this installation is using the Local Linux user accounts to ìperform the username / password authentication against. Before that occurs ìthe username has to also be found in PPP pap-secrects configuration file, ìmore on that later.

    another line in mgetty's login.config file not documented very often, is to ìchange the last line from:
    * - - /bin/login @

    to the following:
    * - - /bin/false

    This stops dead any logons that are not strickly "AutoPPP". If the ì"issue-file" and "login-prompt" are not implented as described earlier, test ìmethod will produce a logon prompt, however after the username is entered the ìcall is disconnected.


    *** THE READER V4.50 [freeware]
    --- SuperBBS v1.17-3 (Eval)
    * Origin: Scrawled in haste at The Lower Planes (21:3/101)