Should similar changes be made to ICMPv6 request/response tracking?
- Chris
________________________________________
From: wireshark-commits-bounces@xxxxxxxxxxxxx [wireshark-commits-bounces@xxxxxxxxxxxxx] On Behalf Of sahlberg@xxxxxxxxxxxxx [sahlberg@xxxxxxxxxxxxx]
Sent: Saturday, October 06, 2012 11:06 AM
To: wireshark-commits@xxxxxxxxxxxxx
Subject: [Wireshark-commits] rev 45343: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-icmp.c
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=45343
User: sahlberg
Date: 2012/10/06 08:06 AM
Log:
ICMP request/response matching fixes
Change icmp request/response matching to be more aligned to other matching
strategies and use two tables. One table for first time we visit a packet
and a second table to track all confirmed matches.
Directory: /trunk/epan/dissectors/
Changes Path Action
+91 -39 packet-icmp.c Modified
--
CONFIDENTIALITY NOTICE: The information contained in this email message is intended only for use of the intended recipient. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately delete it from your system and notify the sender by replying to this email. Thank you.
