<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>I am ShadowLord&#187; packet analysis</title>
	<atom:link href="http://iamshadowlord.com/tag/packet-analysis/feed" rel="self" type="application/rss+xml" />
	<link>http://iamshadowlord.com</link>
	<description>Interesting to me</description>
	<lastBuildDate>Mon, 26 Mar 2012 03:41:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Wireshark 1.2.0 &#8211; New Version</title>
		<link>http://iamshadowlord.com/2009/06/wireshark-1-2-0-new-version.html</link>
		<comments>http://iamshadowlord.com/2009/06/wireshark-1-2-0-new-version.html#comments</comments>
		<pubDate>Tue, 30 Jun 2009 02:32:00 +0000</pubDate>
		<dc:creator>Hans</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[packet analysis]]></category>
		<category><![CDATA[VoIP]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[wireshark]]></category>

		<guid isPermaLink="false">http://iamshadowlord.com/?p=23</guid>
		<description><![CDATA[Wireshark is a tool that performs packet and protocol analysis on a network. Packets are the virtual transport mechanism that moves are data from sender to receiver. Each packet has a header and payload &#8211; the header contains information about where the packet came from and where it&#8217;s going, as well as the protocols being [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.wireshark.org/">Wireshark</a> is a tool that performs packet and protocol analysis on a network. Packets are the virtual transport mechanism that moves are data from sender to receiver. Each packet has a header and payload &#8211; the header contains information about where the packet came from and where it&#8217;s going, as well as the protocols being used. The payload has our actual digitized data &#8211; parts of website, text, a section of photo, or a clip of audio from an MP3 or a phone call. If you don&#8217;t get all of the packets then a phone call may sound choppy or it may take a while to download a complete file. Wireshark allows you to take a look at the packets you are sending and receiving and learn a lot more about what it happening and what&#8217;s breaking down. Wireshark is not for the lighthearted, as the tool requires knowledge of protocols and a deep understanding of OSI, IP, and TCP/UDP at the very least. But, with time, Wireshark becomes invaluable to the troubleshooting process. I have relied on the tool for my work supporting Voice-over-IP (VoIP) and system and application connectivity. The only side-effect to Wireshark is that you will soon realize why it&#8217;s not a good idea to surf the web in a public spot (without a VPN or encryption).</p>
<div>
<div><a href="hhttp://www.wireshark.org/" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 186px; height: 64px;" src="http://www.iamshadowlord.com/uploaded_images/wsbadge64-744077.png" border="0" alt="" /></a></div>
<div>The <a href="http://www.wireshark.org/docs/relnotes/wireshark-1.2.0.html">new version</a> of Wireshark includes more protocols that it will decode, supports 64-bit Windows, and has GeoIP integrated support. Also, Wireshark works perfectly with my <a href="http://www.iamshadowlord.com/2007/05/passive-packet-capturing.html">passive network cable</a>. Visit <a href="http://www.wireshark.org/">www.wireshark.org </a>to download the latest version and learn more about it.</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://iamshadowlord.com/2009/06/wireshark-1-2-0-new-version.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Passive Packet Capturing</title>
		<link>http://iamshadowlord.com/2007/05/passive-packet-capturing.html</link>
		<comments>http://iamshadowlord.com/2007/05/passive-packet-capturing.html#comments</comments>
		<pubDate>Tue, 29 May 2007 18:11:00 +0000</pubDate>
		<dc:creator>Hans</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[packet analysis]]></category>
		<category><![CDATA[recieve-only]]></category>
		<category><![CDATA[sniffing]]></category>
		<category><![CDATA[wireshark]]></category>

		<guid isPermaLink="false">http://iamshadowlord.com/?p=4</guid>
		<description><![CDATA[User A to User B packet data traffic can be monitored through a HUB by User C using a “receive‑only” Ethernet cable. On the HUB end of the cable, there is a loop between TX and RX to activate the HUB port. Any traffic through the HUB will now include this port in the broadcasts. [...]]]></description>
			<content:encoded><![CDATA[<p><em>User A</em> to <em>User B</em> packet data traffic can be monitored through a HUB by <em>User C</em> using a “receive‑only” Ethernet cable.</p>
<p><a href="http://www.iamshadowlord.com/uploaded_images/Recieve_Only_Cable-757878.jpg"><img style="display: block; margin: 0px auto 10px; cursor: hand; text-align: center;" src="http://www.iamshadowlord.com/uploaded_images/Recieve_Only_Cable-757873.jpg" border="0" alt="" /></a></p>
<p>On the HUB end of the cable, there is a loop between TX and RX to activate the HUB port. Any traffic through the HUB will now include this port in the broadcasts.</p>
<p><em>User C</em> taps onto the loop by its receive pins.</p>
<p>Once the connections are made to the HUB, <em>User C</em> will receive all packets that flow through the HUB, but <em>User C</em> will not transmit any packets towards the HUB (no DHCP requests and no ARP requests).<em></em></p>
<p><em></em>The NIC on<em> User C</em> is in promiscuous mode capturing all incoming packets only.</p>
<p>Using a receive-only Ethernet cable in this configuration allows for the ability to passively capture packets, while not actively being a part of the network.</p>
<p>Network administrators can actively test for devices in promiscuous mode, monitor for DHCP and ARP requests, and review MAC tables to determine the presence of a packet analysis tool.</p>
]]></content:encoded>
			<wfw:commentRss>http://iamshadowlord.com/2007/05/passive-packet-capturing.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

