Difference between revisions of "Bluetooth GPRS Howto"

From ArchWiki
Jump to: navigation, search
m (added switch to speicfy bt address)
Line 16: Line 16:
         00:19:79:89:13:8E      Penpen N70</pre>
         00:19:79:89:13:8E      Penpen N70</pre>
Now, mark that above address, it's the bluetooth hardware address of your mobile phone (provided that the name in the right matches what you have written in the phone).</li>
Now, mark that above address, it's the bluetooth hardware address of your mobile phone (provided that the name in the right matches what you have written in the phone).</li>
<li>Scan, which channel is used for Dial-Up Networking: <pre>sdptool search DUN
<li>Scan, which channel is used for Dial-Up Networking: <pre>sdptool search --bdaddr 00:19:79:89:13:8E DUN
Inquiring ...
Inquiring ...
Searching for DUN on 00:19:79:89:13:8E ...
Searching for DUN on 00:19:79:89:13:8E ...

Revision as of 10:11, 27 July 2008

This Howto will describe, how to set up a GPRS Internet connection using bluetooth device and compatible mobile phone.


  1. Linux compatible bluetooth device
  2. Bluetooth enabled mobile phone - I'm using Nokia N70


  1. Install bluez-utils, bluez-libs and dbus (install also ppp if you haven't):
    pacman -S bluez-utils bluez-libs dbus
  2. Start dbus and bluetooth service:
    /etc/rc.d/dbus start
    /etc/rc.d/bluetooth start
  3. Scan for nearby bluetooth devices:
    hcitool scan
    Scanning ...
             00:19:79:89:13:8E      Penpen N70
    Now, mark that above address, it's the bluetooth hardware address of your mobile phone (provided that the name in the right matches what you have written in the phone).
  4. Scan, which channel is used for Dial-Up Networking:
    sdptool search --bdaddr 00:19:79:89:13:8E DUN
    Inquiring ...
    Searching for DUN on 00:19:79:89:13:8E ...
    Service Name: Dial-Up Networking
    Service RecHandle: 0x10007
    Service Class ID List:
      "Dialup Networking" (0x1103)
    Protocol Descriptor List:
      "L2CAP" (0x0100)
      "RFCOMM" (0x0003)
        Channel: 3
    Language Base Attr List:
      code_ISO639: 0x454e
      encoding:    0x6a
      base_offset: 0x100
    Profile Descriptor List:
      "Dialup Networking" (0x1103)
        Version: 0x0100
    Now check the line beginning with "Channel:" - it contains the channel which is used for Dial-Up Network and it is not necessarily 1 and so is the case with my Nokia N70; my phone uses channel 3. Check also that you are reading the right results; the bluetooth hardware address must match your phone's.
  5. Next, edit /etc/bluetooth/hcid.conf . Set the following in options section:
    autoinit yes;
    security auto;
    Editing the same file, comment out passkey, as it is not used actually. Also, in the device section change the line beginning with name to:
    name "BlueZ (%h)";
  6. Now edit /etc/bluetooth/rfcomm.conf , first uncomment the rfcomm0 device section. Then add/change the lines as this (if necessary):
    bind yes;
    device 00:19:79:89:13:8E;
    channel 3;
    comment "GPRS dialup";
    Of course, you should use your device address and the appropriate channel.
  7. Edit the bluetooth script in /etc/rc.d/bluetooth to make the rfcomm start when bluetooth system is started:
  8. Restart the bluetooth service:
    /etc/rc.d/bluetooth restart
  9. Look, whether the bluetooth device is bound to the phone. It should look like this:
    ll /dev/rfcomm0
    crw-rw---- 1 root tty 216, 0 2007-08-10 21:32 /dev/rfcomm0
  10. Now comes the interesting part. You see, there must be an agreed password for connecting to the phone's modem. And this password is set up in an awkward way. First decide a password. Then open another root console, type there (substitute your phone's hardware address and password accordingly)
    passkey-agent 8922 00:19:79:89:13:8E
    , but don't press enter yet. On another root window, issue
    cat /dev/rfcomm0
    and immediately after that execute the typed passkey-agent command in other window. Situation is like this http://asuka.fi/u/jpaalija/tmp/catting_passkey-agent_ready.png The phone should now show something like this: http://asuka.fi/u/jpaalija/tmp/passcode_dialog.jpg . Quickly, enter the passcode and press "Ok". If the passkey-agent prints something like
    Passkey	request	for device 00:19:79:89:13:8E
    Passkey	service	has been released
    you have no need to hurry anymore as you are almost set. Next, go to Menu->Connectivity->Bluetooth, select right for paired devices, select Options->Set as authorized, confirm and you are done!
  11. Edit the bottom of /etc/ppp/ip-up as following:
    echo -e "#generated by ip-up\nsearch local\nnameserver $DNS1\nnameserver $DNS2" > /etc/resolv.conf
    chmod a+r /etc/resolv.conf
    This change is used to set correct DNS settings after connection.
  12. Now you need scripts to actually use the phone's modem and call your ISP. My ISP is the Finnish saunalahti, mainly because of it's predefined fee for unlimited data access. You must substitute saunalahti for your ISP accordingly through the rest of the document. First we edit the modem setup script for my isp. I'm using script named /etc/ppp/peers/saunalahti and having the following content:
    connect /etc/ppp/peers/saunalahti-connect
    disconnect /etc/ppp/peers/saunalahti-disconnect
    #lcp-echo-interval 0
    maxfail 10
    lcp-echo-failure 0
    lcp-echo-interval 0
    #lcp-max-configure 0
    #lcp-max-failure 10000
    #lcp-max-terminate 0
    #lcp-restart 30000 
    linkname saunalahti
    mtu 1500
    mru 1500
    Some remarks: You should possibly first uncomment the nodetach-option, so you can track, whether the call succeeds. Without the option you just get no confirmation. The lines starting with "connect" and "disconnect" are locations for connect and disconnect chat scripts. Chat scripts are used to "talk" with the modem. Lets take a look at them next.
  13. Now, we edit the connect script. Mine is at /etc/ppp/peers/saunalahti-connect and is like the following:
    exec chat                                               \
            TIMEOUT         5                               \
            ECHO            ON                              \
            ABORT           '\nBUSY\r'                      \
            ABORT           '\nERROR\r'                     \
            ABORT           '\nNO ANSWER\r'                 \
            ABORT           '\nNO CARRIER\r'                \
            ABORT           '\nNO DIALTONE\r'               \
            ABORT           '\nRINGING\r\n\r\nRINGING\r'    \
            ''              \rAT                            \
            TIMEOUT         12                              \
            SAY             "Press CTRL-C to close the connection at any stage!"    \
            SAY             "\ndefining PDP context...\n"   \
            OK              ATH                             \
            OK              ATE1                            \
            OK              'AT+CGDCONT=1,"IP","internet.saunalahti","",0,0'        \
            OK              ATD*99#                         \
            TIMEOUT         22                              \
            SAY             "\nwaiting for connect...\n"    \
            CONNECT         ""                              \
            SAY             "\nConnected." \
            SAY             "\nIf the following ppp negotiations fail,\n"   \
            SAY             "try restarting the phone.\n"
    Also some remarks about these: In the place of internet.saunalahti you should have your mobile operators access point name. That can be checked from Settings->Connection->Access points . Hilight the Internet access point and select edit. Go down to section "Access point name". There you have it. One more thing. The modem command "ATD*99#"'s number "*99#" is a special number (at least in Nokia phones) which is used to "call to Internet access point". Pretty clever I'd say; no fiddling around with actual numbers, let the phone handle everything behind the scenes.
  14. Edit the disconnect script (mine's is in /etc/ppp/peers/saunalahti-disconnect). You should have something like this:
    exec /usr/sbin/chat -V -s -S    \
    ABORT           "BUSY"          \
    ABORT           "ERROR"         \
    ABORT           "NO DIALTONE"   \
    SAY             "\nSending break to the modem\n"        \
    ""              "\K"            \
    ""              "\K"            \
    ""              "\K"            \
    ""              "+++ATH"        \
    ""              "+++ATH"        \
    ""              "+++ATH"        \
    SAY             "\nPDP context detached\n"
  15. Set executable atribute for files saunalahti-connect and saunalahti-disconnect
    chmod +x /etc/ppp/peers/saunalahti*connect
  16. Ok, you have completely set up bluetooth + gprs connection. Yay! Next thing to do is to test it. If you let the "nodetach" option uncommented in section 12, running (again, substitute yourisp for, well your ISP :)
    pon yourisp
    should return something like this:
    Press CTRL-C to close the connection at any stage!

    defining PDP context... rAT OK ATH OK ATE1 OK AT+CGDCONT=1,"IP","internet.saunalahti","",0,0 OK waiting for connect...

    ATD*99# CONNECT Connected. If the following ppp negotiations fail, try restarting the phone.

    Serial connection established. Using interface ppp0 Connect: ppp0 <--> /dev/rfcomm0 kernel does not support PPP filtering Cannot determine ethernet address for proxy ARP local IP address remote IP address primary DNS address

    secondary DNS address
    If the output is something similar, you have a working connection . If this is the case, you can press ctrl-c to abort the connection and uncomment the "nodetach" option from section 12. Later when you want connection, you can just run
    pon yourisp
    and when disconnecting
    poff yourisp
  17. Add "dbus bluetooth" to the DAEMONS section in /etc/rc.conf so you can connect more easily after reboot.
  18. All done, enjoy!