Iiwish it was as easy as you say.... I've been able to get kpp working (with
some trouble) and wvdial (with somewhat less trouble) and for the moment, both
seem to be working 100% .
But there is just no way I can get chat to talk to my modem.... I've just spent an
entire day fiddling around, reading the
howto's and the SDB. But whatever I try, when I send "ATZ" to my modem, BANG,
nothing happens...
On Mon, 28 Dec 1998, you wrote:
>Why do so many people have such a problem with suseppp? OK, its not exactly plug and
>play owing to the differences between ISPs, but it's easy enough to find out what you
>need to change in the chat script by dialling in manually with a modem program like
>minicom. That's how I did it.
>
>Here's a useful tip for those who are having problems; the default chat script isn't
>very informative about progress during connection and it's not very readable. As an
>alternative, you can adapt the shell script in /usr/lib/diald/connect to your ISP's
>login protocols quite easily as it is quite transparent about how it goes about
>making a conection.
>
>Rename the customised shell script to /etc/suseppp/scripts/generic.connect, then
>replace the pppd invocation in ppp-up with the following:
>
>/usr/sbin/pppd \
> connect "/etc/suseppp/scripts/$1.connect < /dev/modem > /dev/modem" \
> file /etc/suseppp/$1.options
>
>And that's all; just run /etc/suseppp/scripts/ppp-up to bring up the line.
>
>Ralph
>
>Joe Ryan wrote:
>
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
