Re: [tipc-discussion] Subdissectors for Wireshark Plug-in

[Martin P. <mar...@go...>]

Hi Randy,

> > i just wanted to announce that I uploaded the Wireshark changes for
> > reassembling fragmented TIPCv2 packages. The dissector also tries to
> > call heuristic dissectors for encapsulated protocols now. Until they
> > release version 0.9.7 one has to grab the sources from SVN in order to
> > use the changes.
>
> That's great, I make time to try that in the next week or so.

In case you're using or planning to use subdissectors - which field
name suits you best to call it, tipc.usr, tipcv2.port_name_type or is
it better to do it the heuristic way? Do you see any need to add or
enhance anything?

> The wireshark connection info will be very useful.

That'd be my next task.

> > I still have *not* received *any* traces for TIPC 1.7 to enhance the
> > dissector for it.
>
> > Is nobody using Wireshark for tracing?
>
> I use the tipc disector in wireshark many times a week - it's
> really appreciated.

Now we're officially three ;-)

> I can send you tipc-1.5.12 connection oriented traces if you like.
> Let me know.

That'd be great!

> If you don't get any 1.7 traces, I'll set up a two node vmware
> cluster, install tipc-1.7 and get you some data.

Don't worry - if there's nobody right now in need of the 1.7 changes
that would be a waste of *your* time, I'll do the connection stuff
first and one day I'll install 1.7 myself.

Martin