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

["bunty " <bunty123_4@xxxxxxxxxxxxxx>]

 
Hello ronnie,
      Thnaks for ur valuable info to me. I am calling data_handle instead calling ip_handle there.
      But got other problem (error in dissector_add) after i add it and recompile ethereal i got  error i am giving last few lines of compliation results
>>>>>>>>>>
creating .libs/dftestS.c
(cd .libs && gcc -c -fno-builtin "dftestS.c")
rm -f .libs/dftestS.c .libs/dftest.nm .libs/dftest.nmS .libs/dftest.nmT
gcc -DINET6 "-D_U_=__attribute__((unused))" -Wall -W -g -O2 -I/usr/local/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -o .libs/dftest dftest.o util.o .libs/dftestS.o -Wl,--export-dynamic -Wl,--export-dynamic  -L/usr/local/lib wiretap/.libs/libwiretap.so epan/.libs/libethereal.so -lgmodule-2.0 -ldl -lglib-2.0 -lm -lpcap -lkrb5 -lk5crypto -lcom_err -lresolv -lz -Wl,--rpath -Wl,/usr/local/lib
creating dftest
(cd doc ; \
make ../ethereal-filter.4 )
make[3]: Entering directory `/home/bunty/ethereal-0.10.10/doc'
../tethereal -G fields | /usr/bin/perl ./dfilter2pod.pl ./ethereal-filter.pod.template > ethereal-filter.pod

** ERROR **: file packet.c: line 647 (dissector_add): assertion failed: (sub_dissectors)
aborting...
/usr/bin/pod2man                    \
--section=4 \
--center="The Ethereal Network Analyzer" \
--release=0.10.10                        \
ethereal-filter.pod > ../ethereal-filter.4
make[3]: Leaving directory `/home/bunty/ethereal-0.10.10/doc'
(cd doc ; \
make ../ethereal-filter.html )
make[3]: Entering directory `/home/bunty/ethereal-0.10.10/doc'
/usr/bin/pod2html                    \
--title="ethereal-filter - The Ethereal Network Analyzer 0.10.10" \
--noindex                                \
ethereal-filter.pod > ../ethereal-filter.html
>>>>>>>>>>>>>>>>>>>

How to solve this problem?
regards,
bunty.

On Fri, 27 May 2005 ronnie sahlberg wrote :
>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
> >
> >
> >