For all the people trying to use wvdial and stuff and failing, you could try
to figure where the problem occours by using minicom or the likes to directly
talk to the modem.
Fire up minicom, set the modem device and speed etc.
Reset the modem:
ATZ
Dial out:
ATDT123455 (or whatever)
>From here on you can see what exactly happens. If you get a bunch of crap
after a CONNECTED reply, you're most likely using pap or chap. Either enter
the account,password in /etc/ppp/chap-secrets or /etc/ppp/pap-secrets - or
add a 'StupidMode=1' entry in the /etc/wvdial.conf file.
One possiblity is that you might be connecting to a server that uses ms-chap
or the likes. This may require a patched pppd in order do connect. Add a
'debug' line to /etc/ppp/options and tail the logs (/var/log/messages) while
connecting (use 'tail -f /var/log/messages') on another terminal and see what
you get when you use wvdial.
I know that this isn't s solution, but the logs that you post from a dial out
session is normally more useful in fixing the problem than an 'I can't use
wvdial' post. :)
Fooling with minicom is useful to tell you if the problem is with a modem
init string (you can't get connected) as opposed to an authentication problem.
Both can be fixed - with a little patience.
HTH,
-Faisal.
--
-====----====----====----====----====----====----====---
____
/ \
"@'| '..` |`@" L I N U X
/__| \__/ |__\ May the source be with you
\__U_/
--------------------------------------------------------
DON'T PANIC!
-The Hitchhiker's Guide To The Galaxy.
-====----====----====----====----====----====----====---
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/linux-india-help
