Having turned on debugging, here is the output of my log file: 6/04 14:01:35 yS0 mgetty: experimental test release 1.1.27-Oct21 06/04 14:01:35 yS0 check for lockfiles 06/04 14:01:35 yS0 locking the line 06/04 14:01:35 yS0 lowering DTR to reset Modem 06/04 14:01:36 yS0 send: \dATQ0V1H0[0d] 06/04 14:01:36 yS0 waiting for ``OK'' ** found ** 06/04 14:01:37 yS0 send: AT[0d] 06/04 14:01:37 yS0 waiting for ``OK'' ** found ** 06/04 14:01:37 yS0 waiting... 06/04 15:01:37 yS0 checking if modem is still alive 06/04 15:01:37 yS0 mdm_send: 'AT' -> OK 06/04 15:01:37 yS0 waiting... 06/04 16:01:37 yS0 checking if modem is still alive 06/04 16:01:37 yS0 mdm_send: 'AT' -> OK 06/04 16:01:38 yS0 waiting... 06/04 16:30:33 yS0 wfr: waiting for ``RING'' 06/04 16:30:33 yS0 send: ATA[0d] 06/04 16:30:33 yS0 waiting for ``CONNECT'' ** found **06/04 16:30:45 yS0 send: 06/04 16:30:45 yS0 waiting for ``_'' ** found **
06/04 16:30:46 ##### data dev=ttyS0, pid=18440, caller='none', conn='19200/ARQ/V34/LAPM/V42BIS', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/' -- 06/04 16:30:46 yS0 mgetty: experimental test release 1.1.27-Oct21 06/04 16:30:46 yS0 check for lockfiles 06/04 16:30:46 yS0 locking the line 06/04 16:30:46 yS0 lowering DTR to reset Modem 06/04 16:30:47 yS0 send: \dATQ0V1H0[0d] 06/04 16:30:47 yS0 waiting for ``OK'' ** found ** 06/04 16:30:48 yS0 send: AT[0d] 06/04 16:30:48 yS0 waiting for ``OK'' ** found ** 06/04 16:30:48 yS0 waiting...
How? The contents of the relevant log file /var/log/mgetty/mg_ttyS0.log should give a clue. (Apologies if you have looked already) Authorisation should be done by pppd in your case (I assume that you don't want people to use mgetty's login prompt). Does mgetty recognise dial-in attempts as PPP connections?If it does, then you should be able to get more clues by adding debugto /etc/ppp/options.server and study /var/log/syslog (depending on your syslogd config). The pppd debug should tell you what is going on.Could the problem have to do with permissions to the port?Probably not, as mgetty will run as root...Maybe mgetty can't assign it an IP due to permissions?Long answer: IP addresses are assigned by pppd; mgetty merely answers the phone and starts up pppd. Besides, the TCP/IP layer of the connection will only be brought up once the two sides have successfully authenticated each other. If things go wrong before authentification, then IP addresses are irrelevant. Short answer: No.
--To UNSUBSCRIBE, email to debian-user-request@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org