AutoPPP question

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

List,

    Before you dismiss my question as yet another ppp question not fit for
this list, please read below. I have gone thru the archives (yes, 15 months
worth) and read every thread regarding autoppp and win95, usually with a
Linux based server. This also applies to my case, but I wont ask about
config or win95 or why my modem goes bump in the night. please answer a very
basic question for me.

    Within the mgetty docs, and every web site about mgetty known to mankind
is this line for making win95 work:
/AutoPPP/       -       -       /usr/local/bin/pppd auth require-pap
refuse-chap login

... or some variance of it. Within the web sites and docs I have visited, I
have blindly followed the docs, with no variance, and yet I still have
problems. I have deduced this much:

1) mgetty does not register the caller as a user /AutoPPP/ and config fails
2) strange behaviour then ensues with variance, and little constants

As a beginner admin, I accept that its my responsibility to fix this. I
further accept I must perform debugging and go thru a trial and fail method
to locate the problem. I accept that actions taken AFTER mgetty has done its
proper job are not related to mgetty, and do not belong here. So, here is my
question (and I feel this belongs in the documentation). What does *EVERY*
field in that /AutoPPP/ line mean? Its presented as if its chisled in stone,
with no variance to system setups, and with no explanations anywhere I can
find. A second question (also fit for documentation), I notice, based on the
numerous logs I read on the archive, that some logs show a hit! next to an
AutoPPP match string, and some do not. As 90% of these questions are
answered by "this is a PPP question, not an mgetty question", please tell me
what a properly registered win95 autoppp call log should show? Is it indeed
an AutoPPP hit! or not? since this IS an mgetty log entry, and seems to deal
directly with mgetty detection, it seems a valid question.

    I realize once mgetty exits and args are handed to login or whatever the
admin sets up to handle the call, you have no responsibility for the
results, but at least tell us who struggle with the config how to interpret
a mgetty log, and what a proper response would be. I hope I avoided ALL
inquiries revolved around actual pppd problems, as I tried to very much.

Any help, tips, answers will be greatly appreciated, as I am out of time,
pateince, and hair on this debug.

Jeffrey Rasmussen
texan@bay-city.net