09-01-2011 02:14 AM
Hi
Regards,
Samarjit Das
Solved! Go to Solution.
09-01-2011 08:34 AM
Hi Samarjit,
Try with the IP Identification
Cesar R
09-01-2011 06:23 PM
Agree with Cesar, IP ID should not be changed by any intermidiate network device, the wireshark filter is
ip.id == 0x6b04, where 0x6b04 is the packet ID, you can find it under Layer 3 header.
09-01-2011 04:35 AM
There is. Look at the TCP Sequence #.
09-01-2011 04:48 AM
I believe wireshark converts all real Seq # and ACK Numbers of packet into relative numbers.Instead of displaying the real seq and Ack # in the display, Wireshark will display a seq and ack number relative to the first seen segment for that conversation. Hence always seq & ack # starts with 0.
If sniffer trace at both ends of conversation started and there would be a slight gap of start time in both ends, there won't have any option to find out how a packet will be represented in destination end.
09-01-2011 08:34 AM
Hi Samarjit,
Try with the IP Identification
Cesar R
09-01-2011 06:23 PM
Agree with Cesar, IP ID should not be changed by any intermidiate network device, the wireshark filter is
ip.id == 0x6b04, where 0x6b04 is the packet ID, you can find it under Layer 3 header.
09-01-2011 10:25 PM
Hi Cesar.
Thanks for your valuable response. I checked with ip.identification and really same packet can be identified at both sides..
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide