[plug] pppd

[Dean Wright]

David,

I tried changing the options and syslog.conf as you said, then dialed in.

nothing was entered in both those files.

any ideas?

Dean



>
> PPPD debugging:
>
> ************************
>
> /etc/ppp/options
>
> *should contain:
>
> debug
> kdebug 4
>
> /etc/syslog.conf
>
> *should contain
>
> daemon.debug /var/log/daemon
> local2.debug /var/log/local2
>
> **************************
>
> All TCP/IP headers, LCP acks and everything will be logged to
> /var/log/daemon. A similar but condensed story will be logged to
> /var/log/messages. The particular logs you haev indicate to me that the
> init chats have failed. You will need to ensure that you can see EXACTLY
> what is being sent through and from to work out whose init chat has
> failed.
>
> An init chat failure has nothing to do with PAP or any other
> authentication. Most of the time UNIX or Linux systems will present
> login: and expect a user name. They'll then present passwrod: and expect
> a password. It looks like the login and expect pairs aren't working
> correctly.
>
> DAVID L
>
> 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
> >
> > > Hi Dean
> > >
> > > If the +pap option is used and the pap-secrets file is empty then pppd
> > > will silently fail (I dont even think it puts any message in
> > > /var/log/messages).
> > >
> > > In the pap-secrets file try:
> > > john * john
> > >
> > >
> > > Then using dialup networking in Windows 98, login as john with
password
> > > of john.
> > >
> > > Mgetty has a good log file to check as well. It is in the /var/log
> > > directory and is called something like mgetty.ttyS1 or mgetty.ttyS0
> > > (serial port 2 or serial port 1) or possibly mgetty.modem.
> > >
> > > In mgetty's log file you should confirm theat mgetty is detecting ppp
> > > packets and automatically launching pppd as a result.
> > >
> > > Also remove the -ip and lock parameters from /etc/ppp/options. In this
> > > scenario (at least during setup) they are not required.
> > >
> > > You can also, as a test of the pppd configuration, as superuser,
execute
> > > the pppd program with exactly the same parameters as in the
login.config
> > > file. You should see some very strange characters appear as output on
> > > your console, or see some pppd error message.
> > >
> > > Garth
> > >
> > > Dean Wright wrote:
> > > >
> > > > Garth,
> > > >
> > > > Thanks for the help, but I am still having prob's.
> > > >
> > > > here is what I have in my login.config file
> > > >
> > > > "pppd debug kdebug 1 192.168.10.10:192.168.10.11 +pap login asyncmap
0
> > > > passive"
> > > >
> > > > is that all I need in there?
> > > >
> > > > this is what I have setup in my options file
> > > >
> > > > asyncmap 0
> > > > crtscts
> > > > local
> > > > lock
> > > > modem
> > > > passive
> > > > -detach
> > > > -ip
> > > > +pap
> > > > debug
> > > > kdebug 1
> > > > login
> > > > lcp-echo-interval 30
> > > > lcp-echo-failure 4
> > > >
> > > > Are these right? I'm not sure.
> > > >
> > > > I dialed in with hyper terminal and I can login ok, but if I try to
use
> > > > dialup networking it gets to the verifying password point then waits
for
> > a
> > > > bit then I get disconnected. So I went and checked the messages and
> > ppp_log
> > > > files and there was only the info from when I restarted the box from
the
> > > > kernel, nothing from pppd.
> > > >
> > > > could my modem string be wrong?
> > > > or maybe my settings on the win98 dailup? which are
> > > >
> > > > type of dialup server: ppp
> > > > advanced options: enable software compression
> > > > protocols: TCP/IP with both server assigned addresses checked,
ipheader
> > > > compression, use default gateway.
> > > >
> > > > also I am not really sure what I need to have in my ppp-secrets file
> > > >
> > > > any ideas on what I am doing wrong (probably heaps)
> > > > please bare with me I'm still on that really steep learning curve
> > > >
> > > > Dean
> > > >
> > > > "Who told you to put the balm on? I didn't tell you to put the balm
on,
> > what
> > > > is a balm anyway?"
> > > > - Jackie Giles  (Seinfeld)
> > >
>
> --
> Subscribe to the Linux C Mailing Lists Today!
>   mailto:linuxCprogramming-subscribe at listbot.com
>   http://users.senet.com.au/~lloy0076/linux_c_programming/index.html
>