{"id":4,"date":"2008-01-14T22:30:00","date_gmt":"2008-01-14T22:30:00","guid":{"rendered":"https:\/\/robertrath.com\/gadgetzone\/archives\/4-linux-hosted-bluetooth-ip-connection-for-tomtom.html"},"modified":"2008-01-15T03:35:24","modified_gmt":"2008-01-15T03:35:24","slug":"linux-hosted-bluetooth-ip-connection-for-tomtom","status":"publish","type":"post","link":"https:\/\/robertrath.com\/gadgetzone\/archives\/4-linux-hosted-bluetooth-ip-connection-for-tomtom.html","title":{"rendered":"Linux Hosted Bluetooth IP Connection For TomTom"},"content":{"rendered":"The following instructions are not meant to be a &#8216;how to&#8217; but a &#8216;how I did&#8217; and is based on Arjan van de Ven&#8217;s website <a href=\"http:\/\/www.fenrus.org\/tomtom\/\" title=\"http:\/\/www.fenrus.org\/tomtom\/\">http:\/\/www.fenrus.org\/tomtom\/<\/a> I have added a couple extra steps including modifying rfcomm.conf, registering the DUN service and specifying the bluetooth channel for DUN.<br \/>\n<br \/>\nThese notes assume you have bluetooth already present and operational as was the case with my Ubuntu 7.10 system.<br \/>\n<br \/>\n<strong>Install bluetooth support and confirm you can see your Bluetooth device.<\/strong><br \/>\n<br \/>\n # hcitool dev<br \/>\n Devices:<br \/>\n        hci0    00:02:5B:01:0D:CB<br \/>\n<br \/>\n<strong>Confirm you can see your TomTom<\/strong><br \/>\n<br \/>\n # hcitool scan<br \/>\n Scanning &#8230;<br \/>\n         00:13:6C:9C:A0:5A       TomTom ONE XL<br \/>\n<br \/>\n<strong>Change your bluetooth device&#8217;s class to report itself as a mobile phone offering Telephony services and confirm settings.<\/strong><br \/>\n<br \/>\n # hciconfig hci0 class 0x500204 (I borrowed this class from my Nokia phone)<br \/>\n # hciconfig hci0 class<br \/>\n hci0:   Type: USB<br \/>\n         BD Address: 00:02:5B:01:0D:CB ACL MTU: 384:8 SCO MTU: 64:8<br \/>\n         Class: 0x500204<br \/>\n         Service Classes: Telephony<br \/>\n         Device Class: Phone, Cellular<br \/>\n<br \/>\n<strong>To have the device class retained as the default HCI configuration edit the file &#8216;\/etc\/bluetooth\/hcid.conf&#8217;<\/strong><br \/>\n<br \/>\n<strong>Write this file into &#8216;\/etc\/ppp\/tomtom.sh&#8217; and ensure it has execute permissions.<\/strong> <br \/>\n<br \/>\n #!\/bin\/sh<br \/>\n \/usr\/sbin\/chat -e -f \/etc\/ppp\/tomtom.chat<br \/>\n<br \/>\n<strong>Write this file into &#8216;\/etc\/ppp\/peers\/tomtom&#8217;<\/strong><br \/>\n<br \/>\n noauth      # Don&#8217;t require authentication<br \/>\n local         # This is needed because it&#8217;s not a real serial line<br \/>\n noipdefault   # Don&#8217;t use the local hostname to determine the local IP used<br \/>\n proxyarp      # Proxy ARP connections<br \/>\n nodefaultroute   # Don&#8217;t use the default route<br \/>\n noipx      # Don&#8217;t use the IPX protocol<br \/>\n idle 0      # Set an unlimited disconnect timeout<br \/>\n <br \/>\n # Change the next three lines for your setup <br \/>\n <br \/>\n # :<br \/>\n #The first ip needs to be your computer, the second ip needs to be a non-used ip in your network<br \/>\n 192.168.10.204:192.168.10.214<br \/>\n <br \/>\n # ms-dns <br \/>\n # this needs to be a real dns server, look in \/etc\/resolv.conf<br \/>\n ms-dns 192.231.203.132<br \/>\n <br \/>\n # netmask <br \/>\n netmask 255.255.255.0<br \/>\n<br \/>\n<strong>Write this file into &#8216;\/etc\/ppp\/tomtom.chat&#8217;<\/strong><br \/>\n<br \/>\n ATZ OK<br \/>\n ATD CONNECT<br \/>\n<br \/>\n<strong>Write\/Edit the file &#8216;\/etc\/bluetooth\/rfcomm.conf&#8217;<\/strong><br \/>\n<br \/>\n #<br \/>\n # RFCOMM configuration file.<br \/>\n #<br \/>\n <br \/>\n rfcomm0 {<br \/>\n         # Automatically bind the device at startup<br \/>\n         bind no; <br \/>\n <br \/>\n         # Bluetooth address of the device<br \/>\n         # This is the address of my TomTom, put your own here!<br \/>\n         device 00:13:6C:9C:A0:5A;<br \/>\n <br \/>\n         # RFCOMM channel for the connection<br \/>\n         # This is appears to be the channel used for DUN<br \/>\n         channel 2;<br \/>\n <br \/>\n         # Description of the connection<br \/>\n         comment &#8220;Example Bluetooth device&#8221;;<br \/>\n }<br \/>\n <br \/>\n<strong>Start the Dial-Up Networking daemon. I found I needed to add the channel option.<\/strong><br \/>\n<br \/>\n # dund &#8211;dialup &#8211;listen &#8211;channel 2 call tomtom connect \/etc\/ppp\/tomtom.sh<br \/>\n<br \/>\n<strong>Register Dial-Up Networking service with bluetooth.<\/strong><br \/>\n<br \/>\n # sdptool add dun<br \/>\n Dial-Up Networking service registered<br \/>\n<br \/>\n<strong>You can use &#8216;# sdptool records local&#8217; to see all local bluetooth services now registered.<\/strong><br \/>\n<br \/>\n<strong>You will need to add these commands to turn your PC into a router for the connection.<\/strong><br \/>\n<br \/>\n echo 1 &gt; \/proc\/sys\/net\/ipv4\/ip_forward<br \/>\n iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE<br \/>\n<br \/>\n<strong>Now you are ready to connect with your TomTom, this is the tedious part as it has to be done manually.<\/strong><br \/>\n<br \/>\nManage Phones -&gt; Yes (search for phones) -&gt; (select you linux machine) -&gt; Continue -&gt; Yes<br \/>\nSelect your phone model: -&gt; Other<br \/>\nSelect your country: -&gt; Other<br \/>\nDo you want to set up your wireless data connection manually? -&gt; YES<br \/>\nAccess point name: -&gt; OK<br \/>\nUsername: -&gt; OK<br \/>\nPassword: -&gt; OK<br \/>\nDo you want to obtain your IP address automatically (DHCP) or do you want to set up your IP address manually? -&gt; Automatic<br \/>\nDo you want to obtain your DNS server address automatically or do you want to set up your DNS server address manually? -&gt; Automatic<br \/>\nDial: -&gt; OK<br \/>\nLogin script: -&gt; OK<br \/>\n<br \/>\n<strong>Yes to all ensuing prompts and you are done!!!!<\/strong>","protected":false},"excerpt":{"rendered":"<p>The following instructions are not meant to be a &#8216;how to&#8217; but a &#8216;how I did&#8217; and is based on Arjan van de Ven&#8217;s website http:\/\/www.fenrus.org\/tomtom\/ I have added a couple extra steps including modifying rfcomm.conf, registering the DUN service and specifying the bluetooth channel for DUN. These notes assume you have bluetooth already present &#8230; <a title=\"Linux Hosted Bluetooth IP Connection For TomTom\" class=\"read-more\" href=\"https:\/\/robertrath.com\/gadgetzone\/archives\/4-linux-hosted-bluetooth-ip-connection-for-tomtom.html\" aria-label=\"Read more about Linux Hosted Bluetooth IP Connection For TomTom\">Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-4","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/robertrath.com\/gadgetzone\/wp-json\/wp\/v2\/posts\/4","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/robertrath.com\/gadgetzone\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/robertrath.com\/gadgetzone\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/robertrath.com\/gadgetzone\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/robertrath.com\/gadgetzone\/wp-json\/wp\/v2\/comments?post=4"}],"version-history":[{"count":0,"href":"https:\/\/robertrath.com\/gadgetzone\/wp-json\/wp\/v2\/posts\/4\/revisions"}],"wp:attachment":[{"href":"https:\/\/robertrath.com\/gadgetzone\/wp-json\/wp\/v2\/media?parent=4"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/robertrath.com\/gadgetzone\/wp-json\/wp\/v2\/categories?post=4"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/robertrath.com\/gadgetzone\/wp-json\/wp\/v2\/tags?post=4"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}