mrouter protocol specs ?

[orp]

hi

2 questions:
are there any (inofficial) mrouter protocol specs available ?


does the 7650 supports AT-commands ? if i connect to my 7650 through hyperterminal i get only an ppp configure request ?!

[egor]

It uses PPP, some details are here:
http://mobile.linux.pt/p800/
let me know if you get any further connecting to it. I'm particularly interested in file (java application) transfer

[orp]

only the first couple of packets were ppp (configuration request/response), then comes some unknown mrouter data
:-(

[egor]

That should be good enough.
Once you established PPP connection, you can work with the phone using normal IP (hopefully standard protocols)
Another option is sniffing PPP connection with something like Ethereal.
I personally managed to sniff only raw IrDA yet, I'm going to write the sniffed protocol in Ethereal format and parse it there, but it takes a while.

[orp]

i use windows, and my btooth driver contains a tool named btspy, wich is able to show the wohle traffic

after the (decodable) ppp configuration phase i get data like this

6a 00 70 00 09 ff cb 02 7e 21 45 00 00 60 00 64
00 00 0a 11 59 e4 a9 fe 01 41 a9 fe 01 08 00 35
0d 4d 00 4c 6e cf ef da 85 80 00 01 00 01 00 00
00 00 09 77 73 6f 63 6b 68 6f 73 74 07 6d 72 6f
75 74 65 72 00 00 01 00 01 09 77 73 6f 63 6b 68
6f 73 74 07 6d 72 6f 75 74 65 72 00 00 01 00 01
00 00 00 0f 00 04 a9 fe 01 44 d6 a9 7e 5c

in ascii:
j.p......!E..`.d
....Y....A.....5
.M.Ln...........
...wsockhost.mro
uter......wsockh
ost.mrouter.....
.........D...\


what type of ip (and upper) could this be ?

[egor]

No idea, this really does not look like PPP data.
Can it be afrarment of data? I mean if yu sent me the fil log i would make more sense to parse it.

[orp]

http://pro.n5home.de/log.zip

[egor]

Strangely enough your log looks completely different from what I have on my IrDA.
It does not have any PPP commands at all.
So maybe Bluetooth has some different comm protocol.

How does it work? Is it connecting to mRouterRuntime.exe? Does it install any additional drivers?

[orp]

the first couple of packets were pure ppp
for example the very first:

33 00 71 00 0b ff 5d 04 7e ff 7d 23 c0 21 7d 21
7d 21 7d 20 7d 34 7d 25 7d 26 fe 7d 3e ba 97 7d
22 7d 26 7d 20 7d 20 7d 20 7d 20 7d 27 7d 22 7d
28 7d 22 5f 81 7e 86


the first 8 and last 1 byte where btooth stuff, so you have to ignore it

so we get

7e ff 7d 23 c0 21 7d 21
7d 21 7d 20 7d 34 7d 25 7d 26 fe 7d 3e ba 97 7d
22 7d 26 7d 20 7d 20 7d 20 7d 20 7d 27 7d 22 7d
28 7d 22 5f 81 7e

and this means

7e //ppp start

ff //addr
7d 23 //ctrl
c0 21 //proto

7d 21 //code=1(confrequest)
7d 21 //id=1
7d 20 7d 34 //len=14

7d 25 //type=5
7d 26 //len=6
......
22 5f 81 //fcs

7e //stop

[egor]

Well, yes I just missed the point that Bluetooth adds some additional bytes to the packet. Now I see that almost every packet contains 7e ff 03, so they are PPP.
Some packets do not contain PPP commands, but I guess they are just part of bigger PPP junks (most probably Bluetooth splits big packets). So if we find a way to first decode Bluetooth specifc things, i.e. remove service info and merge underlying packets, we can then decode log contents as PPP.

I will try work on this in next few days, not today unfortunately.

BTW: Why are you so keen to decode it? As long as it is known that you can connect to the phone using PPP, you can just implement pppd or analogue and after that work with the phone using standard IP. That sounds more promising for using phone features. Other way is to reverse engineer mRouterRuntime.exe i.e. write a shim around it, implementing the same interfaces (it is out of process COM object) and then work with mRouter rather than with raw Bluetooth/irDA.

[orp]

i tried to decode the whole stuff, because i wont use the mrouter server (Which contains the pppd), so i had to write an own pppd

but i abandoned it, because of the unknown data

[egor]

OK, I'll keep you informed. However most likely I will either use mRouter or write own pppd

[orp]

thanks, i'm interested in your results

[Skate-Scout]

Hi,

1. The phone connect normal via PPP
2. Request from the Provided DNS (via PPP) Server the IP for the Host wsockhost.mrouter
3. The Phone connect to the IP of wsockhost.mrouter Port 3004 TCP

[BOEBOE]

Just saw this is in the wrong section.
Moved it to DCT4 Dev.

[Skate-Scout]

Hi,
im an large step wider.
1. DNS query for the Mrouter Server (DNS Provided by TCP)
2. Connect on 3004 and Inform mRouter about Port adress of auxiliary Ports (vCard, Controll, Backup)
3. Now you can use TCp for backup of vCards (already implemented by me under Linux)