<?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 Global Protect at the inside truted interface in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-at-the-inside-truted-interface/m-p/179068#M55638</link>
    <description>&lt;P&gt;PAN 5060&lt;/P&gt;&lt;P&gt;Outisde untrusted interface 5.5.1.77&lt;/P&gt;&lt;P&gt;Inside trusted interface 10.10.1.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wifi guest network inside 10.10.5.0/24&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most Global Protect corporate users go to ourvpn.foo.com 5.5.1.77.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;WiFi users normally PAT to the Internet using that same interface IP 5.5.1.77. So all source addresses to the Internet appear to be 5.5.1.77. Like most guest networks the users have no access (for the most part) to internal IP private addresses. Just Internet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But let's say that WiFi user 10.10.5.99 wants to to user Global Protect like the outside users so he can access internal resources. Is there a NAT that would say if you see traffic from the WiFi network destined for the external interface address 5.5.1.77 at VPN port whatever - instead of PATting it, terminate that traffic and create the tunnel just as is it had originated from the outside untrusted network. Is that possible?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Sep 2017 04:28:54 GMT</pubDate>
    <dc:creator>palomed</dc:creator>
    <dc:date>2017-09-28T04:28:54Z</dc:date>
    <item>
      <title>Global Protect at the inside truted interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-at-the-inside-truted-interface/m-p/179068#M55638</link>
      <description>&lt;P&gt;PAN 5060&lt;/P&gt;&lt;P&gt;Outisde untrusted interface 5.5.1.77&lt;/P&gt;&lt;P&gt;Inside trusted interface 10.10.1.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wifi guest network inside 10.10.5.0/24&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most Global Protect corporate users go to ourvpn.foo.com 5.5.1.77.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;WiFi users normally PAT to the Internet using that same interface IP 5.5.1.77. So all source addresses to the Internet appear to be 5.5.1.77. Like most guest networks the users have no access (for the most part) to internal IP private addresses. Just Internet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But let's say that WiFi user 10.10.5.99 wants to to user Global Protect like the outside users so he can access internal resources. Is there a NAT that would say if you see traffic from the WiFi network destined for the external interface address 5.5.1.77 at VPN port whatever - instead of PATting it, terminate that traffic and create the tunnel just as is it had originated from the outside untrusted network. Is that possible?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Sep 2017 04:28:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-at-the-inside-truted-interface/m-p/179068#M55638</guid>
      <dc:creator>palomed</dc:creator>
      <dc:date>2017-09-28T04:28:54Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect at the inside truted interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-at-the-inside-truted-interface/m-p/179131#M55639</link>
      <description>&lt;P&gt;hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/54718"&gt;@palomed&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;you'll need a NAT rule at the top of your NAT policy that actually does not do NAT for that specific destination address&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so&lt;/P&gt;
&lt;P&gt;trust to untrust, destination ip 5.5.1.177 no-NAT&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="nonoat.png" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/11582i2A2E7F00A30C5B6E/image-size/large?v=v2&amp;amp;px=999" role="button" title="nonoat.png" alt="nonoat.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;make sure it is placed above your default outbound NAT&lt;/P&gt;</description>
      <pubDate>Thu, 28 Sep 2017 09:28:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-at-the-inside-truted-interface/m-p/179131#M55639</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-09-28T09:28:41Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect at the inside truted interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-at-the-inside-truted-interface/m-p/179180#M55647</link>
      <description>&lt;P&gt;Very helpful.&amp;nbsp;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Sep 2017 14:52:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-at-the-inside-truted-interface/m-p/179180#M55647</guid>
      <dc:creator>palomed</dc:creator>
      <dc:date>2017-09-28T14:52:53Z</dc:date>
    </item>
  </channel>
</rss>

