Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Siginificance of pinfo->fd->flags.visited

From: Anders Broman <anders.broman@xxxxxxxxxxxx>
Date: Fri, 10 Jan 2014 09:23:12 +0000

 

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Vishnu Bhatt
Sent: den 10 januari 2014 08:59
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] Siginificance of pinfo->fd->flags.visited

 

>Hello all,

> 

>Can anyone please explain me the significance of pinfo->fd->flags.visited. I know that this variable is set to TRUE if a packet has been visited once but if we click on the same packet then why all things are done again?

 

pinfo->fd->flags.visited is FALSE on the first pass when all packets are read in sequence then it’s set to FALSE. The result of a packet dissection is thrown away as soon as the packet has been read and presented, so if you ‘click’ on a new packet the dissection has to be redone.

 

> 

>Logically if a frame has been dissected once, it should not be checked again, so condition “if(pinfo->fd->flags.visited == FALSE)” should always be checked before doing the dissection.

No true see above.

 

>Why the need of re-dissecting >the frame over and over again?

 

See above.

 

>My second doubt is that in RLC, if duplicity has already been checked then why to check it again? I mean should the duplicity function be covered under “if(pinfo->fd->flags.visited == FALSE)”?

 

 

Not sure what you are referring to here…

 

Thanks

Vishnu Bhatt





===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================