Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: Re: [Ethereal-dev] Submitting an iSNS dissector

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Ronnie Sahlberg" <ronnie_sahlberg@xxxxxxxxxxxxxx>
Date: Fri, 4 Jul 2003 00:50:02 +1000
For a new dissector a common way to get it integrated into ethereal would be
to send
a patch that add it and makes the appropriate changes to the makefiles to
this list.
Often together with a capture file that contains an example of the protocol
in question.

Currently, I belive ethereal already has a dissector for iSNS but I do not
know how complete
or functional it is since iSNS is currently a rather new and not too common
protocol.

Have you talked to Gareth Bushell   gbushell AT elipsan.com
who wrote the current ethereal dissector for iSNS?

Maybe you can join forces and work together to inprove iSNS support in
ethereal.

What is different/better with the dissector you work on?
This is a serious question since I do not know much about the current one
and nothing at all about your one.


----- Original Message -----
From: "Austin Boris Waters"
Sent: Monday, June 30, 2003 2:35 PM
Subject: [Ethereal-dev] Submitting an iSNS dissector


> Hi,
>
> I'm developing a dissector for the Internet Storage Name Service (iSNS)
> protocol that's nearing a reasonably usable state.  I'm interested in
> submitting the dissector for general use, if possible.
>
> There are a few things my dissector doesn't do (and probably won't, for a
> while).  Namely, it doesn't handle the iSNS authentication block (see
> spec. section 5.5), nor does it decode the values of funky attribute types
> (X.509 certificates, IKE messages, etc.)  in the PDU.
>
> Also, I should note that the dissector might be slightly out of date
> because iSNS is still a work in progress.  My dissector is written to be
> compliant with draft #16, released in late January, but the IETF has
> released 4 new drafts of the protocol since then (and I'm not sure exactly
> what has changed).  However, network appliance and EMC apparently are
> already developing iSNS-capable devices, since they have both unofficially
> expressed interest in acquiring the code.
>
> So, how might I go about submitting my code?  (Should I send a diff
> against the latest CVS?)
>
> Comments?
>
> Austin
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev