[Ns-bugs] [Bug 1100] New: IPv6 fragmentation not handled correctly

[code@nsnam.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=1100

           Summary: IPv6 fragmentation not handled correctly
           Product: ns-3
           Version: ns-3-dev
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: internet
        AssignedTo: ns-bugs at isi.edu
        ReportedBy: tommaso.pecorella at unifi.it
   Estimated Hours: 0.0


Two separate issues, but close enough to need one single handler.

Both are related to this function:
uint8_t Ipv6ExtensionFragment::Process (Ptr<Packet>& packet, uint8_t offset,
Ipv6Header const& ipv6Header, Ipv6Address dst, uint8_t *nextHeader, bool&
isDropped)
found in ipv6-extension.cc

1st one:
when a fragment is received but it's not the last fragment (as is, more are
expected), it's called:
      NS_LOG_LOGIC ("Fragment. Drop!");
      m_dropTrace (packet);
This doesn't seems the correct behaviour, as the fragment is not really
dropped. This might lead to completely wrong statistics.

2nd one:
I have not found any method to "clean" the fragment buffer when a fragment is
lost in space/time.
If this is true, a long simulation might have memory issues (i.e., the buffer
will keep increasing).

I know that fragmentation should not really happen in IPv6, but still...

-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.