GUI
using KPPP
(some steps still have to be done via the CLI)
(some steps still have to be done via the CLI)
Start the Bluetooth service:
litljay:/ # service bluetooth start
Starting bluetooth: hcid sdpd hidd hid2hci opd rfcomm pand dund done
litljay:/ #
Get your phone's MAC address and the channel number for your phone's DUN service:
litljay:/ # sdptool search DUN
Inquiring ...
Searching for DUN on ...
Service Name: Dial-up networking
Service RecHandle: 0x10001
Service Class ID List:
"Dialup Networking" (0x00001103)
Protocol Descriptor List:
"L2CAP" (0x00000100)
"RFCOMM" (0x00000003)
Profile Descriptor List:
"Dialup Networking" (0x00001103)
Version: 0x0100
litljay:/ #
So we know that my phone's MAC address is 00:16:DB:D5:9C:1C and that the DUN service is on channel 2 (flashing). We need to bind this to a serial port. Use a text editor to edit the file /etc/bluetooth/rfcomm.conf:
rfcomm0 {
bind yes;
device 00:16:DB:D5:9C:1C;
channel 2;
comment "Jason's Cell Phone";
}
We also need the file /etc/bluetooth/hcid.conf, which is probably fine by default if you already configured bluetooth in Yast:
options {
autoinit yes;
security user;
pairing multi;
passkey ";
}
device {
name "DESKTOP";
class 0xff0100;
iscan enable;
pscan enable;
lm accept;
lp rswitch,hold,sniff,park;
}
Restart the Bluetooth service to get it bound:
litljay:/ # service bluetooth restart
Shutting down bluetooth ( dund pand opd hidd sdp hcid) done
Starting bluetooth: hcid sdpd hidd hid2hci opd rfcomm pand dund done
litljay:/ #
Check to make sure it bound the phone correctly:
litljay:/ # rfcomm
rfcomm0: 00:16:DB:D5:9C:1C channel 2 clean
litljay:/ #
If it isn't (usually after changing an existing rfcomm.conf) you may have to replug your bluetooth adapter or even reboot.
Alternately, if the bind fails you can bind it manually just this once, knowing that it should bind automatically on the next reboot:
litljay:/ # rfcomm bind 0 00:16:DB:D5:9C:1C 2
litljay:/ # rfcomm
rfcomm0: 00:16:DB:D5:9C:1C channel 2 clean
litljay:/ #
Start KPPP. You may have to do it as root if you run into permissions problems. Click on the
button:
Go to the "Modems" tab, click on the
button:
On the "Device" tab, give the modem a name that you like, set "Modem device:" to "/dev/rfcomm0", "Flow control" to "None", "Line termination" to "CR", and "Connection speed" to "115200", uncheck "Use lock file", and then click on the
button:
Select the newly created modem and click the
button...
...followed by the "Modem" tab. Uncheck "Wait for dial tone before dialing" and click on the
button:
This will give you a report of
its results and (hopefully) populate the command set for your phone.
My Samsung A707 Sync returns the exact same useless line on all 8
inquiries...
...so the commands must be filled in manually. You can check by dismissing the results with the
button followed by clicking the 
button
to see if most of the blanks are filled in. If they aren't, you
can probably use the standard Hayes AT commands from the following screenshot. EVEN
IF YOUR MODEM WAS ABLE TO AUTOMATICALLY POPULATE YOU WILL NEED TO FILL
IN THE "Initialization string 2:" LINE AS IT IS SHOWN BELOW!
Take note of the highlighted section in the screenshot. This will need
to be changed to your wireless carrier's data gateway (some Cingular
customers will need to use "ISP.CINGULAR" instead of "WAP.CINGULAR"):
Click, then again, click on the "Accounts" tab, and click on the button:
Opt for the
when prompted:
Give the connection a name that you like. Something relevant to your wireless carrier is useful. Click the
button...
...and type the phone number for your carrier. *99# and *99***1# are both common, and they both work on Cingular's WAP gateway. Click the button. Set "Authentication:" to "PAP", "CHAP", or "PAP/CHAP", check "Store password", and set "Callback type:" to "None". Click the button...
...and the button again. Select your connection that you just created and enter the user name and password for your carrier. On Cingular
connections these are supposedly "WAP@CINGULARGPRS.COM"
("ISP.CINGULARGPRS.COM" for the ISP gateway) and "CINGULAR1", but I
have connected using just about anything for both; even leaving them
blank! Check "Show log window" if you want to watch the terminal as it connects:
Now just click the
button
and you should be tethered! You can disconnect by clicking the
minimized window on the taskbar that is named for your connection and
then clicking the 
button:
...so the commands must be filled in manually. You can check by dismissing the results with the
button followed by clicking the button
to see if most of the blanks are filled in. If they aren't, you
can probably use the standard Hayes AT commands from the following screenshot. EVEN
IF YOUR MODEM WAS ABLE TO AUTOMATICALLY POPULATE YOU WILL NEED TO FILL
IN THE "Initialization string 2:" LINE AS IT IS SHOWN BELOW!
Take note of the highlighted section in the screenshot. This will need
to be changed to your wireless carrier's data gateway (some Cingular
customers will need to use "ISP.CINGULAR" instead of "WAP.CINGULAR"):Click
, then again, click on the "Accounts" tab, and click on the button:Opt for the
when prompted:Give the connection a name that you like. Something relevant to your wireless carrier is useful. Click the
button......and type the phone number for your carrier. *99# and *99***1# are both common, and they both work on Cingular's WAP gateway. Click the
button. Set "Authentication:" to "PAP", "CHAP", or "PAP/CHAP", check "Store password", and set "Callback type:" to "None". Click the button......and the
button again. Select your connection that you just created and enter the user name and password for your carrier. On Cingular
connections these are supposedly "WAP@CINGULARGPRS.COM"
("ISP.CINGULARGPRS.COM" for the ISP gateway) and "CINGULAR1", but I
have connected using just about anything for both; even leaving them
blank! Check "Show log window" if you want to watch the terminal as it connects:Now just click the
button
and you should be tethered! You can disconnect by clicking the
minimized window on the taskbar that is named for your connection and
then clicking the button: