Hi,

I have some problems with 'Wvdial' Would you pls help me to sort it out !

Details
Distribution : Debian Sarge
Modem : Samsung SGH C130
Port : /dev/sy0
Provider : Airtel India
Dial No : *99**1*1#
Password :
Username :
APN : airtelgprs.com But Idont know where to place this APN line ( is in resolv.conf? OR optins ? )
Username & password is not required ,Provider is not mentioned ,It is working in Windows XP. with out username & Password

My wvdial.conf is :
[Dialer Defaults]
Modem = /dev/ttyS0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
Phone = *99**1*1#
Username = " "
Password = " "



Wvdial.out File ( which is obtained by the command wvdial 2>&1 | tee wvdial.out )

--> WvDial: Internet dialer version 1.54.0
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
ATQ0
OK
--> Re-Sending: ATZ
ATZ
OK
--> 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: ATDT*99**1*1#
--> Waiting for carrier.
ATDT*99**1*1# ( In one forum i found ATD ,how can i modify this ?)
CONNECT
--> Carrier detected. Waiting for prompt.
--> Don't know what to do! Starting pppd and hoping for the best.
--> Starting pppd at Wed Jan 30 02:18:14 2002
--> pid of pppd: 4263
--> Using interface ppp0
--> Using interface ppp0
--> Disconnecting at Wed Jan 30 02:18:44 2002
--> The PPP daemon has died: PPP negotiation failed (exit code = 10)
--> man pppd explains pppd error codes in more detail.
--> I guess that's it for now, exiting
--> The PPP daemon has died. (exit code = 10)



Please let me know if there are mistakes in my configuration .
Thanks

reg
Arun

To use "ATD" as your dial string (rather than "ATDT") try adding the following to wvdial.conf

Dial Command = ATD

You appear to be actually connecting to something though based on the
Carrier detected. Waiting for prompt.
line, so I am not sure dialing is your problem.

This article (pdf file) suggests you would identify your APN in a modem initialization string. The article may not be talking about the exact modem you are using, but see if it doesn't give you some ideas about what to try. And here is another article that seems to be saying about the same thing.

I hope this helps.

I've never specified the APN on the computer, I simply select the appropriate GPRS connection profile in the phone.

The APNs for Vodafone UK and China Mobile are different, so I know that it works this way.

hI Blackhole,
As per that article i changed my wvdial.conf file as given below

But I am getting > Bad init string ERROR

node5:/home/node5# wvdial
--> WvDial: Internet dialer version 1.54.0
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
ATQ0
OK
--> Re-Sending: ATZ
ATZ
OK
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Modem initialized.
--> Configuration does not specify a valid phone number.
--> Configuration does not specify a valid login name.
node5:/home/node5# nano /etc/wvdial.conf
node5:/home/node5# wvdial
--> WvDial: Internet dialer version 1.54.0
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
ATQ0
OK
--> Re-Sending: ATZ
ATZ
OK
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Modem initialized.
--> Configuration does not specify a valid phone number.
--> Configuration does not specify a valid login name.
node5:/home/node5# nano /etc/wvdial.conf
node5:/home/node5# wvdial
--> WvDial: Internet dialer version 1.54.0
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
ATQ0
OK
--> Re-Sending: ATZ
ATZ
OK
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT&FV1&D2&SO&C1SO=0
AT&FV1&D2&SO&C1SO=0
ERROR
--> Bad init string.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT&FV1&D2&SO&C1SO=0
AT&FV1&D2&SO&C1SO=0
ERROR
--> Bad init string.
node5:/home/node5#

Hi Ojnab , can u pls show ur wvdial.conf file?

..arun

