hallo, ich bin absoluter linux newbie und versuche verzweifewlt eine verbindung ins web ueber gprs via bluetooth aufzubauen.
ich habe im web auch eine ausfuehrliche anleitung dazu gefunden. aber an der stelle wo maN DIE MODEMBEFEHLE ABFRAGT ERHALTE ICH NUR DIE MELDUNG dass das modem nicht gefunden werden kann.
selbst als root benutzer ist das so.
hat jemand von euch evtl. einen tip fuer mich, wie ich das doch noch ans laufen bekomme? hier mal die anleitung die ich im web gefunden habe.
Using GPRS Internet
From SUSE Wiki
This article is about setting up an Internet connection using your GPRS-enabled cellphone. It may be applied, probably, also to an UMTS-enabled phone.
Contents
[hide]
• 1 Serial connection to the device
o 1.1 USB or serial cable
o 1.2 Infrared port
o 1.3 Bluetooth
• 2 KPPP configuration
[edit]
Serial connection to the device
The preliminary steps involve setting up a working serial connection with the phone internal modem.
[edit]
USB or serial cable
If you use a USB or serial cable, connect it to your linux box and to the cellphone. If the cellphone connection is supported, you should be able to see the device recognized. Enter dmesg or tail -f /var/log/messages in a Konsole. In this case, the serial port name of the modem is /dev/ttyS0, /dev/tty/USB0, or similar.
[edit]
Infrared port
If you have an Infrared port, enable it in SUSE: open Yast->Hardware->Infrared device, select Start IRDA, select the physical port the IRDA device is attached to (generally it is the second serial, /dev/ttyS1), and press Test. In the resulting window, you can see the IRDA discovery log, with lines stating
...
00:13:00.159207 xid:cmd 7f43b3f7 > ffffffff S=6 s=0 (14)
00:13:00.247209 xid:cmd 7f43b3f7 > ffffffff S=6 s=1 (14)
00:13:00.335216 xid:cmd 7f43b3f7 > ffffffff S=6 s=2 (14)
00:13:00.423226 xid:cmd 7f43b3f7 > ffffffff S=6 s=3 (14)
00:13:00.511231 xid:cmd 7f43b3f7 > ffffffff S=6 s=4 (14)
00:13:00.599234 xid:cmd 7f43b3f7 > ffffffff S=6 s=5 (14)
00:13:00.687237 xid:cmd 7f43b3f7 > ffffffff S=6 s=* ringo hint=0400 [ Computer ] (21)
...
Activate the IRDA port on your mobile device and put it in visibility with your Host IRDA port. The discovery log now should display a discovered device: it is your phone. If nothing happens, it may be that your Host IRDA chipset is not supported: give up. If there is a discovered device, continue and press Finish. In this case, the serial port name of the modem is /dev/ircomm0 or similar.
[edit]
Bluetooth
If you use Bluetooth, plug in your Bluetooth USB dongle or enable the Bluetooth chipset. Activate the BT services: Yast->Hardware->Bluetooth, then select Enable BT services and press Finish. Now, open the Bluetooth on your phone, and let it be discoverable. Open a Konsole, and enter the command hcitool scan DUN. If the result is something like this
ringo:~ # hcitool scan DUN
Scanning ...
00:80:37:FA:C8:11 T39m
ringo:~ #
then your phone is OK: the first hex string is the hardware address of the phone, the final string is the broadcast name of your cellphone. Now, the command sdptool search DUN
ringo:~ # sdptool search DUN
Inquiring ...
Searching for DUN on 00:80:37:FA:C8:11 ...
Service Name: Dial-up Networking
Service RecHandle: 0x10000
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
ringo:~ #
gives a number of results: you need the Channel number above. In this case, we can attach to a serial port, /dev/rfcomm0, with the following command
ringo:~ # rfcomm bind 0 00:80:37:FA:C8:11 1
Substitute the hex address and the final Channel number with your inquiry results. Remember, again, that your modem serial port is now /dev/rfcomm0.
To automate those steps, edit /etc/bluetooth/rfcomm.conf (tested on 10.0 and 10.1) to something like this:
rfcomm0 {
# Automatically bind the device at startup
bind yes;
# Bluetooth address of the device
device 00:80:37:FA:C8:11;
# RFCOMM channel for the connection
channel 1;
# Description of the connection
comment "Nokia 6230 bluetooth connection";
KPPP configuration
Now, we are ready to set up a connection with KPPP. Open KPPP, select Configure...->Modems->New, type something in the modem name field, select the proper modem device (/dev/ttyS0, /dev/ircomm0, or /dev/rfcomm0), Flow control to none. Press OK. Reselect the newly created modem, press Edit..., go to Modem tab, set the volume to 0, and push Modem commands. Set Initialization String 2 to ATM0 and press OK. Now push Query modem: after some ten seconds, you will find the results of your query. Differently, click on Terminal and enter the commands ATI, ATI1, ATI3, ATI5, and ATI7. The results should look like:
ATI
T39
ATI1
CXC125147_TAE
ATI3
T39 Bluetooth (TM) Modem
ATI5
Configuration Settings on Channel 0
&C: 1
&D: 0
+CGACT: 1,0
+CGATT: 1
+CGDCONT: 1,"IP","WEB.OMNITEL.IT","",0,0
+CGEREP: 0,0
+CGQMIN: 1,0,0,0,0,0
+CGQREQ: 1,0,0,3,0,0
+CGREG: 0,1
+CHSR: 0
+CHSU: 0
+CMEE: 0
+CMUX: 0,0,1,31,10,3,30,10,2
+CR: 0
+CRC: 0
+CRLP: 61,61,48,6,0
+CRLP: 120,120,48,6,2,3
+CVHU: 2
+DR: 0
+DS: 3,0,2048,32
+ICF: 3,3
+IFC: 2,2
+ILRR: 0
+IPR: 0
E: 1
M: 0
Q: 0
S0: 000
S10: 002
S2: 043
S3: 013
S4: 010
S5: 008
S6: 002
S7: 050
S8: 002
V: 1
X: 4
ATI7
T39 Modem Configuration Profile
Product Type Internal Terminal Adapter
Interfaces Bluetooth, IrDA, System Bus
Options FAX, GPRS, OBEX, RLP, V42bis
You can use ATI3 results to change your modem name. Now, look at ATI5: there is a line with CGDCONT:1 and the number 1 is your telephone connection number. Yours may be different. Let's go back to KPPP configuration: Accounts->New->Manual setup.
W
Description
rite a connection name, and add a number like *98*1# or *99***1#: I choose 1 because that is my preferred GPRS account, whereas your one can be different. Authentication mode is PAP/CHAP. Callback type is none. Click on Customize pppd arguments and add the following arguments
• lcp-echo-failure 10000
• lcp-echo-interval 30000
• lcp-max-configure 0
• lcp-max-failure 10000
• lcp-max-terminate 0
• lcp-restart 30000
Those ones are really necessary, otherwise pppd is going to close the connection after about 30s. Now, you can click on connect and browse, hopefully, the internet!
ich habe im web auch eine ausfuehrliche anleitung dazu gefunden. aber an der stelle wo maN DIE MODEMBEFEHLE ABFRAGT ERHALTE ICH NUR DIE MELDUNG dass das modem nicht gefunden werden kann.
selbst als root benutzer ist das so.
hat jemand von euch evtl. einen tip fuer mich, wie ich das doch noch ans laufen bekomme? hier mal die anleitung die ich im web gefunden habe.
Using GPRS Internet
From SUSE Wiki
This article is about setting up an Internet connection using your GPRS-enabled cellphone. It may be applied, probably, also to an UMTS-enabled phone.
Contents
[hide]
• 1 Serial connection to the device
o 1.1 USB or serial cable
o 1.2 Infrared port
o 1.3 Bluetooth
• 2 KPPP configuration
[edit]
Serial connection to the device
The preliminary steps involve setting up a working serial connection with the phone internal modem.
[edit]
USB or serial cable
If you use a USB or serial cable, connect it to your linux box and to the cellphone. If the cellphone connection is supported, you should be able to see the device recognized. Enter dmesg or tail -f /var/log/messages in a Konsole. In this case, the serial port name of the modem is /dev/ttyS0, /dev/tty/USB0, or similar.
[edit]
Infrared port
If you have an Infrared port, enable it in SUSE: open Yast->Hardware->Infrared device, select Start IRDA, select the physical port the IRDA device is attached to (generally it is the second serial, /dev/ttyS1), and press Test. In the resulting window, you can see the IRDA discovery log, with lines stating
...
00:13:00.159207 xid:cmd 7f43b3f7 > ffffffff S=6 s=0 (14)
00:13:00.247209 xid:cmd 7f43b3f7 > ffffffff S=6 s=1 (14)
00:13:00.335216 xid:cmd 7f43b3f7 > ffffffff S=6 s=2 (14)
00:13:00.423226 xid:cmd 7f43b3f7 > ffffffff S=6 s=3 (14)
00:13:00.511231 xid:cmd 7f43b3f7 > ffffffff S=6 s=4 (14)
00:13:00.599234 xid:cmd 7f43b3f7 > ffffffff S=6 s=5 (14)
00:13:00.687237 xid:cmd 7f43b3f7 > ffffffff S=6 s=* ringo hint=0400 [ Computer ] (21)
...
Activate the IRDA port on your mobile device and put it in visibility with your Host IRDA port. The discovery log now should display a discovered device: it is your phone. If nothing happens, it may be that your Host IRDA chipset is not supported: give up. If there is a discovered device, continue and press Finish. In this case, the serial port name of the modem is /dev/ircomm0 or similar.
[edit]
Bluetooth
If you use Bluetooth, plug in your Bluetooth USB dongle or enable the Bluetooth chipset. Activate the BT services: Yast->Hardware->Bluetooth, then select Enable BT services and press Finish. Now, open the Bluetooth on your phone, and let it be discoverable. Open a Konsole, and enter the command hcitool scan DUN. If the result is something like this
ringo:~ # hcitool scan DUN
Scanning ...
00:80:37:FA:C8:11 T39m
ringo:~ #
then your phone is OK: the first hex string is the hardware address of the phone, the final string is the broadcast name of your cellphone. Now, the command sdptool search DUN
ringo:~ # sdptool search DUN
Inquiring ...
Searching for DUN on 00:80:37:FA:C8:11 ...
Service Name: Dial-up Networking
Service RecHandle: 0x10000
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
ringo:~ #
gives a number of results: you need the Channel number above. In this case, we can attach to a serial port, /dev/rfcomm0, with the following command
ringo:~ # rfcomm bind 0 00:80:37:FA:C8:11 1
Substitute the hex address and the final Channel number with your inquiry results. Remember, again, that your modem serial port is now /dev/rfcomm0.
To automate those steps, edit /etc/bluetooth/rfcomm.conf (tested on 10.0 and 10.1) to something like this:
rfcomm0 {
# Automatically bind the device at startup
bind yes;
# Bluetooth address of the device
device 00:80:37:FA:C8:11;
# RFCOMM channel for the connection
channel 1;
# Description of the connection
comment "Nokia 6230 bluetooth connection";
KPPP configuration
Now, we are ready to set up a connection with KPPP. Open KPPP, select Configure...->Modems->New, type something in the modem name field, select the proper modem device (/dev/ttyS0, /dev/ircomm0, or /dev/rfcomm0), Flow control to none. Press OK. Reselect the newly created modem, press Edit..., go to Modem tab, set the volume to 0, and push Modem commands. Set Initialization String 2 to ATM0 and press OK. Now push Query modem: after some ten seconds, you will find the results of your query. Differently, click on Terminal and enter the commands ATI, ATI1, ATI3, ATI5, and ATI7. The results should look like:
ATI
T39
ATI1
CXC125147_TAE
ATI3
T39 Bluetooth (TM) Modem
ATI5
Configuration Settings on Channel 0
&C: 1
&D: 0
+CGACT: 1,0
+CGATT: 1
+CGDCONT: 1,"IP","WEB.OMNITEL.IT","",0,0
+CGEREP: 0,0
+CGQMIN: 1,0,0,0,0,0
+CGQREQ: 1,0,0,3,0,0
+CGREG: 0,1
+CHSR: 0
+CHSU: 0
+CMEE: 0
+CMUX: 0,0,1,31,10,3,30,10,2
+CR: 0
+CRC: 0
+CRLP: 61,61,48,6,0
+CRLP: 120,120,48,6,2,3
+CVHU: 2
+DR: 0
+DS: 3,0,2048,32
+ICF: 3,3
+IFC: 2,2
+ILRR: 0
+IPR: 0
E: 1
M: 0
Q: 0
S0: 000
S10: 002
S2: 043
S3: 013
S4: 010
S5: 008
S6: 002
S7: 050
S8: 002
V: 1
X: 4
ATI7
T39 Modem Configuration Profile
Product Type Internal Terminal Adapter
Interfaces Bluetooth, IrDA, System Bus
Options FAX, GPRS, OBEX, RLP, V42bis
You can use ATI3 results to change your modem name. Now, look at ATI5: there is a line with CGDCONT:1 and the number 1 is your telephone connection number. Yours may be different. Let's go back to KPPP configuration: Accounts->New->Manual setup.
W
Description
rite a connection name, and add a number like *98*1# or *99***1#: I choose 1 because that is my preferred GPRS account, whereas your one can be different. Authentication mode is PAP/CHAP. Callback type is none. Click on Customize pppd arguments and add the following arguments
• lcp-echo-failure 10000
• lcp-echo-interval 30000
• lcp-max-configure 0
• lcp-max-failure 10000
• lcp-max-terminate 0
• lcp-restart 30000
Those ones are really necessary, otherwise pppd is going to close the connection after about 30s. Now, you can click on connect and browse, hopefully, the internet!