<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Getting started with Wireshark, the Fiddler for Ubuntu</title>
	<atom:link href="http://www.tohir.co.za/2010/02/01/getting-started-with-wireshark-the-fiddler-for-ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tohir.co.za/2010/02/01/getting-started-with-wireshark-the-fiddler-for-ubuntu/</link>
	<description></description>
	<lastBuildDate>Sun, 17 Apr 2011 18:16:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Kevin Bong</title>
		<link>http://www.tohir.co.za/2010/02/01/getting-started-with-wireshark-the-fiddler-for-ubuntu/comment-page-1/#comment-2651</link>
		<dc:creator>Kevin Bong</dc:creator>
		<pubDate>Mon, 28 Feb 2011 21:39:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.tohir.co.za/?p=349#comment-2651</guid>
		<description>I think the reason that it seems like Wireshark is truncating your response text is that you are filtering by &quot;http&quot; - which means Wireshark will only show packets that have http request or response headers, and not the following packets with the remaining data.  Two good options:
#1 - filter by &quot;tcp.port == 80&quot; instead to see all web packets
#2 (even better) Do what you did above, but instead of clicking on the response line and looking at the line based text data row you should right click on the packet and do &quot;Follow TCP stream&quot;.  This will show all the session data.</description>
		<content:encoded><![CDATA[<p>I think the reason that it seems like Wireshark is truncating your response text is that you are filtering by &#8220;http&#8221; &#8211; which means Wireshark will only show packets that have http request or response headers, and not the following packets with the remaining data.  Two good options:<br />
#1 &#8211; filter by &#8220;tcp.port == 80&#8243; instead to see all web packets<br />
#2 (even better) Do what you did above, but instead of clicking on the response line and looking at the line based text data row you should right click on the packet and do &#8220;Follow TCP stream&#8221;.  This will show all the session data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wireshark Filters &#8211; Ajax Example &#8212; Tohir Solomons</title>
		<link>http://www.tohir.co.za/2010/02/01/getting-started-with-wireshark-the-fiddler-for-ubuntu/comment-page-1/#comment-555</link>
		<dc:creator>Wireshark Filters &#8211; Ajax Example &#8212; Tohir Solomons</dc:creator>
		<pubDate>Thu, 30 Sep 2010 08:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.tohir.co.za/?p=349#comment-555</guid>
		<description>[...] blogged about Wireshark before, and how to use it for Ajax. Next is a quick tip on how to use Wireshark&#8217;s filters [...]</description>
		<content:encoded><![CDATA[<p>[...] blogged about Wireshark before, and how to use it for Ajax. Next is a quick tip on how to use Wireshark&#8217;s filters [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wireshark and [truncated] &#8212; Tohir Solomons</title>
		<link>http://www.tohir.co.za/2010/02/01/getting-started-with-wireshark-the-fiddler-for-ubuntu/comment-page-1/#comment-390</link>
		<dc:creator>Wireshark and [truncated] &#8212; Tohir Solomons</dc:creator>
		<pubDate>Mon, 10 May 2010 09:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.tohir.co.za/?p=349#comment-390</guid>
		<description>[...] posted a tutorial on how to get wireshark up and running on Ubuntu. The one problem , though, is that sometimes (actually often) you get [truncated]. How can you [...]</description>
		<content:encoded><![CDATA[<p>[...] posted a tutorial on how to get wireshark up and running on Ubuntu. The one problem , though, is that sometimes (actually often) you get [truncated]. How can you [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

