Very good question! I'm also looking for this same information to add
support for JXTA conversations.
When you do get an answer I'd be happy to help with writing a new
README.developer section on this topic.
Mike
Manu Pathak wrote:
Still hoping somebody can help me out on this one...
Essentially, I need to know what needs to be done to generate
RSVP related information apart from adding the regular conversation
stuff described in README.developer. I would have thought that the
task would be analogous to how we handle things to the IPv4
dissector from the Ethernet frame, but I haven't been able to
figure this out so far:(.
Thanks in advance for any help! Regards,
Manu
-------- Original Message --------
Date: Thu, 26 May 2005 14:48:32 -0400
From: Manu Pathak <mapathak@xxxxxxxxx>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Hi,
I am working on adding support for RSVP conversations to Ethereal,
and using the IP conversations code as the example to follow. So
far:
- I have added the gtk/conversations_rsvp.c and gtk/hostlist_rsvp.c
files and successfully got an RSVP entry in the conversations list
and the conversations tab. To do this, I also edited packet-rsvp.h
to define the rsvphdr structure.
- Added conversation stuff to packet-rsvp.c as described in the
README.developer file. I am reasonably sure I have made all the
changed described in Section 2.2 of that document, which deals
with conversations. I also populate the rsvphdr structure in
this file and have added the conversation specific initialization
routine. For what it's worth, I used the conversations code
in packet-afs.c and packet-beep.c as example to make these
changes [As an aside, I could not find where the conversations for
these protocols are available in the GUI; I would have expected
them with the rest, but they don't seem to be there. Why is that
the case?].
Unfortunately, when I load the sample RSVP capture file from
the Ethereal Wiki page, I still don't see any information in the
RSVP tab (though the Ethernet and IPv4 tabs have the information
as one would expect). Clearly, I am missing something here. I
think it has to do with the fact that somehow I need to add some
code somewhere which would be responsible for calling the RSVP
subdissector. I added something like the following to packet-rsvp.c
but it did not do the trick:
rsvp_dissector_table =
register_dissector_table("rsvp.proto", "RSVP Protocol",
FT_UINT8, BASE_DEC);
register_heur_dissector_list("rsvp", &heur_subdissector_list);
Can anybody tell me what I am missing? Thanks,
Manu