<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Vlan on The IT Hollow</title>
    <link>https://theithollow.com/tags/vlan/</link>
    <description>Recent content in Vlan on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 16 Mar 2012 13:00:27 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/vlan/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VMware Network Traffic Routing</title>
      <link>https://theithollow.com/2012/03/16/vmware-network-traffic-routing/</link>
      <pubDate>Fri, 16 Mar 2012 13:00:27 +0000</pubDate>
      <guid>https://theithollow.com/2012/03/16/vmware-network-traffic-routing/</guid>
      <description>&lt;p&gt;VMware has lots of ways to setup networking on their ESXi hosts.  In order to set this up in the best way for your needs, it&amp;rsquo;s important to understand how the traffic will be routed between VMs, virtual switches, physical switches and physical network adapters.&lt;/p&gt;
&lt;p&gt;Before looking at an example, we should review some networking 101.  Machines on the same vlan on the same switch can communicate with one another (assuming there is no firewall type devices in the way).  Machines on different vlans on the same switch cannot communicate unless the traffic passes through a router.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
