Ethereal-dev: Re: [Ethereal-dev] why ethereal is unable to go through my dissector?

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

From: ronnie sahlberg <ronniesahlberg@xxxxxxxxx>
Date: Fri, 27 May 2005 08:05:51 +1000
is IP the only protocol ever to be transported ato your dissector/protocol?

if so   you should just search for the IP handle  (see examples in  packet-vj.c)

ip_handle  = find_dissector("ip")
and then just call it through that handle.

...
call_dissector(ip_handle, ...


examples also available in packet-vj.c


if there are other protocols also possible in addition to ip   then
you will have
to create a dissector table and let ip and the others register with it.
in that case   grep for   register_dissector_table() and see how it is used.


On 26 May 2005 09:34:11 -0000, bunty <bunty123_4@xxxxxxxxxxxxxx> wrote:
> 
> 
>  Hello all,
>            I tried a lot and nobody also even helped me in adding new
> dissector to ethereal. so i decided to ask a general question hoping nobody
> will again point me to read README.developer.
>            I want to ask that I am getting packet from Ethernet layer to my
> protocol layer but unable to transfer control to IP layer from my layer
> instead it goes to data layer that mean after displaying Ethernet then my
> new header it start to display remaining part in packet as data. Where am i
> wrong. I have alredy sent my source but not got any reply. so i expect
> genereal answer to my question.
>  Thanks everbody for reading my question.
>  regards,
>  bunty.
>  
> 
>  
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
> 
> 
>