<?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 spoofing in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-spoofing/m-p/3986244#M9150</link>
    <description>&lt;P&gt;hi there, was this issue resolved? I am getting exactly same issue and not sure how to fix it.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Nov 2019 21:53:34 GMT</pubDate>
    <dc:creator>mirzauddin1295</dc:creator>
    <dc:date>2019-11-19T21:53:34Z</dc:date>
    <item>
      <title>ASA spoofing</title>
      <link>https://community.cisco.com/t5/network-security/asa-spoofing/m-p/3736802#M9145</link>
      <description>&lt;P&gt;I have a rather stubborn occurrence. I keep getting:&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Deny IP spoof from (10.87.88.1) to 10.141.36.60 on interface inside.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is connected via VPN. 10.87.88.1 is the VPN Termination point. It is a site to site connection. The 10.141.36.60 is the laptop I am using. I am able to ping the other devices which are 10.87.88.2 - up. But I believe it is because of the IP spoof that this is not replying. I have&amp;nbsp;spent three days off and on with this, and even have another engineer working on it with me. For some reason, the firewall thinks that when anything attempts to ping 10.87.88.1, the IP being pinged (or Cisco ASA inside interface) is a spoofed address. I have already tried to turn off&amp;nbsp;&lt;SPAN&gt;unicast reverse path failure. And a myriad of things that this and other sites suggested.&amp;nbsp;&lt;/SPAN&gt;Anyone have thoughts on how to resolve. Also I cannot ping this device but I can ssh to it. I am hoping from someone with an "Oh yeah" moment, if not, I can see this post going deep.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:25:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-spoofing/m-p/3736802#M9145</guid>
      <dc:creator>egoodman2</dc:creator>
      <dc:date>2020-02-21T16:25:22Z</dc:date>
    </item>
    <item>
      <title>Re: ASA spoofing</title>
      <link>https://community.cisco.com/t5/network-security/asa-spoofing/m-p/3736812#M9146</link>
      <description>&lt;P&gt;One more thing, any persons posting KB articles wanting me to wade through infinite pages of irrelevant information need not post.&amp;nbsp;I am a busy person, and if you are just guessing to get some kind of rating for your profile...don't. Thank you all.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Oct 2018 19:37:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-spoofing/m-p/3736812#M9146</guid>
      <dc:creator>egoodman2</dc:creator>
      <dc:date>2018-10-31T19:37:00Z</dc:date>
    </item>
    <item>
      <title>Re: ASA spoofing</title>
      <link>https://community.cisco.com/t5/network-security/asa-spoofing/m-p/3986244#M9150</link>
      <description>&lt;P&gt;hi there, was this issue resolved? I am getting exactly same issue and not sure how to fix it.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Nov 2019 21:53:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-spoofing/m-p/3986244#M9150</guid>
      <dc:creator>mirzauddin1295</dc:creator>
      <dc:date>2019-11-19T21:53:34Z</dc:date>
    </item>
  </channel>
</rss>

