<?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 Deny TCP reverse path check in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813726#M983105</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"Ip verify reverse path" checks two things:&lt;/P&gt;&lt;P&gt;1. is a route present for that specific source?&lt;/P&gt;&lt;P&gt;2. is the packet&amp;nbsp; comming on the right interface?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest to check the routing to exclude possible assymetic routing issues. If everything looks alright then it might be a real spoofing attack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 09 Sep 2012 17:22:11 GMT</pubDate>
    <dc:creator>oszkari</dc:creator>
    <dc:date>2012-09-09T17:22:11Z</dc:date>
    <item>
      <title>Deny TCP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813720#M983002</link>
      <description>&lt;P&gt;Hi I get following message from PIX ver 7.0:&lt;/P&gt;&lt;P&gt;PIX-1-106021: Deny TCP reverse path check from 192.168.0.150 to 192.168.0.250 on interface dmz&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;106021: Someone is attempting to spoof an IP address on an inbound connection. Unicast Reverse Path Forwarding (Unicast RPF), also known as reverse route lookup, detected a packet that does not have a source address represented by a route and assumes that it is part of an attack on your firewall. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but extraly, we have virtual ip with netscaler in the dmz, then do &lt;A class="jive-link-custom" href="http://virtual" target="_blank"&gt;http://virtual&lt;/A&gt; ip address, from 192.168.0.150, phisical server ip is 192.168.0.250. How to fix or disable Unicast Reverse Path Forwarding? if disable, what is happend?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ben&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:52:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813720#M983002</guid>
      <dc:creator>bma</dc:creator>
      <dc:date>2019-03-11T10:52:55Z</dc:date>
    </item>
    <item>
      <title>Re: Deny TCP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813721#M983035</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;look for the following command in your config:&lt;/P&gt;&lt;P&gt;ip verify reverse-path interface ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Although, it'd be best to figure out what was causing the log message.  Basically the message means the dmz interface received a packet with the source address matching a known inside network address.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Aug 2007 21:40:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813721#M983035</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-08-02T21:40:53Z</dc:date>
    </item>
    <item>
      <title>Re: Deny TCP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813722#M983064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because issue, people cannot access web server with virtual address. &lt;/P&gt;&lt;P&gt;What should be impacted if disable ip verify reverse-path?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ben&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Aug 2007 22:24:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813722#M983064</guid>
      <dc:creator>bma</dc:creator>
      <dc:date>2007-08-02T22:24:08Z</dc:date>
    </item>
    <item>
      <title>Re: Deny TCP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813723#M983076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;its intended as a security feature to prevent address spoofing.&lt;/P&gt;&lt;P&gt;should be no impact if you disable it. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Aug 2007 02:55:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813723#M983076</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-08-03T02:55:39Z</dc:date>
    </item>
    <item>
      <title>Deny TCP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813724#M983087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try adding a static route to the source IP towards the interface through which it comes. so that a route is present for that IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sony&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Sep 2011 07:10:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813724#M983087</guid>
      <dc:creator>sonybabu2k1</dc:creator>
      <dc:date>2011-09-27T07:10:31Z</dc:date>
    </item>
    <item>
      <title>Deny TCP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813725#M983097</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Need a serious help for this antispoofing issue :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sep&amp;nbsp; 6 14:19:42 vrd-swi-asa-01-pri %ASA-6-302013: Built inbound TCP&amp;nbsp; connection 25447904 for IP-PBX-WAN:10.98.2.12/49383 (10.98.2.12/49383)&amp;nbsp; to Mitel-Front:172.20.128.5/7011 (172.20.128.5/7011)&lt;/P&gt;&lt;P&gt;Sep&amp;nbsp; 6 14:19:42 vrd-swi-asa-01-pri %ASA-6-302014: Teardown TCP&amp;nbsp; connection 25447903 for IP-PBX-WAN:10.98.2.12/49382 to&amp;nbsp; Mitel-Front:172.20.128.5/7011 duration 0:00:00 bytes 6845 TCP FINs&lt;/P&gt;&lt;P&gt;Sep&amp;nbsp; 6 15:09:38 vrd-swi-asa-01-pri %ASA-1-106021: Deny TCP reverse path check from 10.98.2.12 to 172.40.0.1 on interface Corp-WAN&lt;/P&gt;&lt;P&gt;Sep&amp;nbsp; 6 15:09:38 vrd-swi-asa-01-pri %ASA-1-106021: Deny TCP reverse path check from 10.98.2.12 to 172.40.0.1 on interface Corp-WAN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are the logs of my WAN firewall..Problem here is traffic originating from 10.98.2.12 when hitting to 172.40.0.1 is getting denied, while hitting to any other destination is allowed.&lt;/P&gt;&lt;P&gt;I think "ip verify reverse path" check the source IP is coming from correct interface or not, here it is coming from IP-PBX-WAN for all other traffic but why not for 172.40.0.1 ?&lt;/P&gt;&lt;P&gt;Please suggest. &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Sep 2012 07:57:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813725#M983097</guid>
      <dc:creator>vipulagrawal</dc:creator>
      <dc:date>2012-09-07T07:57:35Z</dc:date>
    </item>
    <item>
      <title>Deny TCP reverse path check</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813726#M983105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"Ip verify reverse path" checks two things:&lt;/P&gt;&lt;P&gt;1. is a route present for that specific source?&lt;/P&gt;&lt;P&gt;2. is the packet&amp;nbsp; comming on the right interface?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest to check the routing to exclude possible assymetic routing issues. If everything looks alright then it might be a real spoofing attack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 09 Sep 2012 17:22:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-path-check/m-p/813726#M983105</guid>
      <dc:creator>oszkari</dc:creator>
      <dc:date>2012-09-09T17:22:11Z</dc:date>
    </item>
  </channel>
</rss>

