<?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 to AWS VPN in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/vm-series-to-aws-vpn/m-p/363551#M1051</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My main aim is that I'm trying to setup a VPN between AWS and my VM Series.&lt;BR /&gt;&lt;BR /&gt;I so far have my Phase 1 and Phase 2 connections up. My AWS VPN has a static route to the remote CIDR, but when I try and send traffic over this (example ping or ssh to 172.168.1.5 from a server on the AWS side) I see no traffic hitting the the VM series.&lt;BR /&gt;&lt;BR /&gt;If I run a traceroute on the server I see it get as far as the local AWS CIDR &lt;SPAN&gt;169.254.222.244/30 but then don't see anything in the monitor side on the VM series.&lt;BR /&gt;&lt;BR /&gt;What areas would i need to check to to either see the traffic attempts or see what could stop it from going over the tunnel?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Nov 2020 15:22:58 GMT</pubDate>
    <dc:creator>Chris.Billett</dc:creator>
    <dc:date>2020-11-17T15:22:58Z</dc:date>
    <item>
      <title>VM Series to AWS VPN</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/vm-series-to-aws-vpn/m-p/363551#M1051</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My main aim is that I'm trying to setup a VPN between AWS and my VM Series.&lt;BR /&gt;&lt;BR /&gt;I so far have my Phase 1 and Phase 2 connections up. My AWS VPN has a static route to the remote CIDR, but when I try and send traffic over this (example ping or ssh to 172.168.1.5 from a server on the AWS side) I see no traffic hitting the the VM series.&lt;BR /&gt;&lt;BR /&gt;If I run a traceroute on the server I see it get as far as the local AWS CIDR &lt;SPAN&gt;169.254.222.244/30 but then don't see anything in the monitor side on the VM series.&lt;BR /&gt;&lt;BR /&gt;What areas would i need to check to to either see the traffic attempts or see what could stop it from going over the tunnel?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2020 15:22:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/vm-series-to-aws-vpn/m-p/363551#M1051</guid>
      <dc:creator>Chris.Billett</dc:creator>
      <dc:date>2020-11-17T15:22:58Z</dc:date>
    </item>
    <item>
      <title>Re: VM Series to AWS VPN</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/vm-series-to-aws-vpn/m-p/374003#M1080</link>
      <description>&lt;P&gt;&lt;STRONG&gt;My question is - am I an ignoramus for not knowing this?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;I get that I probably shouldn't have taken their published throughput numbers at face value, but I've just never had reported issues with throughput using this type of design in the past. Moreover, this limitation was not mentioned&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;anywhere&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;in any documentation/blog posts, etc. I could find previously.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 12 Dec 2020 07:54:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/vm-series-to-aws-vpn/m-p/374003#M1080</guid>
      <dc:creator>Savannah</dc:creator>
      <dc:date>2020-12-12T07:54:35Z</dc:date>
    </item>
  </channel>
</rss>

