<?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 Re: Multiple bridged VMs on host - host and server on same VLAN - ACL on physical switch in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Multiple-bridged-VMs-on-host-host-and-server-on-same-VLAN-ACL-on/m-p/2846084#M169935</link>
    <description>&lt;P&gt;I rarely use "Bridged" connections, so please consider the following suggestions more as a guess.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Configure the bridged network (vmnet0) in the Virtual Network Editor with a dedicated NIC, rather then Automatic.&lt;/LI&gt;
&lt;LI&gt;Modify the VMs' network settings, and try whether enabling/disabling “Replicate physical network connection state” on all VMs makes a difference.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;André&lt;/P&gt;</description>
    <pubDate>Sat, 08 May 2021 10:22:23 GMT</pubDate>
    <dc:creator>a_p_</dc:creator>
    <dc:date>2021-05-08T10:22:23Z</dc:date>
    <item>
      <title>Multiple bridged VMs on host - host and server on same VLAN - ACL on physical switch</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Multiple-bridged-VMs-on-host-host-and-server-on-same-VLAN-ACL-on/m-p/2846059#M169930</link>
      <description>&lt;P&gt;Hello!&amp;nbsp; First time poster; nice to meet everyone!&lt;/P&gt;&lt;P&gt;I've attached a small generic diagram of my setup.&amp;nbsp; A brief summary in words:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;I am using Workstation Pro on my host for 3x VMs (Windows all around).&lt;/LI&gt;&lt;LI&gt;All 3x VMs are bridged and on vmnet0.&lt;/LI&gt;&lt;LI&gt;The host machine and a server are connected to a physical switch.&lt;/LI&gt;&lt;LI&gt;All machines - host, server, VMs - are IP'd in the same subnet.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I have an ACL on the switch port that the host is connected to (host port).&amp;nbsp; Due to the Cisco IOS vintage, the ACL is "in" only on the host port.&amp;nbsp; The switch port the server is connected to has no ACL.&amp;nbsp; In short, I want to only allow pings from the VMs to the server (and vice versa) to test connectivity.&amp;nbsp; I have a one-way UDP stream from the server that should get through to the VMs since that is "out" traffic on the host port; ACL shouldn't affect it.&amp;nbsp; There is also VM-to-VM database communication (TCP and UDP, several ports).&lt;/P&gt;&lt;P&gt;The problem I am running into seems to be that the ACL is affecting the VM-to-VM communication.&amp;nbsp; Is this what one should expect?&amp;nbsp; The documentation diagrams that describe virtual bridged networking all show a virtual switch with multiple ports and describe connecting multiple VMs to the same virtual switch / vmnet, so I expected ordinary switch functionality in that case.&amp;nbsp; I understand that the virtual switch is limited in functionality, but shouldn't it still contain all VM-to-VM communication such that the ACL would have no effect?&amp;nbsp; Or do I have a fundamental misunderstanding about how the virtual switch works and VM-to-VM traffic really all travels out the host NIC, to the physical switch "in", "out" back through the physical switch, back through the host NIC, and then to the VMs?&lt;/P&gt;&lt;P&gt;Please let me know what your questions are... I'm sure I'm less than clear as a newbie on this forum.&amp;nbsp; &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&amp;nbsp; Thank you all in advance for the help!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 May 2021 23:08:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Multiple-bridged-VMs-on-host-host-and-server-on-same-VLAN-ACL-on/m-p/2846059#M169930</guid>
      <dc:creator>kent_ridl</dc:creator>
      <dc:date>2021-05-07T23:08:44Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple bridged VMs on host - host and server on same VLAN - ACL on physical switch</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Multiple-bridged-VMs-on-host-host-and-server-on-same-VLAN-ACL-on/m-p/2846084#M169935</link>
      <description>&lt;P&gt;I rarely use "Bridged" connections, so please consider the following suggestions more as a guess.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Configure the bridged network (vmnet0) in the Virtual Network Editor with a dedicated NIC, rather then Automatic.&lt;/LI&gt;
&lt;LI&gt;Modify the VMs' network settings, and try whether enabling/disabling “Replicate physical network connection state” on all VMs makes a difference.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Sat, 08 May 2021 10:22:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Multiple-bridged-VMs-on-host-host-and-server-on-same-VLAN-ACL-on/m-p/2846084#M169935</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2021-05-08T10:22:23Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple bridged VMs on host - host and server on same VLAN - ACL on physical switch</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Multiple-bridged-VMs-on-host-host-and-server-on-same-VLAN-ACL-on/m-p/2846315#M169958</link>
      <description>&lt;P&gt;Hi, André!&lt;/P&gt;&lt;P&gt;Each VM is already configured for a dedicated NIC, not Automatic.&amp;nbsp; But we haven't tried the Replicate option yet... thank you for the suggestion.&lt;/P&gt;</description>
      <pubDate>Mon, 10 May 2021 13:07:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Multiple-bridged-VMs-on-host-host-and-server-on-same-VLAN-ACL-on/m-p/2846315#M169958</guid>
      <dc:creator>kent_ridl</dc:creator>
      <dc:date>2021-05-10T13:07:16Z</dc:date>
    </item>
  </channel>
</rss>

