<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Track a packet in source &amp; destination end sniffer captures in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792699#M35530</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Agree with Cesar, IP ID should not be changed by any intermidiate network device, the wireshark filter is &lt;/P&gt;&lt;P&gt;ip.id == 0x6b04, where 0x6b04 is the packet ID, you can find it under Layer 3 header.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Sep 2011 01:23:11 GMT</pubDate>
    <dc:creator>Ahmad Basel Jaber</dc:creator>
    <dc:date>2011-09-02T01:23:11Z</dc:date>
    <item>
      <title>Track a packet in source &amp; destination end sniffer captures</title>
      <link>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792695#M35526</link>
      <description>&lt;P&gt;&lt;SPAN style="font-family: comic sans ms,sans-serif;"&gt;Hi &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;&lt;SPAN style="font-family: comic sans ms,sans-serif;"&gt;I have taken sniffer capture at both&amp;nbsp; ends(source &amp;amp; destination) of communication but how can I track a single&amp;nbsp; packet from both sides of capture. Is there any unique #&amp;nbsp; tagged into the packet&amp;nbsp; from which it can be identified that this is the packet reaching the destination&amp;nbsp; side capture which was sent by source.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: comic sans ms,sans-serif;"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: comic sans ms,sans-serif;"&gt;Samarjit Das&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2011 09:14:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792695#M35526</guid>
      <dc:creator>samarjitdas</dc:creator>
      <dc:date>2011-09-01T09:14:06Z</dc:date>
    </item>
    <item>
      <title>Track a packet in source &amp; destination end sniffer captures</title>
      <link>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792696#M35527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is. Look at the TCP Sequence #.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Sep 2011 11:35:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792696#M35527</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2011-09-01T11:35:04Z</dc:date>
    </item>
    <item>
      <title>Track a packet in source &amp; destination end sniffer captures</title>
      <link>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792697#M35528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe wireshark converts all real Seq #&amp;nbsp; and ACK Numbers of packet&amp;nbsp; into relative numbers.Instead of displaying the real seq and Ack # in&amp;nbsp; the display, Wireshark will display a seq and ack number relative to the first&amp;nbsp; seen segment for that conversation. Hence always seq &amp;amp; ack # starts with 0. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If sniffer trace at both ends of conversation started and there would be a slight gap of start time in both ends, there&amp;nbsp; won't have any option to find out how a packet will be represented in destination end.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Sep 2011 11:48:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792697#M35528</guid>
      <dc:creator>samarjitdas</dc:creator>
      <dc:date>2011-09-01T11:48:35Z</dc:date>
    </item>
    <item>
      <title>Track a packet in source &amp; destination end sniffer captures</title>
      <link>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792698#M35529</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Samarjit,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try with the IP Identification &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cesar R&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Sep 2011 15:34:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792698#M35529</guid>
      <dc:creator>Cesar Roque</dc:creator>
      <dc:date>2011-09-01T15:34:43Z</dc:date>
    </item>
    <item>
      <title>Track a packet in source &amp; destination end sniffer captures</title>
      <link>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792699#M35530</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Agree with Cesar, IP ID should not be changed by any intermidiate network device, the wireshark filter is &lt;/P&gt;&lt;P&gt;ip.id == 0x6b04, where 0x6b04 is the packet ID, you can find it under Layer 3 header.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2011 01:23:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792699#M35530</guid>
      <dc:creator>Ahmad Basel Jaber</dc:creator>
      <dc:date>2011-09-02T01:23:11Z</dc:date>
    </item>
    <item>
      <title>Track a packet in source &amp; destination end sniffer captures</title>
      <link>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792700#M35531</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Cesar.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your valuable response. I checked with ip.identification and really same packet can be identified at both sides.. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2011 05:25:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/track-a-packet-in-source-destination-end-sniffer-captures/m-p/1792700#M35531</guid>
      <dc:creator>samarjitdas</dc:creator>
      <dc:date>2011-09-02T05:25:54Z</dc:date>
    </item>
  </channel>
</rss>

