Linmodems Mailing list Archives

Google
 
Web archives.linmodems.org

Return-Path: <stodolsk@rcn.com>
Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Delivered-To: mailing list discuss@linmodems.org
Received: (qmail 16859 invoked from network); 2 Jun 2001 20:24:51 -0000
Received: from smtp01.mrf.mail.rcn.net (207.172.4.60)
  by www.linmodems.org with SMTP; 2 Jun 2001 20:24:51 -0000
Received: from 66-44-2-38.s546.apx1.lnh.md.dialup.rcn.com ([66.44.2.38] helo=rcn.com)
	by smtp01.mrf.mail.rcn.net with esmtp (Exim 3.16 #6)
	id 156HwX-0004B1-00 
	for discuss@linmodems.org; Sat, 02 Jun 2001 16:24:18 -0400
Sender: marv
Message-ID: <3B194AFE.D0057372@rcn.com>
Date: Sat, 02 Jun 2001 15:22:22 -0500
From: Marvin Stodolsky <stodolsk@rcn.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.4.3 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: LinModems <discuss@linmodems.org>
Subject: wvdial instructions for winmodems,  pedantic
Content-Type: multipart/mixed;
 boundary="------------12F944035D177DFE0251682F"

This is a multi-part message in MIME format.
--------------12F944035D177DFE0251682F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The great majority of you DO NOT need the Attachment,
but given some recent reported mis-use, its useful to have it in the
repository to link up.  Anyone feel write to edit a version for your
particular winmodem.

MarvS
--------------12F944035D177DFE0251682F
Content-Type: text/plain; charset=us-ascii;
 name="wvdial.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="wvdial.txt"

Here is how to set  up WVDIAL for usage with winmodems.
The guidance here is for ltmodem hardware & drivers.
But the process will be substantially the same for any winmodem.

1) First check that you drivers in fact have been added to the running kernel:
$ 	modprobe lt_serial
$	lsmod
among modules displayed there should be:
lt_serial              21008   
lt_modem              314752   [lt_serial]

2) wvdialconf scans ONLY for ports with generic serial port names: /dev/ttyS* 
Consequently  a symbolic link is needed for using other port designations.
First verify that there is present a real node, for the case of ltmodem it is:
$ 	ls -l /dev/ttyLT0
crw-rw----    1 root     dialout   62,  64 Jun  2 13:32 /dev/ttyLT0

which should have been made earlier by  
	./autoload 
Next make the TEMPORARY symbolic link using the "local/experimental" port
reservation space, S14 or S15:
$	ln -sf /dev/ttyLT0 /dev/ttyS14
Verify success with:
$	# ls -l  /dev/ttyS14
lrwxrwxrwx    1 root     root      11 Jun  2 13:16 /dev/ttyS14 -> /dev/ttyLT0

AFTER your setups be low are completed, BE SURE to: 
$	rm -f /dev/ttyS14
as for a Very-Small-Minority of Systems having resource conflicts,
retention of /dev/ttyS14 could cause a CRASH during bootup.

3) Now run the configuration test with command:
$	wvdial /etc/wvdial.conf
There should be output like:
-----
Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1 -- ATQ0 V1 E1 -- nothing.
Port Scan<*1>: S1   S2   S3   
ttyS14<*1>: ATQ0 V1 E1 -- OK
ttyS14<*1>: ATQ0 V1 E1 Z -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 -- OK
ttyS14<*1>: Modem Identifier: ATI -- LT V.90 Data+Fax Modem Version 5.99
ttyS14<*1>: Speed 2400: AT -- OK 
ttyS14<*1>: Speed 4800: AT -- OK 
ttyS14<*1>: Speed 9600: AT -- OK  
ttyS14<*1>: Speed 19200: AT -- OK
ttyS14<*1>: Speed 38400: AT -- OK
ttyS14<*1>: Speed 57600: AT -- OK
ttyS14<*1>: Speed 115200: AT -- OK
ttyS14<*1>: Max speed is 115200; that should be safe.
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 -- OK  
--------
and there will be written a file /etc/wvdial.conf:

[Dialer Defaults]
Modem = /dev/ttyS14
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
; Phone = <Target Phone Number>
; Username = <Your Login Name>
; Password = <Your Password >

---------
The following should next be done:
1) Edit 
   /dev/ttyS14 ---> /dev/ttyLT0
2) Edit the lines beginning with ; including deletion of ;
3) Your modem May or May Not be set with an appropriate Country Code.
If in doubt, edit per below:

[Dialer Defaults]
Modem = /dev/ttyLT0
Baud = 115200
Init1 = ATZ  
Init2 = AT+GCI=HexadecimalNumber
Init3 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
Phone = Target_Phone_Number
Username = Your_Login_Name 
Password = Your_Password

-------
HexadecimalNumber should be chosen from the list in DOCs/CountryCodes.

That is the essense. 
You should be able to dialout simple with:
$	wvdial
and terminate a session with:
$	Ctrl-C

For ltmodem users a liner within /etc/modules.conf
   alias char-major-62 lt_serial

enables demand loading of drivers, upon start up of PPP.
--------------------------------------------------

Happily note that Wvdial supports Many Useful configuration variants
Do read the documentation suppled with the wvdial package.
Below is one of mine:

======================
[Dialer Defaults]
Modem = /dev/ttyLT0
Baud = 115200
Init1 = ATZ
# Init2 = AT+GCI=b5, country code usage when traveling
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0

# Phone = 17574238738
Phone = 3019178111
Username = stodolsk
Password = xxxxxxx

[Dialer daughter]
phone=4301146
Username = xxxxxxxx
Password = YYYYYYY

[Dialer lake]
Phone = 17574238738

[Dialer hotel]
Phone = 8,1,9252189607

# for verbose report
#  wvdial >/var/log/wvdial.log 2>&1 &

# Jacques advice.
# This last thing has rescued me from something looking like your new problem:
#  pppd waited for a prompt and the ISP waited for a request. 
# StupidMode = yes
# With StupidMode on using wvdial, 
#  pppd starts trying to establish a connection and everything works fine.
===============
For example, to use my daughter's IP when visiting, it suffices to:

$	wvdial daughter


--------------12F944035D177DFE0251682F--

Webmaster: Russell Nelson
Last modified: Wed Jul 30 11:02:43 EDT 2003