I am not sure about the bad init string (but maybe my suggestion doesn't work!). But I noticed you took out the Dial No line. The Dial Command line was to be in addition to what you had there before. I would add the Dial No string back in before I tried anything else.

I should make sure you are clear that I have used wvdial for standard dialup, but not for what you are doing. You should also know that I am unfamilar with Dial No. But I will note that on my system, wvdial logs everything it does into /var/log/messages, so I can see exactly what was done when something goes wrong. I.e., I get more detail than what you are showing. You might check your log to see if it has this info.

Hi blackhole thanks for your response. pls see the results and advice me!

My last few portion of /var/log/messages
----------------------------------------

Jan 8 12:02:16 localhost pppd[5630]: pppd 2.4.3 started by root, uid 0
Jan 8 12:02:16 localhost pppd[5630]: Using interface ppp0
Jan 8 12:02:16 localhost pppd[5630]: Connect: ppp0 <--> /dev/ttyS0
Jan 8 12:02:46 localhost pppd[5630]: LCP: timeout sending Config-Requests
Jan 8 12:02:46 localhost pppd[5630]: Connection terminated.
Jan 8 12:02:46 localhost pppd[5630]: Using interface ppp0
Jan 8 12:02:46 localhost pppd[5630]: Connect: ppp0 <--> /dev/ttyS0
Jan 8 12:02:46 localhost pppd[5630]: tcflush failed: Bad file descriptor
Jan 8 12:02:46 localhost pppd[5630]: Exit.
:

First, I want to appologize for an error I made in my last post; somehow I did not see your phone line and thought the file contained no phone number!

Also, I want to clarify what I was talking about wrt /var/log/messages. Here is a snippet of my file showing wvdial entries, followed by the start of pppd entries (of course, the details would differ from yours):

So from your last post I don't know if your log file didn't contain any wvdial entries or if everything went OK. I am not sure, but I am wondering if the &quot;LCP: timeout sending Config-Requests&quot; corresponds to the &quot;PPP negotiation failed (exit code = 10)&quot; in your first post.

You might try increasing the number of config-requests with an lcp-max-configure line in your /etc/ppp/options file. You must supply a number after it; the default is ten. I have never done this, so be sure to take a look at this in the pppd man page, and you also might want to google on it.

Hi Blackhole,

At the time of configuration i run wvdial >/var/log/wvdial.log 2>1&

I am suspecting that , so the log files are creating in /var/log/wvdial.log
instead of var/lor/messages !

My current /var/log/wvdial.log is given below

[HTML]
--> WvDial: Internet dialer version 1.54.0
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
ATQ0
OK
--> Re-Sending: ATZ
ATZ
OK
--> 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: ATDT*99**1*1#
--> Waiting for carrier.
ATDT*99**1*1#
CONNECT
--> Carrier detected. Waiting for prompt.
--> Don't know what to do! Starting pppd and hoping for the best.
--> Starting pppd at Wed Jan 30 02:09:53 2002
--> pid of pppd: 4145
--> Using interface ppp0
--> Using interface ppp0
--> Disconnecting at Wed Jan 30 02:10:24 2002[/HTML]

Hi Blachhole in other tutorial(http://kapsi.fi/~mcfrisk/linux_gprs.html#AEN226) refer to /etc/ppp/peers/gprs configuration.

Here is the stripped example from that tutorial..

I checked a few things and ran an experiment; Apparently wvdial logs differently on my system than yours because it is called differently. Specifically, mine is called from within pppd with the --chat option used. When I manually call it from the command line, I get output like yours and nothing in /var/log/messages. This is just for your info -- I am not suggesting you change anything on your system.

Point well taken.

To get some background you might want to look over this howto. But that document can throw you in the deep end pretty fast. You might want to just look through it to see what general concepts you can pull out rather than worrying about the details right now.

You need to be aware that there are two different, mutually exclusive ways to go about connecting. The howto I just mentioned, and the link you provided in post #10 talk about using chat scripts. This is an alternate way of doing things than using wvdial, which is discussed in the links I provided in post #2. So the first thing you need to decide is which method you wish to try. And note that if you wish to follow the instructions (using a chat script) provided in your link (post #10), that you are need to download and modify some files.

Some things I have gathered from your link and the link I mentioned above:

• The correct dial command is ATD rather than ATDT
• Different telephones behave differently. So you need to pay attention to this, and if you post back, you should include the model and make of the phone you are using.
• The string you are using for a phone number, I think is really a special command to the phone. From the howto linked above, certainly *98*2# is a special command that tells the phone to execute something already stored in it (that you might have to set up yourself). Now I notice this is different from the *9***1# used in the article you linked to, which is different yet from the *99**1*1# that you are using. So was this number you are using provided to you from your cell phone company, or else, where did you get it?

Look over this stuff and post back if you wish.

Hi blackhole,

That number *99**1*1# , i got it from my provider and the same is using in my Wndows box, which is working fine. but i need to switch to Debian completly. Nowadays i am booting to Windows only for Browsing.

Anyway i decided to approach the issue in a clear manner . So thanks for your help Black hole , I need your helps, I am newbie in this , have to learn lot of things.

Thanks once again.

Does YOUR Linux Box have KDE installed? IF Yes, try using Kppp. It is very easy to setup, and is configurable after setup to tweek to YOUR needs. Is it possible...that YOUR modem connects in M$Windows, but has not yet ever connected in Debian? IF never connected this modem in Debian...I strongly urge YOU to get an external serial modem that uses an RS-232 serial cable to YOUR serial port on YOUR Motherboard. On the circuit board is a controller chip that does all the work that the software in the Distro used to do. Plus, the Linux Distro uses the serial connection for most software applications. Very few Distros use the PCI modem interface successfully. And it is always a headache to configure. Try http://tldp.org/HOWTO/HOWTO-INDEX/howtos.html