Downunder35m wrote:The above models and all other/upcoming models based on Navcore 10.xxx/11.xxx use a modified Linux filesystem, which can not be accessed by the user
other than using the "MyTomTom" application for PC/Mac.
This means neither is it possible to copy/install any files to these models, nor is it possible to patch these Navcores.
(Note: It is basically possible to patch the installation files before they are installed on the device, but it is still useless until there is a way to access the filesystem from the PC/Mac)
If there is any change you will be notified in this posting.
Anyone here interested in trying "fix" this problem?
I bought a 1000/2405 yesterday and was pissed
when I discovered the device was not visible as a Windows drive. However, MyTomTom can talk to it, so it is obviously possible to do so. I've learned a very
little bit about how it does this, which I will post here. If anyone else is interested in this project, I suggest we work together.
The little I have learned
With MyTomTom running, it listens for TomToms on 127.0.0.1:4000 by default.
If you connect a TomTom, there is initial back and forth on 127.0.0.1. Soon thereafter a second connection is established. This one is on an [Please Register or Login to download file]
virtual ethernet link that serves as the TomTom connection to Windows.
On my computer, the TomTom has the address 169.254.255.1, and the RNDIS virtual adapter has 169.254.255.2. The RNDIS adapter is used by by a number of (system) processes other than MyTomTom, which may or may not matter. I don't know yet.
I am presently capturing a navcore and a map update between MyTomTom and my new gps on both 127.0.0.1 and 169.254.255.2. I won't look at the captures until they are finished, but will post anything I learn.
Some bad news
The popular packet sniffer Wireshark can't
sniff the Windows loopback interface because of the way the loopback interface is wedged into the network stack. It can
sniff the RNDIS interface, but it is hard to get the initial traffic. That may or may not matter, don't know yet.
There are some Windows workarounds mentioned on the Wireshark wiki, but they are unappealing so I have not yet tried them.
Some potential good news
sniff the loopback interface on Macs, so anyone with a Mac has the benefit of all of [Please Register or Login to download file]
delicious gui niceness and smarts. Mac's probably don't use RNDIS either, which is a bonus.
My current setup
I'm keeping an eye on TCP ports with NirSoft's CurrPorts [Please Register or Login to download file]
. A [Please Register or Login to download file]
is available too.
I'm using a simple command line program, [Please Register or Login to download file]
, to capture packets on both interfaces.
Once I have finished the capture, I will start drilling through the packets with Wireshark [Please Register or Login to download file]
. It is also available in a [Please Register or Login to download file]
More in the next few days.