<?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>cyborgworkshop.org &#187; Networking</title>
	<atom:link href="http://cyborgworkshop.org/category/networking/feed/" rel="self" type="application/rss+xml" />
	<link>http://cyborgworkshop.org</link>
	<description>Blurring the line</description>
	<lastBuildDate>Wed, 22 Feb 2012 14:31:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>802.1q vlan pass-thru with ESXi</title>
		<link>http://cyborgworkshop.org/2009/02/04/8021q-vlan-pass-thru-with-esxi/</link>
		<comments>http://cyborgworkshop.org/2009/02/04/8021q-vlan-pass-thru-with-esxi/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 04:47:13 +0000</pubDate>
		<dc:creator>jason</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[802.1q]]></category>
		<category><![CDATA[pass through]]></category>
		<category><![CDATA[pass-thru]]></category>
		<category><![CDATA[vlan]]></category>

		<guid isPermaLink="false">http://cyborgworkshop.org/2009/02/04/8021q-vlan-pass-thru-with-esxi/</guid>
		<description><![CDATA[Getting 802.1q vlans out of a virtual machine and into the wild world beyond,]]></description>
			<content:encoded><![CDATA[<p>ESXi 3.5 only allows 4 virtual NICs to be assigned to a virtual machine. For many uses, that&#8217;s just fine, but my latest overly complex home network requires for 5 wireless network, 3 wired networks, 2 storage networks and a public hotspot type network. That&#8217;s no less then 11 network interfaces.  Fortunately, I have the hardware to handle 802.1q vlans. Unfortunately, vmware doesn&#8217;t seem to like passing 802.1q headers through the vmnics and into the outside world.  I spent a fair amount of time with a sniffer trying to figure this situation out and came across a white paper that saved my bacon.  When you create a virtual interface in the VI Client, you have to set it to use vlan 4095 if you plan on using it as a pass-thru trunk interface. If you don&#8217;t, none shall pass.  How frustrating is that?<br />
Hey VMWare, consider this a feature request. How about a flipping check box labeled &#8220;Pass-Thru Interface&#8221; instead of a white paper buried on under the interwebs?</p>
<p><em>update</em> The latest ESXi configuration guide mentions this on page 30 <a rel="nofollow" href="http://www.vmware.com/pdf/vi3_35/esx_3i_e/r35/vi3_35_25_3i_server_config.pdf">http://www.vmware.com/pdf/vi3_35/esx_3i_e/r35/vi3_35_25_3i_server_config.pdf</a></p>
]]></content:encoded>
			<wfw:commentRss>http://cyborgworkshop.org/2009/02/04/8021q-vlan-pass-thru-with-esxi/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Perform a ping sweep using nmap</title>
		<link>http://cyborgworkshop.org/2009/01/13/perform-a-ping-sweep-using-nmap/</link>
		<comments>http://cyborgworkshop.org/2009/01/13/perform-a-ping-sweep-using-nmap/#comments</comments>
		<pubDate>Tue, 13 Jan 2009 15:44:40 +0000</pubDate>
		<dc:creator>jason</dc:creator>
				<category><![CDATA[Best Tools]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[icmp]]></category>
		<category><![CDATA[nmap]]></category>
		<category><![CDATA[ping scan]]></category>
		<category><![CDATA[scan]]></category>

		<guid isPermaLink="false">http://cyborgworkshop.org/?p=198</guid>
		<description><![CDATA[nmap is a really excellent  network tool that most folks are familiar with.  I find that I tend to use it to first discover hosts on a network and then to get more specific information from a targeted node. The first part of that discovery is the ping sweep, which can be done thusly. nmap [...]]]></description>
			<content:encoded><![CDATA[<p>nmap is a really excellent  network tool that most folks are familiar with.  I find that I tend to use it to first discover hosts on a network and then to get more specific information from a targeted node. The first part of that discovery is the ping sweep, which can be done thusly.</p>
<blockquote><p>
nmap -sP 192.168.1.1-254
</p></blockquote>
<p>Pretty simple.  192.168.1.1 is the start IP and 192.168.1.254 is the stop IP. nmap will ping every address in that range and return the IP of hosts that respond. </p>
]]></content:encoded>
			<wfw:commentRss>http://cyborgworkshop.org/2009/01/13/perform-a-ping-sweep-using-nmap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

