[ILUG] Dialup problems

[Darragh Bailey]

Quoting Lars Hecking <lhecking at users.sourceforge.net>:

>
>  Laptop running SuSE 9.1
>
>  Setting up dialup to, say, IOLfree, works fine with YaST/wvdial/kinternet,
>  but not with pppd directly, and I'm seeing similar problems when using
>  minicom. Basically, when it comes to the point where my chat script
>  expects the prompt, it gets binary garbage and then NO CARRIER. Same in
>  minicom: connecting to the site manually to see what the actual prompt
>  looks like, it gets binary garbage instead.
>
> /etc/ppp/peers/iolfree:
>  /dev/ttySL0 38400 crtscts
>  connect '/usr/sbin/chat -f /etc/ppp/chat-iolfree'
>  noauth
>  user iolfree
>  defaultroute
>  replacedefaultroute
>  netmask 255.255.255.0
>
> /etc/ppp/chat-iolfree:
>  TIMEOUT 120
>  ABORT '\nNO CARRIER\r'
>  ABORT '\nNO DIALTONE\n'
>  ABORT '\nERROR\n'
>  ABORT '\nNO ANSWER\n'
>  ABORT '\nBUSY\n'
>  ABORT '\nUsername/Password Incorrect\n'
>  '' AT
>  OK "ATDT1890924042"
>  CONNECT ''
>  'ogin:' iolfree
>  'word:' iolfree
>  'access>' ppp
>
<snipped>
> Nov 25 22:24:27 localhost chat[5522]: CONNECT
> Nov 25 22:24:27 localhost chat[5522]:  -- got it
> Nov 25 22:24:27 localhost chat[5522]: send (^M)
> Nov 25 22:24:27 localhost chat[5522]: expect (ogin:)
> Nov 25 22:24:27 localhost chat[5522]:  49333^M
> Nov 25 22:24:36 localhost chat[5522]: ~^?}#@!}!}!} "}!}$}%p}"}&} } } }
> }#}%B#}%}%}&_f}3.}1}$}%\}2}"}3}#} ^Y{~~^?}#@!}!}"}

Generally I see this output when there is no login prompt and all authenication
is being done over ppp using chap or pap.

I would be willing to bet that /etc/wvdial.conf has stupidmode set in it, and if
you check /etc/ppp/chap-secrets and /etc/ppp/pap-secrets you'll see the password
for the dialup account created with kinternet setup to be used by ppp.


I've never tried creating dial-up scripts before I usually leave it up to a
combination of wvdial/ppp and only tweak certain settings by hand if necessary
but you probably just need to kick off ppp as soon as you receive the connect
response and tell ppp to use chap or pap to authenicate correctly.

I don't know the correct arguments to pass but you should be able to find those
out either by checking the script that kinternet uses to start ppp or by just
checking the command line it uses when its started by kinternet using ps.

--
Darragh

"Nothing's foolproof to a sufficently talented fool"