due to my posting in this group
i recieved a personal email response
that solved my problem
thanks to that person for helping
i wont be coming back to follow this thread,
so if you would like more info on the topic
of accessing rr roaming dialup service in linux
feel free to email me.
i will post the response i was given,
in the hope it will help someone else
-------- here is the response i recieved ----------
On Tue, 11 Mar 2003 03:11:09 GMT, you posted to comp.os.linux.networking:
Quote:>I have tested my ppp/modem setup with someone elses dial up account,
>so i know that my configuration is good.
>i have read the man pages on pppd,chat,wvdial,
>and reviewed the GUI tools with redhat, including kppp.
>but have not grasped the solution to my problem
For a _NORMAL_ ISP, this would result in something like this:
[hubble ~]$ cat /usr/local/bin/dialin
exec /usr/sbin/pppd connect "/usr/sbin/chat -f /etc/ppp/dialscript"? \
defaultroute lock noipdefault modem nodetach /dev/modem 115200 crtscts \
There must not be anything after the \ in those two lines.
[hubble ~]$ cat /etc/ppp/dialscript
ABORT BUSY ABORT 'NO CARRIER' "" AT&F1 OK ATDT2662902 CONNECT \d\c
You would change the username at the end of the first script, and the phone
number and modem init-string (see your modem manual - &F1 is for a USR,
while others probably want &F0) in the second.
There would also be /etc/ppp/pap-secrets or chap-secrets, depending on the
authentication protocol chosen by the ISP. But other than setting the name
server addresses in /etc/resolv.conf, that's the whole thing.? It's a lot
simpler than the material presented in the (nearly obsolete) man pages.
Quote:>1. the remote end sends a login prompt
>2. I respond in plain text with the string "aolnet/ent."
>2. the remote end starts ppp
PARSE ERROR - core dumped??????????? ;-)
It's _very_ unusual to see a login prompt being presented to a dialin user
any more. I'd guess that 99% of the windoze users wowuld panic if they saw
one.? Basic windoze95 killed that off virtually around the world. But it's
extremely easy to implement - all that changes is the 'chat' script above.
I'd change that to
ABORT BUSY ABORT 'NO CARRIER' "" AT&F1 OK ATDT2662902 ogin: "aolnet/ent."
which means instead of waiting for the modem to report a connection, you
wait for the login prompt (here using the classic ogin: to accomodate a
capital or lower case L), then reply with the string. Note that the string
is quoted to protect the slash and period.
Quote:>3. i respond from within ppp with my login/password info
>??? ( i am not for sure of the mechanics of this, but it uses
>??? the standard process of winxp, so i assume CHAP?)
Could be one of several protocols - PAP (RFC1334), CHAP-MD5 (RFC1994),
microsofts borken version of CHAP (MS-CHAP v1 RFC2433), microsoft's
improved (and even more b0rken) version 2 (RFC2759) or one of a handful of
purposely incompatible mechanisms like ShivaPAP, SecureID, or similar. If
it's going to work with Linux, it has to be one of the first three, and they
work transparently if you have the right stuff in /etc/ppp/pap-secrets AND
You might be able to get this to work with one or more of the GUI "tools"
that come with modern distributions (like wvdial, kppp, etc.), but I'd
expect you'd need to hack the code to handle the separate authentication and
chat responses. Probably not worth the effort. The GUIs were never designed
Hope this helps,