[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

mgetty: AutoPPP Failure



Hello Debianites,

I am struggling to get the AutoPPP feature of mgetty to work.
I want to connect two Debian Maschines running (mostly) Hamm.
In /etc/mgetty/login.config of the PPP-Server maschine I have tested
the following lines by uncommenting each in turn:

#/AutoPPP/ -  a_ppp  /usr/sbin/pppd auth -chap +pap login
#/AutoPPP/ -  @      /usr/sbin/pppd auth -chap -pap login
/AutoPPP/ -   @      /usr/sbin/pppd auth login +pap -chap modem crtscts proxya
rp lock

/etc/ppp/pap-secrets is set up to include:

# Every regular user can use PPP and has to use passwords from /etc/passwd
# Tested both:
#*      fliwatut        ""
*       192.168.0.1        ""   *

And the options file for the modem is /etc/ppp/options.ttyS0 includes:

# local-ip:remote-ip
#fliwatut.scifi.com:fliwatut.scifi.com-s0
198.162.0.1:198.162.0.50

to give the incoming connection an IP number

THE PROBLEM:
I tested this with a user called "eric" with password "secret" (just
kidding, in fact it was another PW). He called me (HOST: fliwatut) from
his debian maschine and mgetty took the call. His setup was done with
"pppconfig" and uses a simple PAP-authentification.

But a ppp connection could not be made. The reason showed in the ppp.log
file like this:

Feb  4 14:39:20 fliwatut pppd[1483]: pppd 2.3.5 started by /AutoPPP/, uid 0
Feb  4 14:39:20 fliwatut pppd[1483]: Using interface ppp0
Feb  4 14:39:20 fliwatut pppd[1483]: Connect: ppp0 <--> /dev/ttyS0
Feb  4 14:39:20 fliwatut pppd[1483]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <au
th pap> <magic 0xa040e69d> <pcomp> <accomp>]
[...]
Feb  4 14:39:23 fliwatut pppd[1483]: sent [LCP EchoReq id=0x0 magic=0xa040e69d]
Feb  4 14:39:23 fliwatut pppd[1483]: rcvd [PAP AuthReq id=0x1 user="eric" passwo
rd="secret"]
Feb  4 14:39:23 fliwatut pppd[1483]: PAP authentication failure for eric
Feb  4 14:39:23 fliwatut pppd[1483]: sent [PAP AuthNak id=0x1 "Login incorrect"]
Feb  4 14:39:23 fliwatut pppd[1483]: sent [LCP TermReq id=0x2 "Authentication fa
iled"]
Feb  4 14:39:23 fliwatut pppd[1483]: rcvd [LCP EchoRep id=0x0 magic=0xdf6]
Feb  4 14:39:23 fliwatut pppd[1483]: rcvd [LCP TermAck id=0x2]
Feb  4 14:39:23 fliwatut pppd[1483]: Connection terminated.
Feb  4 14:39:23 fliwatut pppd[1483]: Hangup (SIGHUP)
Feb  4 14:39:23 fliwatut pppd[1483]: Exit.

The accompanying mgetty logfile has:

02/04 14:39:18 yS0   getlogname (FIDO AUTO_PPP), read:~[ff]}#[c0]!
02/04 14:39:20 yS0   input finished with '\r', setting ICRNL ONLCR
02/04 14:39:20 yS0   tio_get_rs232_lines: status: RTS CTS DSR DTR DCD
02/04 14:39:20 yS0    login: use login config file /etc/mgetty/login.config
02/04 14:39:20 yS0   match: user='/AutoPPP/', key=''
02/04 14:39:20 yS0   match: user='/AutoPPP/', key=''
02/04 14:39:20 yS0   match: user='/AutoPPP/', key='/AutoPPP/'*** hit!
02/04 14:39:20 yS0   login: utmp entry: /AutoPPP/
02/04 14:39:20 yS0    looking for utmp entry... (my PID: 1483)
02/04 14:39:20 yS0   utmp + wtmp entry made
02/04 14:39:20 yS0   calling login: cmd='/usr/sbin/pppd', argv[]='pppd auth logi
n +pap -chap modem crtscts proxyarp lock'
02/04 14:39:20 ##### data dev=ttyS0, pid=1483, caller='none', conn='33600/LAPM/V
42BIS', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

02/04 14:39:20 yS0   setenv: 'CALLER_ID=none'
02/04 14:39:20 yS0   setenv: 'CONNECT=33600/LAPM/V42BIS'

Obviously pppd got started but athentification failed. I even added user
"eric" to group dip and dialout, just in case.

But what now? Did anybody here successfully set up a ppp server with
mgetty? Any tips where to look for mistakes?
Thank you very much in advance,
-- 
                                                     __    __
 Frank Barknecht           ____ ______   ____ __ trip\ \  / /wire ______
                          / __// __  /__/ __// // __  \ \/ /  __ \\  ___\	
                         / /  / ____/  / /  / // ____// /\ \\  ___\\____ \	
                        /_/  /_____/  /_/  /_//_____// /  \ \\_____\\_____\
                                                    /_/    \_\ 


Reply to: