TomTom IP Stack Over Bluetooth

I finally managed to get a working IP stack from the TomTom One to my PC working…

I ended up using rfcomm and running ppp over it. I would have preferred to use PAN but that didn’t look like a goer from the stock TomTom kernel.

Unfortunately devpts was also omitted from the kernel, so I’m going to have to get a little creative with the pseudo terms.

Here’s a quick teaser before I package it all up with a telnet daemon..

This is from the TomTom Side..

dund[175]: New connection from 00:0B:0D:60:37:75
Using interface ppp0
Connect: ppp0 <--> /dev/rfcomm0
Deflate (15) compression enabled
local IP address 10.10.10.10
remote IP address 10.10.10.11
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ppp0 Link encap:Point-Point Protocol
inet addr:10.10.10.10 P-t-P:10.10.10.11 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:75 (75.0 B) TX bytes:69 (69.0 B)

And this from the Pc side..

[jim@molly sbin]$ sudo dund –search -n
Password:
dund[20313]: Bluetooth DUN daemon
dund[20313]: Inquiring
dund[20313]: Searching for LAP on 00:0D:93:16:FA:D0
dund[20313]: Failed to connect to the SDP server. Connection timed out(110)
dund[20313]: Searching for LAP on 00:0E:07:B3:D6:05
dund[20313]: Searching for LAP on 00:60:57:EA:4F:2C
dund[20313]: Searching for LAP on 00:13:6C:3D:84:1D
dund[20313]: Connecting to 00:13:6C:3D:84:1D channel 1
dund[20313]: Connection established
[jim@molly sbin]$ Using interface ppp0
Connect: ppp0 <--> /dev/rfcomm0
Deflate (15) compression enabled
local IP address 10.10.10.11
remote IP address 10.10.10.10

Comments are closed.