<?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: FTD Route based VPN in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099641#M1112310</link>
    <description>&lt;P&gt;Not showing&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 10 May 2024 11:04:53 GMT</pubDate>
    <dc:creator>N3om</dc:creator>
    <dc:date>2024-05-10T11:04:53Z</dc:date>
    <item>
      <title>FTD Route based VPN</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099217#M1112297</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have created the VTI Interface for this but when I run packet tracer input the VTI I nterface is not in the list of available interfaces to use in packet tracer.??&lt;/P&gt;&lt;P&gt;Any ideas anyone&amp;nbsp;&lt;BR /&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 08:09:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099217#M1112297</guid>
      <dc:creator>N3om</dc:creator>
      <dc:date>2024-05-10T08:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route based VPN</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099323#M1112300</link>
      <description>&lt;P&gt;Wierd&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway you can use Inside interface in packet tracer fer&amp;nbsp; and the route lookup must poiny to VTI&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 08:48:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099323#M1112300</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-05-10T08:48:26Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route based VPN</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099328#M1112301</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;when I run packet tracer from inside to the subnet at the peer side in the results its ok it says inside to vti, but when i run in other direction I only see outside and inside interface, so i cant do packet tracer from vti to inside.??&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 08:52:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099328#M1112301</guid>
      <dc:creator>N3om</dc:creator>
      <dc:date>2024-05-10T08:52:15Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route based VPN</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099335#M1112303</link>
      <description>&lt;P&gt;Yes, when I test policy based VPN I do two direction&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But since nameif of VTI is not appear in packet tracer you have only one direction test.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But as You mentioned when you use Inside the packet tracer is all UP and allow so the&amp;nbsp; VTI is OK.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or Do you have issue in VTI and you need to test other direction?&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 08:57:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099335#M1112303</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-05-10T08:57:58Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route based VPN</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099574#M1112307</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;The Customer are sending traffic but its not connecting and I dont see thier traffic in our connections gui. I wonder if there is a bug that causes Interface not to show in list ??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 10:32:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099574#M1112307</guid>
      <dc:creator>N3om</dc:creator>
      <dc:date>2024-05-10T10:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route based VPN</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099599#M1112308</link>
      <description>&lt;P&gt;Sorry the connection is drop or not showing in GUI?&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 10:37:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099599#M1112308</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-05-10T10:37:59Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route based VPN</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099641#M1112310</link>
      <description>&lt;P&gt;Not showing&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 11:04:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099641#M1112310</guid>
      <dc:creator>N3om</dc:creator>
      <dc:date>2024-05-10T11:04:53Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route based VPN</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099797#M1112313</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1726559"&gt;@N3om&lt;/a&gt; the documentation is poor and does not explictly state you can or cannot specify a VTI as the input interface, but it does state that some packet-tracer functionality is not supported with route based VPN.&lt;/P&gt;
&lt;P&gt;"It is possible to inject a decrypted packet in a VPN tunnel, which is generic and applicable for both IPSec and TLS. It is also possible to simulate a packet that comes across a VPN tunnel. The simulated ‘decrypted’ packet would be matched against an existing VPN tunnel and the associated tunnel policies would be applied. However, &lt;STRONG&gt;this functionality is not applicable for a route-based VPN tunnel."&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa-cli-reference/I-R/asa-command-ref-I-R/pa-pn-commands.html#wp1614728796" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa-cli-reference/I-R/asa-command-ref-I-R/pa-pn-commands.html#wp1614728796&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I double checked a VTI I have access to and I cannot specify it as the source interface in packet-tracer either, so I would say you cannot.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 12:01:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5099797#M1112313</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-05-10T12:01:33Z</dc:date>
    </item>
  </channel>
</rss>

