Problems Getting pppd to Start

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

John Bell <jbell@sanderson.net.my> wrote:
> (Unix PAP or CHAP, and NT with MSchap80) dial out serial (via cu) and dial in 

no. If you have mgetty on /dev/ttyS0, you must dial out on /dev/ttyS0.

BTW, /dev/cua* devices are now obsolete anyway in Linux.

> (or later) it appears that even though mgetty recognises the ppp frames it is 
> unable to launch ppp.  The basis for this statement is that ppp does not log 
> its start up message via syslog.  Naturally pppd is world executable and suid 

Can you show

> port-owner uucp
> port-group uucp
> port-mode 0664

0660 would be better

> Feb 23 14:08:54 sultan mgetty[2904]: data dev=modem, pid=2904, caller=none, 
> conn='38400', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

nice


> 02/23 14:08:54 dem   setenv: 'CALLER_ID=none'
> 02/23 14:08:54 dem   setenv: 'CONNECT=38400'
> --
> 02/23 14:08:55 dem  mgetty: experimental test release 1.1.5-Apr16

pppd is presumably exiting immediately, because of kernel not compiled
with PPP support, unmatching PPP versions, missing configuration file,
etc.

What happens if you launch the *exact same* command line as specified
in the /AutoPPP/ configuration from a root-xterm ?

If you do not get PPP frames, you will certainly get a very precize
error message.