From: Gert Doering <gert@greenie.muc.de>

You can't get a ppp connection going. So, what should you check before
calling for help in the list.

Run mgetty with a debug level high enough to see what login it will
try. It might not be wrong to just use level 9 to see everything
happening.

Scenario 1: mgetty recognizes AutoPPP:
  03/11 12:06:31 yS1   match: user='/AutoPPP/', key='/AutoPPP/'*** hit!
  03/11 12:06:31 yS1   login: utmp entry: ppp
  03/11 12:06:31 yS1    looking for utmp entry... (my PID: 5313)
  03/11 12:06:31 yS1   utmp + wtmp entry made
  03/11 12:06:31 yS1   calling login: cmd='/usr/sbin/pppd', argv[]='pppd...
  03/11 12:06:31 ##### data dev=ttyS1, pid=5313, caller=none, conn='LAPM', name=''
At this point, mgetty executes pppd and has nothing to do with
connection failures, failing authorization, the police banging at your
door or anything else. Check pppd's logs for any trouble.

If you use "who" and the only thing you can see is "a_ppp", go check
your pppd sources. It's pppd's job to forge a utmp entry

It looks like some unix clients should explicitely send the string
"/AutoPPP/" as there seems to be a problem in connecting. Mgetty
doesn't seem to get ppp-frames and waits for something it can decide
what to do. As you are most probably using a script for the
connection, there should be no problem to send that string.