<?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 you're right. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919116#M171669</link>
    <description>&lt;P&gt;you're right.&lt;/P&gt;
&lt;P&gt;checking routing!!!&lt;/P&gt;</description>
    <pubDate>Fri, 13 May 2016 13:15:02 GMT</pubDate>
    <dc:creator>gianluca811</dc:creator>
    <dc:date>2016-05-13T13:15:02Z</dc:date>
    <item>
      <title>ASA - Deny TCP reverse path.  WHY ????</title>
      <link>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919112#M171658</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;on my asa ASA5540 I have the following error:&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;1&amp;nbsp;&amp;nbsp; &amp;nbsp;May 13 2016&amp;nbsp;&amp;nbsp; &amp;nbsp;11:19:07&amp;nbsp;&amp;nbsp; &amp;nbsp;106021&amp;nbsp;&amp;nbsp; &amp;nbsp;10.168.101.100&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;232.239.122.219&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Deny TCP reverse path check from 10.168.101.100 to 232.239.122.219 on interface Outside&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;The source 10.168.101.100 is directly connected, the destination has the following static route:&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;route Outside 232.239.122.192 255.255.255.224 10.168.201.1 1 &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;ASA5540#show route&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.168.101.100 255.255.254.0 is directly connected, Inside&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp; 232.239.122.192 255.255.255.224 [1/0] via 10.168.201.1, Outside&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;I made a capture on the source and destination interface filtering the destination 232.239.122.219:&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp; 1: 11:19:06.784581&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 802.1Q vlan#18 P0 10.168.101.100.38529 &amp;gt; 232.239.122.219.21: S 3629871294:3629871294(0) win 14600 &amp;lt;mss 1460,sackOK,timestamp 745899726 0,nop,wscale 7&amp;gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp; 2: 11:19:07.783879&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 802.1Q vlan#18 P0 10.168.101.100.38529 &amp;gt; 232.239.122.219.21: S 3629871294:3629871294(0) win 14600 &amp;lt;mss 1460,sackOK,timestamp 745900726 0,nop,wscale 7&amp;gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp; 3: 11:19:09.784047&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 802.1Q vlan#18 P0 10.168.101.100.38529 &amp;gt; 232.239.122.219.21: S 3629871294:3629871294(0) win 14600 &amp;lt;mss 1460,sackOK,timestamp 745902726 0,nop,wscale 7&amp;gt;&lt;/SPAN&gt; &lt;BR /&gt;&lt;BR /&gt;What is wrong ?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:44:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919112#M171658</guid>
      <dc:creator>gianluca811</dc:creator>
      <dc:date>2019-03-12T07:44:57Z</dc:date>
    </item>
    <item>
      <title>The router with the IP 10.168</title>
      <link>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919113#M171661</link>
      <description>&lt;P&gt;The router with the IP&amp;nbsp;&lt;SPAN&gt;10.168.201.1 could have a route for 232.239.122.192/24 back to your firewall.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 May 2016 12:39:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919113#M171661</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2016-05-13T12:39:41Z</dc:date>
    </item>
    <item>
      <title>yes it has a route back to</title>
      <link>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919114#M171664</link>
      <description>&lt;P&gt;yes it has a route back to Outside Interface on my firewall.&lt;/P&gt;
&lt;P&gt;For this I cannot understand why this error&lt;/P&gt;</description>
      <pubDate>Fri, 13 May 2016 12:42:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919114#M171664</guid>
      <dc:creator>gianluca811</dc:creator>
      <dc:date>2016-05-13T12:42:50Z</dc:date>
    </item>
    <item>
      <title>The initial packet came from</title>
      <link>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919115#M171666</link>
      <description>&lt;OL&gt;
&lt;LI&gt;The initial packet came from your internal network. 10.168.101.100 has a network-location that is not outside of your firewall.&lt;/LI&gt;
&lt;LI&gt;The router&amp;nbsp;routes the packet back to your firewall. There it arrives with a source-address of 10.168.101.100 on the outside interface. Based on the routing-table this packet is spoofed as the location of 10.168.101.100 is inside.&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Fri, 13 May 2016 12:59:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919115#M171666</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2016-05-13T12:59:42Z</dc:date>
    </item>
    <item>
      <title>you're right.</title>
      <link>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919116#M171669</link>
      <description>&lt;P&gt;you're right.&lt;/P&gt;
&lt;P&gt;checking routing!!!&lt;/P&gt;</description>
      <pubDate>Fri, 13 May 2016 13:15:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919116#M171669</guid>
      <dc:creator>gianluca811</dc:creator>
      <dc:date>2016-05-13T13:15:02Z</dc:date>
    </item>
    <item>
      <title>found the routing problem. as</title>
      <link>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919117#M171673</link>
      <description>&lt;P&gt;found the routing problem. as described from you was like a "loop"&lt;/P&gt;</description>
      <pubDate>Fri, 13 May 2016 14:36:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-deny-tcp-reverse-path-why/m-p/2919117#M171673</guid>
      <dc:creator>gianluca811</dc:creator>
      <dc:date>2016-05-13T14:36:04Z</dc:date>
    </item>
  </channel>
</rss>

