Hi,
You can build your plugin from several .c files so I think it would be possible 
to have only one .dll
with the protocols separated but if you want two that should work too.
Regards
Anders

________________________________

From: [email protected] 
[mailto:[email protected]] On Behalf Of Aurélien Decagny
Sent: den 23 juli 2009 12:15
To: [email protected]
Subject: Re: [Wireshark-dev] Using multiple layers of dissectors


Hi,

I thought that if there is 2 protocols, I should create 2 plugins. So if one 
protocol evolve, or is replaced, we only have to change one dissector, and we 
won't need to change the other. I thought it would be easier.
And so in the tree, where the data are dissected, we would have two lines: one 
for each protocol. In fact like for the Ethernet / IP / TCP...
Is it possible to do that with only one dissector?

And the two protocols are:

ASN.1 described protocol <= protocol used to transform satellite data into 
something understandable by all space agencies.
ISP <= little protocol used to transfer the data, make the bind and send 
Heartbeat messages to maintain connexion.
TCP
IP
...

For the ASN.1, I have already made a C program which transform data in ASN.1 
into something I can display. Now, I just need to adapt this program for 
Wireshark. So I think it would be easier to use directly this, as I know how to 
use it and which parameters have to be selected by the user in Wireshark.

As the ISP protocol is specified by the OSI, I think it's not a 
private/proprietary protocol. Where can I send the code? By the mailing list? 
In fact there is almost nothing for the ISP protocol, so I won't be sure that 
it will help you if I send you my dissector.

Regards
Aurelien


________________________________

Date: Thu, 23 Jul 2009 11:25:33 +0200
From: [email protected]
To: [email protected]
Subject: Re: [Wireshark-dev] Using multiple layers of dissectors


Hi,
The ASN1 plugin is sort of deprecated (plugins/asn1/) and I think it is 
supposed to work by loading ASN1 descriptions via som external tool
if I remember correctly. The dissectors generated by asn2wrs relies on 
packet-per.c or packet-ber.c to do the dissection depending
on the encoding(PER/BER).
 
Why would you need two .dll:s? 
Is the protocol private/proprietarry? If not make it a built in dissector and 
send us the code(which protocol is it?).
 
As ASN1 is used to describe a protocol is the stack more like:
 
Satelite Message
ASN.1 described protocol
TCP
IP
:
If so you'll need two dissectors I suppose one for the ASN1 protocol and one 
for the satelite message they could be in the same
plugin dll ( see other plugins with multiple files). 
Regards
Anders

________________________________

From: [email protected] 
[mailto:[email protected]] On Behalf Of Aurélien Decagny
Sent: den 23 juli 2009 10:48
To: [email protected]
Subject: Re: [Wireshark-dev] Using multiple layers of dissectors


Hi,
thank you for your answer.

In fact, my question was more: is it possible to create 2 different plugins (2 
different .dll files on windows), to dissect something like this:
http://imagik.fr/view-rl/93396
(A figure is better than a long explanation, and I know that this figure is not 
really accurate for the transmission layer.)

But thank you for your link! I was trying to build the ASN.1 plugin by myself 
when I saw that he was already integrated in Wireshark, so your link will help 
me a lot!

Regards

Aurelien





________________________________

Date: Thu, 23 Jul 2009 10:24:22 +0200
From: [email protected]
To: [email protected]
Subject: Re: [Wireshark-dev] Using multiple layers of dissectors


Hi,
You should use asn2wrs to generate the asn1 part of your protocol see
http://wiki.wireshark.org/Asn2wrs and a bunch of asn2wrs generated dissectors 
in the source dir /asn1/
 
Regards
Anders

________________________________

From: [email protected] 
[mailto:[email protected]] On Behalf Of Aurélien Decagny
Sent: den 23 juli 2009 10:11
To: [email protected]
Subject: [Wireshark-dev] Using multiple layers of dissectors


Hi!

I have been searching this on Internet, but I don't find any solution, this is 
why I write to you.
I have built a first dissector for Wireshark. Now, I know that for some kind of 
messages from this protocol, the data it contains are encoded with an other 
protocol (ASN.1, to be accurate).
So I would like to know what I have to put in my dissector code and where, to 
make the data dissected by the ASN.1 dissector.

Thanks

Aurelien


________________________________

Votre correspondant a choisi Hotmail et profite d'un stockage quasiment 
illimité. Créez un compte Hotmail gratuitement ! 
<http://www.windowslive.fr/hotmail/default.asp> 

________________________________

Découvrez toutes les possibilités de communication avec vos proches 
<http://www.microsoft.com/windows/windowslive/default.aspx> 

________________________________

Souhaitez vous  « être au bureau sans y être » ? Oui je le veux ! 
<http://www.microsoft.com/france/windows/bts/default.mspx>  
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to