ds
Ilya 'Akhil' Shvetsov
On 7 February 2013 22:14, Christopher Maynard wrote:
> Ilya Shvetsov writes:
>
> > But I have to mention, that if i use proto_tree_set_visible, my dissector
> fails to link. May be this happens because proto_tree_set_visible are not
>
using proto_tree_set_visible. I found examples packet-frame.c
and in packet-wsp.c
--
With best regards
Ilya 'Akhil' Shvetsov
On 7 February 2013 01:29, Jaap Keuter wrote:
> On 02/06/2013 01:08 PM, Ilya Shvetsov wrote:
> > Hi, there.
> >
> > Thank you guys for great
Hi, there.
Thank you guys for greate product.
I successuly wrote my dissector and few days ago found failure in it.
I have next situatioin:
I dissect last packet in some sequence and get new tvbuffer from
process_reassembled_data
Next step i do is parsing of this new tvbuffer.
I parse it and ad
i would like to point user attention
on this moment.
i hope, this sheds more light on what really i want
--
With best regards
Ilya 'Akhil' Shvetsov
> Thanks,
> Jaap
>
> Send from my iPhone
>
> On 19 apr. 2012, at 11:17, Ilya Shvetsov wrote:
>
> Hi, there!
>
>
Hi, there!
I wroute my own dissector for our custom protocol. It works good. we are
very satisfied with wireshark.
But now i have task to check our protocol for errors. we implemented
reliable protocol over UDP, so we would like to check whether we have lost
packet or not. whether all packet's se
Hi, there!
I use wireshark 1.6.7 to build my dissector.
And found that if packets have same source and destination address, they
reassembled incorrectly.
this happens because fragment_key contains only addresses (src and dest)
and does not contains ports.
What is the best way to deal with this i
