Sorry Dante: no attachments in your mail!
Dante ZePasta wrote:
Okay, per Jacques' suggestions, I used wvdial to try
to connect to my ISP (which is BruinOnline). I seemed
to get a bit further - some of the time.
The logs Jacques requested are attached - but the
command I was told to use to generate the
wvdial-specific log didn't work, so I manually copied
over everything that appeared in the terminal during
the dialing sequence into a text file.
Also, I attached two versions of "mybug1.txt" because
my modem doesn't do the same thing every time I try to
connect. Sometimes the negotiations appear to time
out before the ppp daemon recognizes the carrier;
sometimes it recognizes the carrier but then seems to
get stuck (mybug1alt) until manually terminated, and
sometimes the connection routine appears to complete
successfully - only to then tell me that DNS isn't
available/working properly. (By the way, what is this
"pppd: sword" thing popping up all over the place?)
Bottom line: while my modem is clearly working, I can
never seem to properly connect.
Other notes:
stupid/non-stupid mode produce virtually identical
results.
I inserted the "Detect Carrier = 0" line into
wvdial.config.
Thanks again.
"Marv,
Obviously, Dante's ISP is BruinOnLine (BOL)
http://www.bol.ucla.edu/
Dante does not explictly write which dialer program
generated his log
(which shows that the dialer uses wvdial), not
reporting further wvdial
output once the modem-to-modem connection is set up
and works.
It would tremendously help if Dante would use
uninterfaced wvdial
because we would see the behavior of wvdial during the
clearly failing
logon procedure.
The BOL setup (Win, Mac, no Linux) instructions are
hyper-standard and
leave no room for some trick which could fool a
standard ppp (for
example it uses PAP, not some possibly "proprietary"
variant).
My bet is that Dante's SuSE box uses a conflicting
"verbessert" version
of ppp.
No doubt, Dante: use PLAIN wvdial to try to connect.
If it still fails:
Edit /etc/ppp/options
Add one line:
debug
In the following console 1 is where you use wvdial.
Create an extra console which will be console 2. Be
root or use
su in console 2 (and already before in console 1).
In console 2 type exactly as shown:
tail -f /var/log/messages | tee mybug2.txt
Now go to console 1 and type:
wvdial | tee mybug1.txt
When wvdial terminates or hangs up,
go to console 2 and hit CTRL-C
If wvdial did not exit go to console 1 and hit CTRL-C
You now will have two files, mybug1.txt and mybug2.txt
Send them to us.
ADDITION: Dante, if you believe that your kppp works
better except for
the NO CARRIER issue, add ATX3 in the initialization
string field
available under Modem Configuration.
Jacques"
