<?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: New Public IP Block-NAT in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/new-public-ip-block-nat/m-p/592332#M117904</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Is your NAT a bi-directional? Also check the security policies to make sure the traffic is allowed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jul 2024 19:07:25 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2024-07-17T19:07:25Z</dc:date>
    <item>
      <title>New Public IP Block-NAT</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-public-ip-block-nat/m-p/592258#M117891</link>
      <description>&lt;P&gt;We have our PA connected to our ISP via /30's and they gave us a /28.&amp;nbsp; We have a SilverPeak sdwan appliance behind the PA and are NAT'ing it's WAN interface from 10.5.1.2 to x.x.x.50.&amp;nbsp; We can reach the SilverPeak on 443, but when we noticed it's not trying to establish underlay tunnels with the other SilverPeaks.&amp;nbsp; I tried to manually configure an ipsec tunnel but even though I pointed the far end to x.x.x.50, the logs show it was trying to establish with our side of the /30.&amp;nbsp; Any pointers would be greatly appreciated.&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="jasongorman_1-1721182677357.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/60906iAAC301D00E044396/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="jasongorman_1-1721182677357.png" alt="jasongorman_1-1721182677357.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2024 02:18:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-public-ip-block-nat/m-p/592258#M117891</guid>
      <dc:creator>J.Gorman581418</dc:creator>
      <dc:date>2024-07-17T02:18:26Z</dc:date>
    </item>
    <item>
      <title>Re: New Public IP Block-NAT</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-public-ip-block-nat/m-p/592332#M117904</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Is your NAT a bi-directional? Also check the security policies to make sure the traffic is allowed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2024 19:07:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-public-ip-block-nat/m-p/592332#M117904</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2024-07-17T19:07:25Z</dc:date>
    </item>
  </channel>
</rss>

