[plug] pppd

[Dean Wright]

Garth,

Sorry it took so long to get back to you.

I have finally tracked down my reference to 'ppp_log', in the debugging ppp
section of the ppp-howto it says to enter the line below in the sysconfig
file,

'daemon.*            /var/log/ppp_log'

so I did, but I forgot to write that down in my list of things that I've
done, which is why it took me so long to find it.

as for the messages file, I invoked pppd twice once from the command line
and the other with my win98 dialup.

the messages seemed to only record the command line effort, as seen here

Oct 31 14:21:37 ScoutCom1 pppd[600]: pppd 2.3.7 started by root, uid 0
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set dbg flags to 10000
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set flags to 10000
Oct 31 14:21:37 ScoutCom1 kernel: ppp_tty_ioctl: set xasyncmap
Oct 31 14:21:37 ScoutCom1 kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set flags to 10000
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set mru to 5dc
Oct 31 14:21:37 ScoutCom1 kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Oct 31 14:21:37 ScoutCom1 pppd[600]: Using interface ppp0
Oct 31 14:21:37 ScoutCom1 pppd[600]: Connect: ppp0 <--> /dev/ttyp0
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set flags to 10000
Oct 31 14:22:27 ScoutCom1 pppd[600]: Hangup (SIGHUP)
Oct 31 14:22:27 ScoutCom1 pppd[600]: Modem hangup
Oct 31 14:22:27 ScoutCom1 pppd[600]: Connection terminated.
Oct 31 14:22:27 ScoutCom1 pppd[600]: Connect time 0.9 minutes.
Oct 31 14:22:27 ScoutCom1 pppd[600]: Exit.
Oct 31 14:22:27 ScoutCom1 kernel: ppp: channel ppp0 closing.


that is everthing in messages at the time's I started pppd and here is
what's in the ppp_log file

Oct 31 14:21:37 ScoutCom1 pppd[600]: pppd 2.3.7 started by root, uid 0
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set dbg flags to 10000
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set flags to 10000
Oct 31 14:21:37 ScoutCom1 kernel: ppp_tty_ioctl: set xasyncmap
Oct 31 14:21:37 ScoutCom1 kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set flags to 10000
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set mru to 5dc
Oct 31 14:21:37 ScoutCom1 kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Oct 31 14:21:37 ScoutCom1 pppd[600]: Using interface ppp0
Oct 31 14:21:37 ScoutCom1 pppd[600]: Connect: ppp0 <--> /dev/ttyp0
Oct 31 14:21:37 ScoutCom1 pppd[600]: Warning - secret file
/etc/ppp/pap-secrets has world and/or group access
Oct 31 14:21:37 ScoutCom1 pppd[600]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<auth pap> <magic 0x58915136> <pcomp> <accomp>]
Oct 31 14:21:37 ScoutCom1 kernel: ppp_ioctl: set flags to 10000
Oct 31 14:21:40 ScoutCom1 pppd[600]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<auth pap> <magic 0x58915136> <pcomp> <accomp>]
Oct 31 14:22:05 ScoutCom1 last message repeated 8 times
Oct 31 14:22:08 ScoutCom1 pppd[600]: LCP: timeout sending Config-Requests
Oct 31 14:22:27 ScoutCom1 pppd[600]: Hangup (SIGHUP)
Oct 31 14:22:27 ScoutCom1 pppd[600]: Modem hangup
Oct 31 14:22:27 ScoutCom1 pppd[600]: Connection terminated.
Oct 31 14:22:27 ScoutCom1 pppd[600]: Connect time 0.9 minutes.
Oct 31 14:22:27 ScoutCom1 pppd[600]: Exit.
Oct 31 14:22:27 ScoutCom1 kernel: ppp: channel ppp0 closing.
Oct 31 14:22:27 ScoutCom1 kernel: ppp0 released
Oct 31 14:22:27 ScoutCom1 kernel: ppp0: ccp closed

and in my mgetty.ttyS0 file it had this

--
10/31 14:28:09 ##### failed timeout dev=ttyS0, pid=271, caller='none',
conn='', name=''

--
10/31 14:29:15 ##### data dev=ttyS0, pid=614, caller='none', conn='38400',
name='', cmd='/bin/login', user='/AutoPPP/'

--
10/31 14:30:09 yS0  init chat failed, exiting...: Invalid argument
10/31 14:30:09 ##### failed in mg_init_data, dev=ttyS0, pid=617


I am logged into linux with root only
and there was no other reference in other files in the /var/log directory
for anything around the time I ran ppp.


Dean




> Hi Dean
>
> The entry in the mgetty log file that refers to user='/AutoPPP/' is the
> correct response by mgetty. This means that mgetty attempted to start
> pppd in answer to that particular phone call. I am a bit concerned that
> you are not seeing any log activity in /var/log/messages from pppd. Did
> you see some logged messages in that file when you started pppd from the
> command line?
>
> For the login feature to work with pppd the user dean with a password of
> dean must exit on the linux system you are calling.
>
> Your question about having a ppp user in /etc/passwd relate to you
> wanting non-root users to be able to run pppd. This is not required at
> the moment, and maybe will never be. It certainly isnt causing your
> current problems.
>
> Right now it seems that mgetty is doing the right thing (at least once
> anyway) and pppd is failing. To debug this setup further you must be
> able to monitor pppd status messages. Is there a chance that your
> /var/log/messages is not being updated at all, or that pppd is logging
> to a different file? Check the /var/log directory for other files maybe.
>
> Whats your reference to ppp_log?
>
> Garth
>
> Dean Wright wrote:
> >
> > Garth,
> >
> > Below is what I had in my mgetty.tty.S0 file after I tried to dial in,
it
> > only logged the first time I tried, I also dialed in at around 11:30 but
as
> > you can see it didn't put anything in here about that.
> >
> > I have in my pap-secrets file "dean * dean"
> >
> > in the entry for 10/31 10:58:56 it has user='CONNECT 38400' does this
mean
> > that my win98 dialup is passing 'CONNECT 38400' when pap is expecting
dean.
> >
> > here is my mgetty.ttyS0 file:
> >
> > 10/31 10:49:39 ##### failed dev=ttyS0, pid=242, got signal 15, exiting
> >
> > --
> > 10/31 10:58:56 ##### data dev=ttyS0, pid=129, caller='none',
conn='38400',
> > name='', cmd='/bin/login', user='CONNECT 38400'
> >
> > --
> > 10/31 10:59:35 yS0  init chat failed, exiting...: Invalid argument
> > 10/31 10:59:35 ##### failed in mg_init_data, dev=ttyS0, pid=143
> >
> > --
> > 10/31 11:01:16 ##### failed A_FAIL dev=ttyS0, pid=144, caller='none',
> > conn='', name=''
> >
> > --
> > 10/31 11:01:48 ##### data dev=ttyS0, pid=147, caller='none',
conn='38400',
> > name='', cmd='/bin/login', user='/AutoPPP/'
> >
> > --
> > 10/31 11:02:26 yS0  init chat failed, exiting...: Invalid argument
> > 10/31 11:02:26 ##### failed in mg_init_data, dev=ttyS0, pid=148
> >
> > as for messages and ppp_log there was nothing entered at the times I
tried
> > dialing.
> >
> > I was reading that for pppd configuring I should have an entry in the
passwd
> > file for a ppp group is this relevant for my current setup, I have added
the
> > user dean and this is in there.
> >
> > I was under the impression that pap will allow the remote login if the
user
> > is a valid user of that machine.
> >
> > thanks for your help
> > Dean
>