The document http://linmodems.technion.ac.il/post-install.html says how
to start debugging and especially how to collect from /var/log/messages
the detailed negotiations going on behind the scene once the CONNECT
message has been displayed.
The material is not trivial and requires attention specially to set the
debug options without which the log is not of great value.
As soon as CONNECT occurs, wvdial triggers pppd which first of all tries
to login.
Since Peyton's wvdial log does not recognize a login prompt but the
remote server has apparently identified itself and wvdial has
captured the identification string (assuming that
STATION ID - hontx07rh11hp011,dlltx43ev
comes from the server, not from Peyton's machine, highly likely), the
detailed debug log from /var/log/messages will immediately show who
waits for what.
Do you, Peyton, have any idea about who writes this completely folkloric
"STATION ID"?
Could you be trying to use some weird ISP who expects the user to know
that this is a login prompt?
In that case, as smart as wvdial may be, it is not enough of a genious
to take this for a prompt.
Jacques
Antonio Olivares wrote:
Peyton,
``Is the line in wvdial: "--> Cannot get information for serial port."
significant?''
Guess it is not very significant if you are not using a serial port.
Otherwise, don't worry about these messages.
``
..........
ATDT7134902223
CONNECT 52000
--> Carrier detected. Waiting for prompt.
STATION ID - hontx07rh11hp011,dlltx43ev
''
This shows that it tried to connect, but failed because of ??? reason.
I hope other users can recommend strategies to get this going. But
for now, I can only recommend checking the DOCs/ folder for
wvdial.txt. You may add a line "Carrier Check = no" and see if it
makes any difference, and or "Stupid Mode = yes" also.
Regards,
Antonio
On Wed, May 12, 2010 at 11:00 AM, peyton bay <peytonbay@xxxxxxxxxxxxx> wrote:
Antonio Olivares wrote:
Peyton,
scanModem reports that your modem is supported through
SLMODEMD.gcc.4.2-??? drivers:
Thanks Antonio,
I seem to be making progress ... up to a point. I can connect after a
loooong wait but then the authentication goes south. I spent the morning
with my dsl provider ATT trying to get info about their dialup services. The
username and password are what I was given this morning. Here is how it
looks. Any ideas? Is the line in wvdial: "--> Cannot get information for
serial port." significant?
-------------------------- slmodemd ----------------------------
peyton@peyton1100:~$ sudo slmodemd --alsa modem:1
[sudo] password for peyton:
SmartLink Soft Modem: version 2.9.11 Dec 16 2008 22:54:51
symbolic link `/dev/ttySL0' -> `/dev/pts/2' created.
modem `modem:1' created. TTY is `/dev/pts/2'
Use `/dev/ttySL0' as modem device, Ctrl+C for termination.
-------------------------- /etc/wvdial.conf ----------------------------
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
Baud = 460800
New PPPD = yes
Modem = /dev/ttySL0
ISDN = 0
Password = ********
Username = pmbay@xxxxxxxxxxxxx
[Dialer hou1]
Phone=7135542481
[Dialer hou2]
Phone=7134902223
-------------------------- wvdial ----------------------------
peyton@peyton1100:~$ sudo wvdial hou2
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT7134902223
--> Waiting for carrier.
ATDT7134902223
CONNECT 52000
--> Carrier detected. Waiting for prompt.
STATION ID - hontx07rh11hp011,dlltx43ev
Welcome
Please Sign-on:
--> Looks like a login prompt.
--> Sending: pmbay@xxxxxxxxxxxxx
pmbay@xxxxxxxxxxxxx
Name, password pair incorrect
Please Sign-on:
--> Looks like a login prompt.
--> Sending: pmbay@xxxxxxxxxxxxx
pmbay@xxxxxxxxxxxxx
Name, password pair incorrect
Please Sign-on:
--> Looks like a login prompt.
--> Sending: pmbay@xxxxxxxxxxxxx
pmbay@xxxxxxxxxxxxx
Name, password pair incorrect
Please Sign-on:
--> Looks like a login prompt.
--> Sending: pmbay@xxxxxxxxxxxxx
pmbay@xxxxxxxxxxxxx
Login failed, reason = (-190,dlltx43ev,1273678481-000,hontx07rh11hp011)
Connection closed by foreign host.
NO CARRIER
Caught signal 2: Attempting to exit gracefully...
--> Disconnecting at Wed May 12 10:35:37 2010
