As an alternative to using the rpms, this section describes how to do things
The manual process is currently not for the faint of heart and it sure isn't as
user friendly as I want it to be. It involves patching a few programs in
your distribution (I'm working to get those patches integrated into the
upstream bluez bluetooth packages so that this will go away in the future).
Set up bluetooth, and find your tomtom with it
There are several HOWTOs on how to set up bluetooth; the simple version is:
install the various bluez rpms and make sure the bluetooth service is
started ("chkconfig --level 345 bluetooth on" in fedora, followed by a
"service bluetooth start").
With that done, a
should find your TTGO like this (the actual address will be different and
unique for each device):
# hcitool scan
00:13:AB:CD:EF:12 TomTom GO 300
(for this to work you may have to go to the options screen on your TTGO and
tell it to connect to a phone)
On my laptop this didn't actually work, and I had to do some "magic" first
to enable the bluetooth chip in a special way. This I stole directly from
one of the TomTom GPL applications; the source code for the simplified app
to do this can be found here: bluetooth_csr.c
Run "make bluetooth_csr" and then "./bluetooth_csr ON" to execute this.
After this, try the scan again.
Set your bluetooth type to be that of a phone
Edit your /etc/bluetooth/hcid.conf file and change the line that says
"class" into the following:
Telling linux to listen for incomming bluetooth connections
The TomTom wants to use a so called "DUN" connection. In linux, these are
provided by the "dund" daemon program. Unfortunately, the standard
dund program in many distributions
advertizes itself as a PC offering DUN services, while
the TomTom is looking specifically for a phone offering DUN services. I've
created a patch for the dund program that
makes it pretend to be a phone.
As of version 2.25 (released on 18/1/2006) of the bluez package, this patch is integrated
and if your bluez version is 2.25 or higher, no extra patching is required.
I start the dund program like this:
dund --dialup --listen call tomtom connect /etc/ppp/tomtom.sh
which is all that is needed, once ppp is configured correctly (see
Configuring ppp consists basically of 3 files you need to put in
Remember to make the /etc/ppp/tomtom.sh file executable with
chmod u+x /etc/ppp/tomtom.sh"
You will need to edit the /etc/ppp/peers/tomtom file to put in your own DNS
server instead of mine! (if you would have used the rpms this would have
been done automatically for you)
Port forwarding and NAT
You want your tomtom to be able to go out on the internet, for this you need
to do the following two things: (this assumes eth0 is the network
interface to your internet
connection, if it's another ethernet device you need to use that instead)
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
Note: This turns your laptop/PC into a router, so you need to be aware of
Add a "-n" option as first argument to dund, as well as the word "debug" to the end of the
above to get improved output to the screen about what is going on