<?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 Assistance Required – Firewall Land Attack Logs in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/assistance-required-firewall-land-attack-logs/m-p/5373575#M1124599</link>
    <description>&lt;P&gt;Dears,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am requesting your kind help regarding a log reported by third pary .&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I received a log from my third‑party security team indicating that my firewall is experiencing a Land Attack. The log shows that the source and destination IP addresses are the same, specifically tied to the firewall’s outside interface (public internet IP).&lt;BR /&gt;The log entry is as follows:&lt;/P&gt;&lt;P&gt;the log is&amp;nbsp;&amp;lt;162&amp;gt;2026-01-20T04:20:12Z FTD-FW : %FTD-2-106017: Deny IP due to Land Attack from x.x.x.x to x.x.x.x .&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, I am unable to find this event in the firewall’s own logs or monitoring dashboards.&lt;BR /&gt;To investigate, I reviewed all relevant configurations, including routing, NAT rules, security policies, and VPN settings, but I did not identify any misconfigurations or suspicious activity.&lt;/P&gt;&lt;P&gt;Thakn you guys&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 01 Mar 2026 07:23:14 GMT</pubDate>
    <dc:creator>ShareefKooliyodan0444</dc:creator>
    <dc:date>2026-03-01T07:23:14Z</dc:date>
    <item>
      <title>Assistance Required – Firewall Land Attack Logs</title>
      <link>https://community.cisco.com/t5/network-security/assistance-required-firewall-land-attack-logs/m-p/5373575#M1124599</link>
      <description>&lt;P&gt;Dears,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am requesting your kind help regarding a log reported by third pary .&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I received a log from my third‑party security team indicating that my firewall is experiencing a Land Attack. The log shows that the source and destination IP addresses are the same, specifically tied to the firewall’s outside interface (public internet IP).&lt;BR /&gt;The log entry is as follows:&lt;/P&gt;&lt;P&gt;the log is&amp;nbsp;&amp;lt;162&amp;gt;2026-01-20T04:20:12Z FTD-FW : %FTD-2-106017: Deny IP due to Land Attack from x.x.x.x to x.x.x.x .&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, I am unable to find this event in the firewall’s own logs or monitoring dashboards.&lt;BR /&gt;To investigate, I reviewed all relevant configurations, including routing, NAT rules, security policies, and VPN settings, but I did not identify any misconfigurations or suspicious activity.&lt;/P&gt;&lt;P&gt;Thakn you guys&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 01 Mar 2026 07:23:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/assistance-required-firewall-land-attack-logs/m-p/5373575#M1124599</guid>
      <dc:creator>ShareefKooliyodan0444</dc:creator>
      <dc:date>2026-03-01T07:23:14Z</dc:date>
    </item>
    <item>
      <title>Re: Assistance Required – Firewall Land Attack Logs</title>
      <link>https://community.cisco.com/t5/network-security/assistance-required-firewall-land-attack-logs/m-p/5373582#M1124600</link>
      <description>&lt;P&gt;There are at least two common causes of this issue that have nothing to do with security and are an issue with how the firewall interprets certain flows incorrectly. It can be caused by a NAT hairpin rule (same source and destination interface) as well as traffic going into and coming out of the same interface (often due to routing issues).&lt;/P&gt;
&lt;P&gt;There was also an old ASA bug related to this but it was long since resolved. (FTD runs LINA or ASA code as part of the underlying packet processing.)&amp;nbsp;&lt;A href="https://quickview.cloudapps.cisco.com/quickview/bug/CSCtr93086" target="_blank"&gt;https://quickview.cloudapps.cisco.com/quickview/bug/CSCtr93086&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 01 Mar 2026 08:11:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/assistance-required-firewall-land-attack-logs/m-p/5373582#M1124600</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2026-03-01T08:11:36Z</dc:date>
    </item>
    <item>
      <title>Re: Assistance Required – Firewall Land Attack Logs</title>
      <link>https://community.cisco.com/t5/network-security/assistance-required-firewall-land-attack-logs/m-p/5373586#M1124601</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; -&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1037350"&gt;@ShareefKooliyodan0444&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; This makes it also more difficult to troubleshoot :&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwj44531" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwj44531&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Sun, 01 Mar 2026 08:34:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/assistance-required-firewall-land-attack-logs/m-p/5373586#M1124601</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2026-03-01T08:34:16Z</dc:date>
    </item>
  </channel>
</rss>

