<?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 VWIRE Physical Connecivity to Current Virtual Firewall in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/vwire-physical-connecivity-to-current-virtual-firewall/m-p/72155#M41004</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am trying to get my head around VWIRE and how it supposed to work.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have the following scenario&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SWITCH -&amp;gt; VIRTUAL FIREWALL (ON SHARED HOST) -&amp;gt; INTERNET&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are now looking to do&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SWITCH -&amp;gt; PALO ALTO -&amp;gt; VIRTUAL FIREWALL (ON SHARED HOST) -&amp;gt; INTERNET&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am thinking how this would work physically. The virtual firewall sits on a VM host (shared with other VMs) which plugs directly into the switch.&amp;nbsp; It is a flat network.&amp;nbsp; Therefore both e1/1 and 1/2 on the palo will go into the same VLAN.&amp;nbsp; How would the Palo know how to intercept the traffic with the client machines default gateway being the virtual firewall which also sits in the same VLAN and also on the same switch.&amp;nbsp; I have seen articles that e1/1 and e1/2 should be connected to the same VLAN either side be it an access or trunk port, then I have seen articles were e1/1 and e1/2 are in different VLANs.&amp;nbsp;&amp;nbsp; The physical architecure iof vWIRE in terms how to cable this up is not documented anywhere really.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Some feedback would be very much appreciated.&amp;nbsp; Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 04 Feb 2016 14:39:06 GMT</pubDate>
    <dc:creator>indysogi</dc:creator>
    <dc:date>2016-02-04T14:39:06Z</dc:date>
    <item>
      <title>VWIRE Physical Connecivity to Current Virtual Firewall</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vwire-physical-connecivity-to-current-virtual-firewall/m-p/72155#M41004</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am trying to get my head around VWIRE and how it supposed to work.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have the following scenario&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SWITCH -&amp;gt; VIRTUAL FIREWALL (ON SHARED HOST) -&amp;gt; INTERNET&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are now looking to do&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SWITCH -&amp;gt; PALO ALTO -&amp;gt; VIRTUAL FIREWALL (ON SHARED HOST) -&amp;gt; INTERNET&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am thinking how this would work physically. The virtual firewall sits on a VM host (shared with other VMs) which plugs directly into the switch.&amp;nbsp; It is a flat network.&amp;nbsp; Therefore both e1/1 and 1/2 on the palo will go into the same VLAN.&amp;nbsp; How would the Palo know how to intercept the traffic with the client machines default gateway being the virtual firewall which also sits in the same VLAN and also on the same switch.&amp;nbsp; I have seen articles that e1/1 and e1/2 should be connected to the same VLAN either side be it an access or trunk port, then I have seen articles were e1/1 and e1/2 are in different VLANs.&amp;nbsp;&amp;nbsp; The physical architecure iof vWIRE in terms how to cable this up is not documented anywhere really.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Some feedback would be very much appreciated.&amp;nbsp; Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2016 14:39:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vwire-physical-connecivity-to-current-virtual-firewall/m-p/72155#M41004</guid>
      <dc:creator>indysogi</dc:creator>
      <dc:date>2016-02-04T14:39:06Z</dc:date>
    </item>
    <item>
      <title>Re: VWIRE Physical Connecivity to Current Virtual Firewall</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vwire-physical-connecivity-to-current-virtual-firewall/m-p/72157#M41005</link>
      <description>&lt;P&gt;to be able to 'force' traffic over the vwire, the virtual firewall will need to be on a different vlan than the clients so the switch is unable to bridge the 2 together&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;that or the server needs to be physically connected to one side of the vwire&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2016 15:18:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vwire-physical-connecivity-to-current-virtual-firewall/m-p/72157#M41005</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2016-02-04T15:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: VWIRE Physical Connecivity to Current Virtual Firewall</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vwire-physical-connecivity-to-current-virtual-firewall/m-p/72164#M41008</link>
      <description>&lt;P&gt;Check the following topology.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/2379i52C8033D6169F885/image-size/original?v=mpbl-1&amp;amp;px=-1" border="0" alt="IPS.jpg" title="IPS.jpg" /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have made the traffic to pass through the firewall by the help of VLAN.&lt;/P&gt;
&lt;P&gt;Note that if the port 4 and port 1 become part of same VLAN the traffic will not pass through PA firewall.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2016 17:35:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vwire-physical-connecivity-to-current-virtual-firewall/m-p/72164#M41008</guid>
      <dc:creator>pankaku</dc:creator>
      <dc:date>2016-02-04T17:35:26Z</dc:date>
    </item>
  </channel>
</rss>

