<?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: Route lookup for AnyConnect traffic in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/route-lookup-for-anyconnect-traffic/m-p/4041919#M1067482</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; It has nothing to do with RPF check in here. Once the packet gets decrypted by the ASA, it will have a source IP of something from the VPN POOL and a destination IP of whatever private resource the user wants to access and has access to. For the data plane to work:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - the ASA needs a route for all internal prefixes towards the core switch&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - the core switch needs a route for the VPN pool range towards the ASA&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Cristian Matei.&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 06 Mar 2020 19:31:38 GMT</pubDate>
    <dc:creator>Cristian Matei</dc:creator>
    <dc:date>2020-03-06T19:31:38Z</dc:date>
    <item>
      <title>Route lookup for AnyConnect traffic</title>
      <link>https://community.cisco.com/t5/network-security/route-lookup-for-anyconnect-traffic/m-p/4041386#M1067432</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using AnyConnect on Cisco ASA, but we use the gateway on core switch instead of ASA.&lt;/P&gt;&lt;P&gt;I'm curious to know does ASA perform RPF check even it's not the next hop for the traffic?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Because I've confirmed the traffic is pass on packet tracer, and VPN client already have secure route to gateway.&lt;/P&gt;&lt;P&gt;But I can not access destination before I add static route on Cisco ASA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does ASA perform RPF check even it's not the next hop for the traffic?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SSLVPN Client &amp;gt;&amp;gt;&amp;gt; Cisco ASA &amp;gt;&amp;gt;&amp;gt; Core switch (VPN gateway, same subnet as ASA inside interface) &amp;gt;&amp;gt;&amp;gt;Destination&lt;/P&gt;</description>
      <pubDate>Fri, 06 Mar 2020 02:08:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/route-lookup-for-anyconnect-traffic/m-p/4041386#M1067432</guid>
      <dc:creator>zexinfinite</dc:creator>
      <dc:date>2020-03-06T02:08:39Z</dc:date>
    </item>
    <item>
      <title>Re: Route lookup for AnyConnect traffic</title>
      <link>https://community.cisco.com/t5/network-security/route-lookup-for-anyconnect-traffic/m-p/4041409#M1067437</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ASA will perform RPF for all traffic passing through the interfaces specified. If the ASA does not have a route to the source that matches the interface, RPF will fail. In your case, i am guessing&amp;nbsp; you are using tunneled gateway for your vpn traffic but the return traffic from the destination has no reverse route in the ASA&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;</description>
      <pubDate>Fri, 06 Mar 2020 03:03:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/route-lookup-for-anyconnect-traffic/m-p/4041409#M1067437</guid>
      <dc:creator>johnd2310</dc:creator>
      <dc:date>2020-03-06T03:03:10Z</dc:date>
    </item>
    <item>
      <title>Re: Route lookup for AnyConnect traffic</title>
      <link>https://community.cisco.com/t5/network-security/route-lookup-for-anyconnect-traffic/m-p/4041919#M1067482</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; It has nothing to do with RPF check in here. Once the packet gets decrypted by the ASA, it will have a source IP of something from the VPN POOL and a destination IP of whatever private resource the user wants to access and has access to. For the data plane to work:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - the ASA needs a route for all internal prefixes towards the core switch&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - the core switch needs a route for the VPN pool range towards the ASA&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Cristian Matei.&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Mar 2020 19:31:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/route-lookup-for-anyconnect-traffic/m-p/4041919#M1067482</guid>
      <dc:creator>Cristian Matei</dc:creator>
      <dc:date>2020-03-06T19:31:38Z</dc:date>
    </item>
  </channel>
</rss>

