<?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 PA-VM Cannot ping eth1/2 internal interface in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-cannot-ping-eth1-2-internal-interface/m-p/183103#M56320</link>
    <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am running a PA VM with a VM-100 license on vmware workstation 12.5.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the mgmt interface bridged to my network and can access the PA GUI, CLI and the internet.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For my internal interface i have setup eth 1/2 to vmnet3 and unchecked the "connect as host only adapter".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also on the vmnet3 i have setup a DSL(**bleep** small linux) linux machine to simulate a client, and assigned a ping allow using int mgmt profile to the eth1/2 interface.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But yet in the end i cannot ping the interface at all, nor can i ping the dsl machine from the PA-VM.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A pcap from the PA shows that the eth1/2 interface never replies to the arp from the DSL client machine.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help is really appreciated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vmnetcfg_2017-10-22_09-54-29.png" style="width: 688px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/12033i34D212F2B62B2AF6/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="vmnetcfg_2017-10-22_09-54-29.png" alt="vmnetcfg_2017-10-22_09-54-29.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 22 Oct 2017 05:55:28 GMT</pubDate>
    <dc:creator>AllwynMascarenhas</dc:creator>
    <dc:date>2017-10-22T05:55:28Z</dc:date>
    <item>
      <title>PA-VM Cannot ping eth1/2 internal interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-cannot-ping-eth1-2-internal-interface/m-p/183103#M56320</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am running a PA VM with a VM-100 license on vmware workstation 12.5.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the mgmt interface bridged to my network and can access the PA GUI, CLI and the internet.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For my internal interface i have setup eth 1/2 to vmnet3 and unchecked the "connect as host only adapter".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also on the vmnet3 i have setup a DSL(**bleep** small linux) linux machine to simulate a client, and assigned a ping allow using int mgmt profile to the eth1/2 interface.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But yet in the end i cannot ping the interface at all, nor can i ping the dsl machine from the PA-VM.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A pcap from the PA shows that the eth1/2 interface never replies to the arp from the DSL client machine.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help is really appreciated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vmnetcfg_2017-10-22_09-54-29.png" style="width: 688px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/12033i34D212F2B62B2AF6/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="vmnetcfg_2017-10-22_09-54-29.png" alt="vmnetcfg_2017-10-22_09-54-29.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 22 Oct 2017 05:55:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-cannot-ping-eth1-2-internal-interface/m-p/183103#M56320</guid>
      <dc:creator>AllwynMascarenhas</dc:creator>
      <dc:date>2017-10-22T05:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: PA-VM Cannot ping eth1/2 internal interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-cannot-ping-eth1-2-internal-interface/m-p/183130#M56325</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It might be related to mac address issue.&lt;/P&gt;&lt;P&gt;Mgmt uses hypervisor provided mac but network interfaces not.&lt;/P&gt;&lt;P&gt;&lt;A title="https://www.paloaltonetworks.com/documentation/70/pan-os/newfeaturesguide/virtualization-features/support-for-hypervisor-assigned-mac-addresses" href="https://www.paloaltonetworks.com/documentation/70/pan-os/newfeaturesguide/virtualization-features/support-for-hypervisor-assigned-mac-addresses" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/70/pan-os/newfeaturesguide/virtualization-features/support-for-hypervisor-assigned-mac-addresses&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 22 Oct 2017 16:40:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-cannot-ping-eth1-2-internal-interface/m-p/183130#M56325</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2017-10-22T16:40:17Z</dc:date>
    </item>
  </channel>
</rss>

