Guy Harris wrote:
>
> > > now i wonder how i can register a protocoll if there is no standard port
> > > associated to it. or it is not using this standard port at the moment.
> >
> > Unfortunately we do not have a way yet. We are close, though.
> > We have the ability for protocol dissectors register the fact that they
> > need to be called in certain situatoins (tcp port number, for example).
>
> That might be sufficient in some cases, e.g. if two machines use
> protocol X, running on some standard port, to set up a subsequent
> conversation using protocol Y, running on some port agreed to by the
> machines as part of the protocol X dialog, so that the protocol X
> dissector could then use "dissector_add()" to specify that the port in
> question should be used for protocol Y.
>
> Some streaming media protocol do this, I think, for example.
exactly this is what i would need for one of the protocolls that i would like
to add. we have a port where the port for further comunication is negotiated.
os if one dissector can add and remove another dissector for a port/protocoll
pair it is fine for us.
> In addition, 0.8.7 includes a mechanism by which a dissector can specify
> that a particular TCP or UDP conversation, in the sense of "traffic
> between machine A/port X and machine B/port Y", should be dissected with
> some particular protocol's dissector.
>
> However, as you note, if there's no way for Ethereal to know that port A
> should be used for protocol Y, or for conversation Z, other than the
> user telling it so, there's currently no mechanism for doing that.
the other protocoll would need exactly this dialog to say please
start using protocoll xxx on this tcp stream.
--
---------------- PI equals 3 at least for small PI and large 3 ----------------
Andre Schroeter
Deutsches Krebsforschungszentrum tel.: (+49) 6221 - 42 2382
Division Medical and Biological Informatics fax.: (+49) 6221 - 42 2345
Im Neuenheimer Feld 280 url: http://mbi.DKFZ-Heidelberg.de/
D-69120 Heidelberg, Germany e-mail: A.Schroeter@xxxxxxxxxxxxxxxxxx
-------------------------------------------------------------------------------
