Hi Guy,
On Sun, Dec 25, 2011 at 01:06:27PM -0800, Guy Harris wrote:
>
> On Dec 25, 2011, at 12:45 PM, Guy Harris wrote:
>
> > What Wireshark does *NOT* do is pass a non-null protocol tree pointer to
> > the dissector when loading a capture file;
>
> Or, more correctly, what Wireshark does *NOT
On Dec 25, 2011, at 12:45 PM, Guy Harris wrote:
> What Wireshark does *NOT* do is pass a non-null protocol tree pointer to the
> dissector when loading a capture file;
Or, more correctly, what Wireshark does *NOT* do is *guarantee* that the
protocol tree pointer passed to the dissector when lo
On Dec 25, 2011, at 1:50 AM, Andriy Beregovenko wrote:
> Hi Andreas,
>
> On Sun, Dec 25, 2011 at 06:35:42AM +0100, Andreas wrote:
>>
>> Wireshark passes all packets in order to the dissector, when the
>> capture is loaded. After this the dissector will get the packets in
>> arbitrary order.
>
Greetings fellow developers!
I'm a student taking Electrical Engineering specializing Computer Engineering
and am still learning a lot about Wireless and Programming.. I'm working on my
last project in University.
I now have to make a packet sniffer program which utilizes wireless adapter in
m
Hi Andreas,
On Sun, Dec 25, 2011 at 06:35:42AM +0100, Andreas wrote:
> Am 24.12.2011 14:16, schrieb Andriy Beregovenko:
> >If I open dump, select frame, and push 'END' I move to end of dump.
> >At this time all frames between first few frames and few last frames, not
> >decoded, so I can't correct
