Re: modem driver file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Marvin,

It won't work without Stupid Mode  =  yes.

Thanks.

Jim

Marvin Stodolsky wrote:
Jim,

Try commenting out the Stupid Mode in /etc/wvdial.conf
#  Stupid Mode  =  yes

On 8/1/07, YH <yh@xxxxxxxxxxxxxx> wrote:

Thanks Jacques and Marv. I've tried to add +MS=34 to Init2, but got
following error, and stopped the process.

--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=34
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=34
ERROR
--> Bad init string.


Then, I tried to add  Username = bizmail/hce@xxxxxxxxxxxxxxx It did not
work. The message seems little bit different than last one. I included
both messages at follows:

--> WvDial: Internet dialer version 1.53
--> 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: ATDT0198331600
--> Waiting for carrier.
ATDT0198331600
CONNECT 34666 V42bis
--> Carrier detected.  Starting PPP immediately.
--> Starting pppd at Wed Aug  1 21:12:06 2007
--> pid of pppd: 3532
--> Disconnecting at Wed Aug  1 21:12:38 2007


Aug  1 21:12:07 Jupiter kernel: PPP generic driver version 2.4.2
        Aug  1 21:12:07 Jupiter pppd[3532]: pppd 2.4.1 started by root,
uid 0           Aug  1 21:12:07 Jupiter pppd[3532]: Using interface ppp0
                       Aug  1 21:12:07 Jupiter pppd[3532]: Connect:
ppp0 <--> /dev/ttyLT0              Aug  1 21:12:07 Jupiter
/etc/hotplug/net.agent: assuming ppp0 is already up     Aug  1 21:12:38
Jupiter pppd[3532]: Hangup (SIGHUP)                             Aug  1
21:12:38 Jupiter pppd[3532]: Modem hangup
 Aug  1 21:12:38 Jupiter pppd[3532]: Connection terminated.
          Aug  1 21:12:38 Jupiter /etc/hotplug/net.agent: NET
unregister event not supported
                                    Aug  1 21:12:38 Jupiter pppd[3532]:
Exit.

Thank you.

Jim

Jacques Goldberg wrote:

Jim,

The instructions at www.bizmail.com.au are very clear (for Windows under
tab labelled "Help Center".
The line shown in your wvdial.conf listing,
Username = hce@xxxxxxxxxxxxxx
is exactly what you need.
What Marv meant was Username = bizmail/hce@xxxxxxxxxxxxxx
not in agreement with the directions from the ISP.
In my Linux box I can see
[root@localhost]/etc/ppp>cat chap-secrets
# Secrets for authentication using CHAP
# client        server  secret                  IP addresses
####### redhat-config-network will overwrite this part!!! (begin)
##########
####### redhat-config-network will overwrite this part!!! (end)
############
and identical with PAP.
You write that the error is not always there, so since it also works
sometime the problem is elswhere.
The first cause to check would be a bad line quality.
What asyncmap set to FFFFFFFF does is to transmit non printable
characters as two characters which reduces the cause of error.
You did not report the speed (in message CONNECTED AT) reported by wvdial.
Perhaps the first thing you might do would be to reduce the maximal
allowed speed,
To do this add +MS=34 to the line
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 to become
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=34
if wvdial reported a speed higher than 33600 bauds
If the reported speed was lower or if +MS=34 does not help, try
+MS=32
This will either succeed or discard the hypothesis that the problem is
due to line speed.

Jacques

YH wrote:


Thanks Marvin, did you mean to try on "Username = bizmail/hce.com.au"?

Thank you.

Jim

Marvin Stodolsky wrote:


RE: CHAP authentication failed
For CHAP identification it is sometimes necessary to replace
LoginName with
provider/LoginName inder Linux

For example if your provider is BIZMAIL, then try:  BIZMAIL/LoginName

MarvS

On 7/31/07, YH <yh@xxxxxxxxxxxxxx> wrote:


Hi Jacques,



Great, Jim.
So if I understand you correctly you compiled the source file and your
modem works , right?


Yes, I compiled the source file and the modem works. But the connection
is not stable, it sometime failed at authentication (please see
following log message). Like today, I actually tried 5 reconnections
before it was connected. Not sure if following wvdial.conf caused the
problem? Or should I change asyncmap to FFFFFFFF next time?

[Dialer Defaults]
Modem = /dev/modem
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
Phone = 0198331600
Username = hce@xxxxxxxxxxxxxx
Password = xxxxxxx
Auto DNS = on
Abort = on
Stupid Mode = yes

Log message:

Jul 31 20:06:45 Jupiter kernel: PPP generic driver version 2.4.2
Jul 31 20:06:45 Jupiter pppd[2366]: pppd 2.4.1 started by root, uid 0
Jul 31 20:06:46 Jupiter pppd[2366]: Using interface ppp0
Jul 31 20:06:46 Jupiter pppd[2366]: Connect: ppp0 <--> /dev/ttyLT0
Jul 31 20:06:46 Jupiter /etc/hotplug/net.agent: assuming ppp0 is
already up
Jul 31 20:07:07 Jupiter pppd[2366]: Remote message: Authentication
failed
Jul 31 20:07:07 Jupiter pppd[2366]: CHAP authentication failed
Jul 31 20:07:07 Jupiter pppd[2366]: Hangup (SIGHUP)
Jul 31 20:07:07 Jupiter pppd[2366]: Modem hangup
Jul 31 20:07:07 Jupiter pppd[2366]: Connection terminated.
Jul 31 20:07:07 Jupiter pppd[2366]: Exit.











[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux