<?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/5092230#M1112162</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Would that be any to&amp;nbsp; any or&amp;nbsp; &amp;nbsp; any to Outside in Nar rule ??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Tue, 07 May 2024 08:43:16 GMT</pubDate>
    <dc:creator>benolyndav</dc:creator>
    <dc:date>2024-05-07T08:43:16Z</dc:date>
    <item>
      <title>FTD Route Based VPN</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5088607#M1112079</link>
      <description>&lt;P&gt;Hi We have to configure a RB VPN and am wondering if I add the new VTI Interface to The exsisting outside security group or do I have to create a new security group, the outsdide Security group has the Internet facing Interfaces in it.??&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 10:39:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5088607#M1112079</guid>
      <dc:creator>benolyndav</dc:creator>
      <dc:date>2024-05-03T10:39:51Z</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/5088615#M1112080</link>
      <description>&lt;P&gt;VTI interface need to put in different zone secuirty than tunnel source of VTI&lt;/P&gt;
&lt;P&gt;This give you more control of traffic pass through vti&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 10:51:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5088615#M1112080</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-05-03T10:51:00Z</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/5089033#M1112093</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/445131"&gt;@benolyndav&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Adding a VTI to a Security Zone is optional. I'd recommend you configure a VTI in a unique Security Zone, you can then control traffic over the VPN tunnel using the Security Zone in the Access Control policy, this allows you to distinguish between VPN traffic and cleartext traffic.&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 17:56:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5089033#M1112093</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-05-03T17:56:22Z</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/5089718#M1112108</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ok makes sense,&amp;nbsp; So now when traffic is soutced from Inside Interface and needs to go through the VTI then I would not say Inside to Outside anymore it would be Inside to VTI and through the tunnel.?&lt;BR /&gt;Also my Nat rule would now be Inside to VTI and Outside to VTI, rather than Inside to Outside and Outside to Inside for other traffic.?&lt;/P&gt;&lt;P&gt;for the static routes would | i now say the gateway for the remote subnet is the remote VTI peer IP Address. ??&lt;BR /&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 04 May 2024 14:46:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5089718#M1112108</guid>
      <dc:creator>benolyndav</dc:creator>
      <dc:date>2024-05-04T14:46:41Z</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/5089724#M1112109</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/445131"&gt;@benolyndav&lt;/a&gt; correct.&lt;/P&gt;
&lt;P&gt;You cannot write NAT rules for a Virtual Tunnel Interface (VTI), which are used in site-to-site VPN. Writing rules for the VTI's source interface will not apply NAT to the VPN tunnel. &lt;STRONG&gt;To write NAT rules that will apply to VPN traffic tunneled on a VTI, you must use "any" as the interface&lt;/STRONG&gt;; you cannot explicitly specify interface names.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/740/management-center-device-config-74/interfaces-settings-nat.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/740/management-center-device-config-74/interfaces-settings-nat.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Yes, for routing use the VTI tunnel IP address as the next hop or using a routing protocol.&lt;/P&gt;</description>
      <pubDate>Sat, 04 May 2024 15:14:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5089724#M1112109</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-05-04T15:14:02Z</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/5089753#M1112111</link>
      <description>&lt;P&gt;You can not use nameif of VTI in NAT' that separate from zone secuirty' you can use ""any"" instead&lt;/P&gt;
&lt;P&gt;For static route&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The VTI tunnel IP of peer is use as next-hop not VTI tunnel IP of fpr.&lt;/P&gt;
&lt;P&gt;Keep in minde that vti tunnel appear as direct connect link from fpr view.&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Sat, 04 May 2024 16:47:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5089753#M1112111</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-05-04T16:47:06Z</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/5092230#M1112162</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Would that be any to&amp;nbsp; any or&amp;nbsp; &amp;nbsp; any to Outside in Nar rule ??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2024 08:43:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5092230#M1112162</guid>
      <dc:creator>benolyndav</dc:creator>
      <dc:date>2024-05-07T08:43:16Z</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/5092233#M1112163</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/445131"&gt;@benolyndav&lt;/a&gt; EDIT: actually INSIDE to any. Ingress through the inside interface, egress via the Tunnel interface - NAT rules are bi-directional. Be as specific as possible in your NAT rule in regard to source/destination networks.&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2024 14:08:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5092233#M1112163</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-05-07T14:08:41Z</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/5092612#M1112168</link>
      <description>&lt;P&gt;NAT will be&amp;nbsp;&lt;/P&gt;
&lt;P&gt;INSIDE to ANY &amp;lt;- if traffic is NAT to VTI interface&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2024 13:59:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5092612#M1112168</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-05-07T13:59:39Z</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/5094563#M1112245</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Am I ok to DM You.??&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 18:37:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5094563#M1112245</guid>
      <dc:creator>benolyndav</dc:creator>
      <dc:date>2024-05-08T18:37: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/5094565#M1112246</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/445131"&gt;@benolyndav&lt;/a&gt; sure.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 18:39:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn/m-p/5094565#M1112246</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-05-08T18:39:51Z</dc:date>
    </item>
  </channel>
</rss>

