[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Re. Total Confusion

[some extra quoting added, because your mailer doesn't and it would
 be confusing as to what were your words and what were others' words.]
On Sun, Jul 01, 2001 at 08:21:07AM -0700, Sidney Brooks wrote:
>> 2.) It's been a long time since I used minicom, but am I totally wrong in
>> thinking it's a terminal emulator? I don't think it's supposed to do ppp
>> of any sort to begin with. What are you trying to do with it, and what's
>> not working? That leads me to...
>        Minicom has a dial function. It is not a terminal emulator.

The original author, who is also the debian package maintainer, writes:

Maintainer: Miquel van Smoorenburg <miquels@cistron.nl>
Depends: libc6, libncurses4
Suggests: lrzsz
Description: Clone of the MS-DOS "Telix" communications program.
 Minicom is a menu driven communications program. It emulates ANSI and
 VT102 terminals. It has a dialing directory and auto zmodem download.

You are using it as a dialler, which is okay.  It can also be used as
a terminal emulator, among others.

>        I have already answered this question today. Both wvdial and minicom 
> connect (the log says so) but they do not authenticate when they send in 
> the password. Oddly minicom was programmed to send both username and 
> password, but nevertheless asked for them after it was connected.

 (I may be wrong here about some ppp facts, in which case I hope miquel
  notices this and follows up with a correction.  I may also be wrong
  about the situation with your provider, but then you do not give me
  many useful clues.)

Maybe you are trying to dial in to a place that only supports challenge
authentication protocol.  In that situation, the authentication takes
place as a part of the ppp setup.  So you can not first dial in, then
login, and finally start (unauthenticated) ppp, because there is no login.
You instead have to dial in, and then start ppp with chap authentication.

Since chap is the default for windows dial-up internet, most providers
support it.  Some providers provide both chap and some sort of shell

As wvdial does not speak ppp, it can not dial in on providers that do
chap only, I'm afraid.  But you can still use it to setup your modem
correctly or to make it generate the proper at commands for your modem,
so that you can put them in the "pon" dialling chatscript.  The same
is true for minicom, which also doesn't do ppp.

Perhaps this is why pppconfig worked for you, because it might have
configured an /etc/ppp/chap-secrets file with the proper user and
password information, and a file /etc/ppp/peers/provider with the ppp
options and the name of the dial script, that you can probably find in
/etc/chatscripts and is an /usr/sbin/chat script.  That is where you
can put extra at commands in, if pppconfig does not let you itself.

Alternatively, you can also set up ppp manually, and use wvdial in your
/etc/peers/provider script as the "connect" option to ppp.  With chat
it looks like this:

  connect "/usr/sbin/chat -v -f /etc/chatscripts/isp-foo"
Change this appropriately for wvdial.  Also make sure that there is a
"user" option, so pppd will know what chap secret to pick, and the
"noauth" option, which turns off the requirement for the isp to
authenticate (login) to your system.  If you set the "debug" option,
which is advisable to get started, it is also advisable to set the
"hide-password" option, or else the passwords are sent to the syslog
along with the debug info.

This and a lot more is also explained in the pppd(8) manpage, btw.



Reply to: