Bluetooth dialup-networking under Linux with MTN

silentcoder

New Member
Joined
Oct 7, 2004
Messages
4
Reaction score
0
Location
.
Hi all,
I used to use the USB cable to dial up to the net using my Sony Erricson W810i. Worked fine, until I lost it. Seems a waste to have to buy a new one though - as I HAVE a bluetooth adaptor. All other bluetooth functions are working fine, I can copy/move files around, sync addressbooks whatever.

But I cannot get dialup to work despite weeks of googling and hacking.

I started by setting up the pairing etc. all seems fine because when I try to dial I can see the phone is trying to connect.

Then I edited my wvdial.conf file and changed the modem location to /dev/rfcomm0
In all other respects, it's exactly the same as before:
===========
[Dialer Defaults]
Modem = /dev/rfcomm0
Baud = 460800
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
#Init3 = AT+COPS=0,0," MTN",3
ISDN = 0
Modem Type = Analog Modem
Phone = *99***1#
Username = username
Password = password
=========

But it doesn't work - it starts to dial, but then the server just hangs up or something. Complains about LCP packets - I logged the output:

===========
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Cannot open /dev/rfcomm0: Input/output error
--> 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: ATDT*99***1#
--> Waiting for carrier.
ATDT*99***1#
CONNECT
~[7f]}#@!}!}!} }8}#}$@#}(}"}'}"}"}&} } } } }%}&,)-[0b]N/~
--> Carrier detected. Waiting for prompt.
~[7f]}#@!}!}"} }8}#}$@#}(}"}'}"}"}&} } } } }%}&,)-[0b]}$=~
--> PPP negotiation detected.
--> Starting pppd at Thu Feb 7 08:36:18 2008
--> pid of pppd: 14711
--> Using interface ppp0
--> pppd: Connect: ppp0 <--> /dev/rfcomm0
--> pppd: Remote message: Congratulations!
--> pppd: PAP authentication succeeded
--> pppd: LCP terminated by peer
--> pppd: Modem hangup
--> pppd: Connection terminated.
--> Disconnecting at Thu Feb 7 08:36:19 2008
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
--> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
--> Auto Reconnect will be attempted in 10 seconds
=======
And it repeats that over and over. The errors suggest that something is not set up right, possibly one of the initstrings or something on the bluetooth side ?

Has anybody successfully dialed up to mtn using bluetooth under linux ? Could you give me a hand ?

Ciao
A.J.
 
Did you write the config file yourself or did you use "wvdialconf" to autodetect your cellphone modem?

In my experience you do need to turn "stupid mode" on.. by adding "stupid mode = 1" under "dialer defaults" like this:
Code:
[Dialer Defaults]
Stupid Mode = 1

I've also found these init strings to be needed:
Code:
[Dialer 384k]
Init6 = AT+CGEQMIN=1,4,64,384,64,384
Init7 = AT+CGEQREQ=1,4,64,384,64,384

[Dialer 144k]
Init6 = AT+CGEQMIN=1,4,64,144,64,144
Init7 = AT+CGEQREQ=1,4,64,144,64,144

[Dialer 64k]
Init6 = AT+CGEQMIN=1,4,64,64,64,64
Init7 = AT+CGEQREQ=1,4,64,64,64,64
It will still normally connect without those, but on MTN I've found that with certain areas I need those or it simply will not connect.. :confused:

Just add one of them in your wvdial command line when connecting ... (i.e., "wvdial 144k" or "wvdial 384k" )
144k and 64k should be used if you're connected to GPRS or EDGE tower ... 384k only works if connected to a 3G tower.. (note this won't limit you to 3G speeds so no need to worry about that).


Oh and one final point, you don't seem to have the CGDCONT init string in your config...
Code:
Init5 = AT+CGDCONT=1,"IP","internet"
I know that with some phone you don't really need to specify it.. but I would anyway just in case.. ;)

Hope this helps.. :)
 
Top
Sign up to the MyBroadband newsletter
X