Hi John;
If windoz can't handle it then I can think of ONE reason for doing it that
way! :->
You certainly could be right on the possibility of a "post-ppp" login but
I thought it was possible.
best,
-bill
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
Bill Leach writes:
> One question that I have: Is it true that ALL ISPs that use chap or pap
> authentication also do not require an initial login? I don't personally
> know of any exceptions but I also don't see any technical reason why it
> would not be possible to use chap following login.
I'v
Hi John;
One question that I have: Is it true that ALL ISPs that use chap or pap
authentication also do not require an initial login? I don't personally
know of any exceptions but I also don't see any technical reason why it
would not be possible to use chap following login.
It also seems to me
bill writes:
> Some ISPs using CHAP present the "username"/"password" sort of thing (of
> course "username:" might be something else like "login:", "account:",
> etc. but actually don't use them for ppp logins. If the script "wakes
> up getty" on such systems, a ppp login attempt will fail.
Yes,
John, I am not sure that I even want to get into this "flay" but some
comments about my own observations with the issue are:
Some ISPs using CHAP present the "username"/"password" sort of thing (of
course "username:" might be something else like "login:", "account:", etc.
but actually don't use the
Richard G. Roberto writes:
> This was supposed to be as generally useful to as many people as
> possible.
Yes. And the most generally useful thing to do for the most people is to
make it easy for them to get a single connection working so that they can
email for help and ftp files.
> It was origi
On Fri, 5 Dec 1997, Robert D. Hilliard wrote:
> On 05 Dec 1997 16:24:10 [EMAIL PROTECTED] wrote:
>
> > Richard G. Roberto writes:
> > > I also want to address this issue about "standard" options file
> > > locations. It is impossible to manage multiple ppp options sets in the
> > > same file u
On 05 Dec 1997 16:24:10 [EMAIL PROTECTED] wrote:
> Richard G. Roberto writes:
> > I also want to address this issue about "standard" options file
> > locations. It is impossible to manage multiple ppp options sets in the
> > same file unless the option requirements are identicle. ... I
> > pe
Richard G. Roberto writes:
> I also want to address this issue about "standard" options file
> locations. It is impossible to manage multiple ppp options sets in the
> same file unless the option requirements are identicle. ... I
> personally have three different connection requirements and use
Just to clear up some confusion about dunc, I realize the
script has shortcomings and John is looking into taking over
the package so it can get properly attended to. However,
its really quite useable in its current state -- even on a
bo system. It's just an ash script that uses dialog, so it
sho
On 03 Dec 1997 15:43:13 you asked:
> Can anyone give me some feedback on dunc?
Several weeks ago I experimented with dunc 1.5. The major bug I
found was in the dialup_connect script. There is what I think is
called a race condition that causes the "/bin/rm -f /tmp/wchatfile"
to remove wcha
On 3 Dec 1997 [EMAIL PROTECTED] wrote:
> Can anyone give me some feedback on dunc? I'm revising it and would like
> to hear opinions on what should be changed. Already planned are pap/chap
> support and use of the standard option and chat files.
What version of dunc are you "looking" at? The l
12 matches
Mail list logo
