<?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: ASA session Check in Asymmetric Routing in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-session-check-in-asymmetric-routing/m-p/3882569#M5940</link>
    <description>Something to consider is using TCP state bypass for your specific (interesting) vpn traffic. This basically alters the way sessions are established. It is similar to how a UDP connection is treated. See: &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa82/configuration/guide/config/conns_tcpstatebypass.html#wp1088415" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa82/configuration/guide/config/conns_tcpstatebypass.html#wp1088415&lt;/A&gt;</description>
    <pubDate>Mon, 01 Jul 2019 13:24:12 GMT</pubDate>
    <dc:creator>Mike.Cifelli</dc:creator>
    <dc:date>2019-07-01T13:24:12Z</dc:date>
    <item>
      <title>ASA session Check in Asymmetric Routing</title>
      <link>https://community.cisco.com/t5/network-security/asa-session-check-in-asymmetric-routing/m-p/3882461#M5938</link>
      <description>&lt;P&gt;I have a question regarding ASA session check&lt;/P&gt;&lt;P&gt;Imagen this situation&lt;/P&gt;&lt;P&gt;We have an ASA which is Building two VPNs (Site-to-Site) to the Cloud and in the Routing table there is a loadbalancing to the Destination in the Cloud over the two VPN connections.(Loadbalancing)&lt;/P&gt;&lt;P&gt;My question is lets if the first packet TCP,Syn sent over the first VPN and the answer&amp;nbsp; TCP-ACK came over the second VPN will the ASA Drop this packet?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ofcourse considring RPF is not being violated.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:15:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-session-check-in-asymmetric-routing/m-p/3882461#M5938</guid>
      <dc:creator>amhish@netfox.de</dc:creator>
      <dc:date>2020-02-21T17:15:46Z</dc:date>
    </item>
    <item>
      <title>Re: ASA session Check in Asymmetric Routing</title>
      <link>https://community.cisco.com/t5/network-security/asa-session-check-in-asymmetric-routing/m-p/3882569#M5940</link>
      <description>Something to consider is using TCP state bypass for your specific (interesting) vpn traffic. This basically alters the way sessions are established. It is similar to how a UDP connection is treated. See: &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa82/configuration/guide/config/conns_tcpstatebypass.html#wp1088415" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa82/configuration/guide/config/conns_tcpstatebypass.html#wp1088415&lt;/A&gt;</description>
      <pubDate>Mon, 01 Jul 2019 13:24:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-session-check-in-asymmetric-routing/m-p/3882569#M5940</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-07-01T13:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: ASA session Check in Asymmetric Routing</title>
      <link>https://community.cisco.com/t5/network-security/asa-session-check-in-asymmetric-routing/m-p/3885154#M5945</link>
      <description>&lt;P&gt;Thank you for your respond.&lt;/P&gt;&lt;P&gt;Looks like loadbalancing over tunnels will stay out of reach&amp;nbsp; on ASA.&lt;/P&gt;&lt;P&gt;TCP Bypass ist not supported on Tunnel interfaces.&lt;/P&gt;&lt;P&gt;we will need to install a router infront of the Firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2019 09:48:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-session-check-in-asymmetric-routing/m-p/3885154#M5945</guid>
      <dc:creator>amhish@netfox.de</dc:creator>
      <dc:date>2019-07-05T09:48:05Z</dc:date>
    </item>
  </channel>
</rss>

