<?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: Wireshark cap. is attached to in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/3999446#M196192</link>
    <description>&lt;P&gt;This discussion is already a few years old, but I wonder if you have ever found a solution for this. We have a similar problem between Huawei access points and controller.&lt;/P&gt;</description>
    <pubDate>Mon, 16 Dec 2019 15:18:42 GMT</pubDate>
    <dc:creator>rjanssen</dc:creator>
    <dc:date>2019-12-16T15:18:42Z</dc:date>
    <item>
      <title>Deny IP teardrop fragment</title>
      <link>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621807#M196187</link>
      <description>&lt;P&gt;Hey everyone.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Running ipsec between several locations.Getting the following on all remote Cisco ASA's.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Deny IP teardrop fragment (size = 744, offset = 0) from 10.150.0.2 to 10.150.4.x&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The 10.150.4.x is Aruba access points and the 10.150.0.2 is the Aruba controller. Everything works fine, but I am wondering about these denies. Can it be because the traffic between the access point and controller are already encrypted ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanx in advance for any feedback.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;UPDATE: attached wireshark log: teardrop-capture.zip&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:37:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621807#M196187</guid>
      <dc:creator>Jon Are Endrerud</dc:creator>
      <dc:date>2019-03-12T05:37:49Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621808#M196188</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Here is more information on this issue:-&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/syslog-guide/syslogs/logmsgs.html#pgfId-4768988&lt;/P&gt;

&lt;PRE&gt;
It is sometimes necessary to break up large packets of data into smaller
fragments before they can be sent across the network.  Each of these
fragments contains information that describes their position in the
original, unfragmented packet, so that when the fragmented data arrives
at its destination it can all be re-assembled in the proper order.  In a
teardrop attack, that positional information is deliberately falsified
so that the fragments overlap.  This can make some machines crash,
thereby causing a denial of service.  &lt;/PRE&gt;

&lt;P&gt;Do you have any Audit signatures enabled on the ASA device ?&lt;/P&gt;
&lt;P&gt;show run | in ip audit&lt;/P&gt;
&lt;P&gt;Thanks and Regards,&lt;/P&gt;
&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
      <pubDate>Thu, 12 Mar 2015 13:54:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621808#M196188</guid>
      <dc:creator>Vibhor Amrodia</dc:creator>
      <dc:date>2015-03-12T13:54:39Z</dc:date>
    </item>
    <item>
      <title>No audit on either sides of</title>
      <link>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621809#M196189</link>
      <description>&lt;P&gt;No audit on either sides of the ipsec.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Mar 2015 09:55:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621809#M196189</guid>
      <dc:creator>Jon Are Endrerud</dc:creator>
      <dc:date>2015-03-13T09:55:07Z</dc:date>
    </item>
    <item>
      <title>Hi,In that case , i think you</title>
      <link>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621810#M196190</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In that case , i think you might need to capture the traffic for these host which are showing up in the logs and verify the issue.&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
      <pubDate>Sat, 14 Mar 2015 06:50:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621810#M196190</guid>
      <dc:creator>Vibhor Amrodia</dc:creator>
      <dc:date>2015-03-14T06:50:05Z</dc:date>
    </item>
    <item>
      <title>Wireshark cap. is attached to</title>
      <link>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621811#M196191</link>
      <description>&lt;P&gt;Wireshark cap. is attached to orginal post. I see the packets, but not sure what to make of it.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Mar 2015 08:00:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/2621811#M196191</guid>
      <dc:creator>Jon Are Endrerud</dc:creator>
      <dc:date>2015-03-16T08:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Wireshark cap. is attached to</title>
      <link>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/3999446#M196192</link>
      <description>&lt;P&gt;This discussion is already a few years old, but I wonder if you have ever found a solution for this. We have a similar problem between Huawei access points and controller.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2019 15:18:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/3999446#M196192</guid>
      <dc:creator>rjanssen</dc:creator>
      <dc:date>2019-12-16T15:18:42Z</dc:date>
    </item>
    <item>
      <title>Re: Wireshark cap. is attached to</title>
      <link>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/4746088#M1096309</link>
      <description>&lt;P&gt;enabling netflow exporter to exporter address behind ipsec tunnel also produces tons of syslogs on remote asa. What's going on ?&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2022 13:14:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-ip-teardrop-fragment/m-p/4746088#M1096309</guid>
      <dc:creator>kerstin-534</dc:creator>
      <dc:date>2022-12-28T13:14:41Z</dc:date>
    </item>
  </channel>
</rss>

