<?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 question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn-question/m-p/5361228#M1124124</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/445131"&gt;@benolyndav&lt;/a&gt;&amp;nbsp;thats fine then. On the remote peer just create a static route pointing to your tunnel IP via the tunnel interface. You will need to permit the traffic in the firewall rules.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jan 2026 15:58:37 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2026-01-14T15:58:37Z</dc:date>
    <item>
      <title>FTD Route Based VPN question</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn-question/m-p/5361205#M1124118</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have a static Route Based VPN and am wondering if I create a loopback interface on the FTD is there a way to allow this IP over the VPN to test the VPN or generate some traffic from the FTD across the VPN ??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2026 14:05:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn-question/m-p/5361205#M1124118</guid>
      <dc:creator>benolyndav</dc:creator>
      <dc:date>2026-01-14T14:05:11Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route Based VPN question</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn-question/m-p/5361206#M1124119</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/445131"&gt;@benolyndav&lt;/a&gt;&amp;nbsp;as long as the peer has a route over the VPN to that loopback IP address and firewall rules that should work. I assume you aren't using the loopback as the tunnel source?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2026 14:08:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn-question/m-p/5361206#M1124119</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2026-01-14T14:08:48Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route Based VPN question</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn-question/m-p/5361226#M1124123</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;No not using Loopback as tunnel source&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2026 15:46:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn-question/m-p/5361226#M1124123</guid>
      <dc:creator>benolyndav</dc:creator>
      <dc:date>2026-01-14T15:46:38Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Route Based VPN question</title>
      <link>https://community.cisco.com/t5/network-security/ftd-route-based-vpn-question/m-p/5361228#M1124124</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/445131"&gt;@benolyndav&lt;/a&gt;&amp;nbsp;thats fine then. On the remote peer just create a static route pointing to your tunnel IP via the tunnel interface. You will need to permit the traffic in the firewall rules.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2026 15:58:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-route-based-vpn-question/m-p/5361228#M1124124</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2026-01-14T15:58:37Z</dc:date>
    </item>
  </channel>
</rss>

