<?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 VM series firewalls and interfaces in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/vm-series-firewalls-and-interfaces/m-p/1228702#M124243</link>
    <description>&lt;P&gt;Howdy all&lt;/P&gt;
&lt;P&gt;I have deployed 2 VM series firewalls in VMware workstation pro but I can't get their dataplane interfaces to ping each other. I'm sure this has to do with how to configure the network adapters.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have no issues accessing the GUIs/ Management interfaces and they can ping each other as these interfaces are bridged in Vmware workstation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;dataplane interfaces should be able to ping each other, as that is the purpose of LAN segment, to put them on an isolated network so the VMs can see each other on the network. I want to do this that I can play with routing only between these 2 VM firewalls.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so from eth1/1 PAVM1 to eth1/1 PAVM2,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;admin@PA-VM&amp;gt; ping source 99.99.99.1 host 99.99.99.2&lt;BR /&gt;PING 99.99.99.2 (99.99.99.2) from 99.99.99.1 : 56(84) bytes of data.&lt;BR /&gt;^C&lt;BR /&gt;--- 99.99.99.2 ping statistics ---&lt;BR /&gt;5 packets transmitted, 0 received, 100% packet loss, time 128ms&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;pavm1&lt;/P&gt;
&lt;P&gt;Network Adapter 1 (eth0/management interface) is Bridged&lt;/P&gt;
&lt;P&gt;Network Adapter 2 (eth1/dataplane interface) is on LAN segment 1&lt;/P&gt;
&lt;P&gt;pavm2&lt;/P&gt;
&lt;P&gt;Network Adapter 1 (eth0/management interface) is Bridged&lt;/P&gt;
&lt;P&gt;Network Adapter 2 (eth1/dataplane interface) is on LAN segment 1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 09 May 2025 21:17:04 GMT</pubDate>
    <dc:creator>aldo-escobar</dc:creator>
    <dc:date>2025-05-09T21:17:04Z</dc:date>
    <item>
      <title>VM series firewalls and interfaces</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vm-series-firewalls-and-interfaces/m-p/1228702#M124243</link>
      <description>&lt;P&gt;Howdy all&lt;/P&gt;
&lt;P&gt;I have deployed 2 VM series firewalls in VMware workstation pro but I can't get their dataplane interfaces to ping each other. I'm sure this has to do with how to configure the network adapters.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have no issues accessing the GUIs/ Management interfaces and they can ping each other as these interfaces are bridged in Vmware workstation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;dataplane interfaces should be able to ping each other, as that is the purpose of LAN segment, to put them on an isolated network so the VMs can see each other on the network. I want to do this that I can play with routing only between these 2 VM firewalls.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so from eth1/1 PAVM1 to eth1/1 PAVM2,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;admin@PA-VM&amp;gt; ping source 99.99.99.1 host 99.99.99.2&lt;BR /&gt;PING 99.99.99.2 (99.99.99.2) from 99.99.99.1 : 56(84) bytes of data.&lt;BR /&gt;^C&lt;BR /&gt;--- 99.99.99.2 ping statistics ---&lt;BR /&gt;5 packets transmitted, 0 received, 100% packet loss, time 128ms&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;pavm1&lt;/P&gt;
&lt;P&gt;Network Adapter 1 (eth0/management interface) is Bridged&lt;/P&gt;
&lt;P&gt;Network Adapter 2 (eth1/dataplane interface) is on LAN segment 1&lt;/P&gt;
&lt;P&gt;pavm2&lt;/P&gt;
&lt;P&gt;Network Adapter 1 (eth0/management interface) is Bridged&lt;/P&gt;
&lt;P&gt;Network Adapter 2 (eth1/dataplane interface) is on LAN segment 1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 21:17:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vm-series-firewalls-and-interfaces/m-p/1228702#M124243</guid>
      <dc:creator>aldo-escobar</dc:creator>
      <dc:date>2025-05-09T21:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: VM series firewalls and interfaces</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vm-series-firewalls-and-interfaces/m-p/1228744#M124246</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/289003"&gt;@aldo-escobar&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have you attached an interface management profile to the interfaces that allow ping?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/11-0/pan-os-networking-admin/configure-interfaces/use-interface-management-profiles-to-restrict-access" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/11-0/pan-os-networking-admin/configure-interfaces/use-interface-management-profiles-to-restrict-access&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Sun, 11 May 2025 20:56:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vm-series-firewalls-and-interfaces/m-p/1228744#M124246</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2025-05-11T20:56:42Z</dc:date>
    </item>
    <item>
      <title>Re: VM series firewalls and interfaces</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vm-series-firewalls-and-interfaces/m-p/1228745#M124247</link>
      <description>&lt;P&gt;Hello Tom,&lt;/P&gt;
&lt;P&gt;Management profiles are attached to interfaces.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 11 May 2025 22:01:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vm-series-firewalls-and-interfaces/m-p/1228745#M124247</guid>
      <dc:creator>aldo-escobar</dc:creator>
      <dc:date>2025-05-11T22:01:19Z</dc:date>
    </item>
    <item>
      <title>Re: VM series firewalls and interfaces</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vm-series-firewalls-and-interfaces/m-p/1228865#M124256</link>
      <description>&lt;P&gt;Hello Tom,&lt;/P&gt;
&lt;P&gt;I'm such a goofball, needed a break and review my settings. Turns out on one of the interfaces I did not attach a zone and a virtual router. This was missing. I configured the zone and virtual router, it now works. I could've swore I already did that part.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank You!&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 19:50:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vm-series-firewalls-and-interfaces/m-p/1228865#M124256</guid>
      <dc:creator>aldo-escobar</dc:creator>
      <dc:date>2025-05-12T19:50:22Z</dc:date>
    </item>
  </channel>
</rss>

