Hi Bill:
It doesn't sound like anyone's rushing forward to answer your email ...
probably because there aren't many TIPC users who have much experience
with Wireshark. You might want to get in touch with Martin Peylo
([EMAIL PROTECTED]), who was (I believe) the last person to work
on the TIPC dissector about a year ago.
You might also want to try posting your query on a Wireshark-related
mailing list.
Regards,
Al
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Kinahan, William P SIK
Sent: Thursday, September 13, 2007 10:38 AM
To: [email protected]
Subject: [tipc-discussion] Subdissectors for Wireshark Plug-in
I'm trying to build a dissector plug-in for my protocol which
utilizes TIPC. It appears that the current TIPC package for Wireshark
doesn't support heuristic subdissectors. Has anyone out there built one
of these? Would you be willing to share your solution or suggestions? My
goal is to key off the "tipcv2.port_name_type" field which will trigger
my dissector.
I've tried emulating what I see in the UDP package provided with
Wireshark, but I'm unable to get it working.
Bill Kinahan
Chief Software Architect
Sikorsky Aircraft
(203)386-3551
Fax (860)998-5575
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
