From: Jon M. <jon...@er...> - 2004-06-08 14:47:33
|
Hi, There is only one number now, 0x88ca, which has been registered with IEEE as the official TIPC protocol number. The two numbers we were using earlier were not properly registered, and can hence not be used in open environments. And, as Mark said, the separation between the two is now done in tipc_recv_msg. I don't know about tipcdump, but you should perhaps have a look at the ethereal module we used in TIPCv1 (attached). If we refurbish this one, we could make it available at SF. Regards /jon Yin, Hu wrote: >Hello Jon and Mark, > >Now I'm trying to enable tipcdump to work on TIPCv2, which developed by >Ling Xiaofeng and can work on TIPCv1. >Through investigating I find maybe you have changed the number of TIPC >configuration protocol from 0x0807 >to 0x88ca and the number of TIPC message protocol from 0x0807 to 0x0800, >thus tipcdump cannot scratch the >package with different protocol number at the same time. And we cannot >distinguish the TIPC package from the >general IP package if we use protocol number 0x0800. Is that correct? If >it was correct how can we solve this >problem? Thank you in advance! > >Best Regards, > >Nick > > |