<?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: What does ip virtual-reassembly do????? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/what-does-ip-virtual-reassembly-do/m-p/3175612#M1055313</link>
    <description>&lt;P&gt;Very nicely done. One thing though , can you specify how many packets are the limit of tresh hold ?&lt;/P&gt;</description>
    <pubDate>Thu, 24 Aug 2017 22:41:44 GMT</pubDate>
    <dc:creator>Velos-itnet</dc:creator>
    <dc:date>2017-08-24T22:41:44Z</dc:date>
    <item>
      <title>What does ip virtual-reassembly do?????</title>
      <link>https://community.cisco.com/t5/network-security/what-does-ip-virtual-reassembly-do/m-p/602224#M1055309</link>
      <description>&lt;P&gt;I found one link on cisco website explaining a little about virtual reassembly, what I dont understand is when I enable that option on my tunnel interface why I cannot ping packets larger than 1420 from the other end of the tunnel??  When I disable virtual-reassembly on the tunnel interfaced ping packets go thru fine as large as 1500.  Why??  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/ps6350/products_configuration_guide_chapter09186a0080455ad0.html" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/ps6350/products_configuration_guide_chapter09186a0080455ad0.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Tunnel1&lt;/P&gt;&lt;P&gt; bandwidth 3072&lt;/P&gt;&lt;P&gt; ip address xxx.xxx.xxx.xxx&lt;/P&gt;&lt;P&gt; ip nat inside&lt;/P&gt;&lt;P&gt; ip tcp adjust-mss 1420&lt;/P&gt;&lt;P&gt; ip virtual-reassembly&lt;/P&gt;&lt;P&gt; tunnel source Loopback1&lt;/P&gt;&lt;P&gt; tunnel destination 192.168.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The GRE tunnel is being encrypted locally on the router FYI.  And CBAC firewall IOS installed as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:46:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/what-does-ip-virtual-reassembly-do/m-p/602224#M1055309</guid>
      <dc:creator>glenthms</dc:creator>
      <dc:date>2020-02-21T08:46:01Z</dc:date>
    </item>
    <item>
      <title>Re: What does ip virtual-reassembly do?????</title>
      <link>https://community.cisco.com/t5/network-security/what-does-ip-virtual-reassembly-do/m-p/602225#M1055311</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;VFR is responsible for detecting and preventing the following types of fragment attacks: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#149;Tiny Fragment Attack&amp;#151;In this type of attack, the attacker makes the fragment size small enough to force Layer 4 (TCP and User Datagram Protocol (UDP)) header fields into the second fragment. Thus, the ACL rules that have been configured for those fields will not match. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VFR drops all tiny fragments, and an alert message such as follows is logged to the syslog server: "VFR-3-TINY_FRAGMENTS." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#149;Overlapping Fragment Attack&amp;#151;In this type of attack, the attacker can overwrite the fragment offset in the noninitial IP fragment packets. When the firewall reassembles the IP fragments, it might create wrong IP packets, causing the memory to overflow or your system to crash. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VFR drops all fragments within a fragment chain if an overlap fragment is detected, and an alert message such as follows is logged to the syslog server: "VFR-3-OVERLAP_FRAGMENT." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#149;Buffer Overflow Attack&amp;#151;In this type of denial-of-service (DoS) attack, the attacker can continuously send a large number of incomplete IP fragments, causing the firewall to lose time and memory while trying to reassemble the fake packets. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To avoid buffer overflow and control memory usage, configure a maximum threshold for the number of IP datagrams that are being reassembled and the number of fragments per datagram. (Both of these parameters can be specified via the ip virtual-reassembly command.) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the maximum number of datagrams that can be reassembled at any given time is reached, all subsequent fragments are dropped, and an alert message such as the following is logged to the syslog server: "VFR-4_FRAG_TABLE_OVERFLOW." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the maximum number of fragments per datagram is reached, subsequent fragments will be dropped, and an alert message such as the following is logged to the syslog server: "VFR-4_TOO_MANY_FRAGMENTS." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In addition to configuring the maximum threshold values, each IP datagram is associated with a managed timer. If the IP datagram does not receive all of the fragments within the specified time, the timer will expire and the IP datagram (and all of its fragments) will be dropped. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Mar 2006 12:13:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/what-does-ip-virtual-reassembly-do/m-p/602225#M1055311</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2006-03-14T12:13:44Z</dc:date>
    </item>
    <item>
      <title>Re: What does ip virtual-reassembly do?????</title>
      <link>https://community.cisco.com/t5/network-security/what-does-ip-virtual-reassembly-do/m-p/3175612#M1055313</link>
      <description>&lt;P&gt;Very nicely done. One thing though , can you specify how many packets are the limit of tresh hold ?&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2017 22:41:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/what-does-ip-virtual-reassembly-do/m-p/3175612#M1055313</guid>
      <dc:creator>Velos-itnet</dc:creator>
      <dc:date>2017-08-24T22:41:44Z</dc:date>
    </item>
    <item>
      <title>Re: What does ip virtual-reassembly do?????</title>
      <link>https://community.cisco.com/t5/network-security/what-does-ip-virtual-reassembly-do/m-p/3179688#M1055315</link>
      <description>&lt;P&gt;Run the command below and you will see the parameters configured for each interface&lt;/P&gt;&lt;P&gt;For my case, the GigabitEthernet interface is with the default values, since I only enabled&amp;nbsp;&lt;STRONG&gt;&lt;EM&gt;ip virtual-reassembly in.&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;RT01&lt;/SPAN&gt;&lt;SPAN&gt;# &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;show running-config interface gi0/0&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;interface GigabitEthernet0/0&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;&amp;nbsp;ip virtual-reassembly in&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;RT01#&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;show ip virtual-reassembly&lt;/STRONG&gt; &lt;/FONT&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;GigabitEthernet0/0:&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;Virtual Fragment Reassembly (VFR) is ENABLED [in]&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;Concurrent reassemblies (max-reassemblies): 16&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;Fragments per reassembly (max-fragments): 32&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;Reassembly timeout (timeout): 3 seconds&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;Drop fragments: OFF&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Current reassembly count:0&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;Current fragment count:0&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;Total reassembly count:8134&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;Total reassembly timeout count:0&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope I have helped.&lt;/P&gt;&lt;P&gt;Best regards.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Sep 2017 11:18:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/what-does-ip-virtual-reassembly-do/m-p/3179688#M1055315</guid>
      <dc:creator>evertonpsp</dc:creator>
      <dc:date>2017-09-04T11:18:24Z</dc:date>
    </item>
  </channel>
</rss>

