Bug 2407 - Packet Metadata Bad State with Small Packet Size
Packet Metadata Bad State with Small Packet Size
Status: NEEDINFO
Product: ns-3
Classification: Unclassified
Component: network
unspecified
Other Linux
: P5 normal
Assigned To: ns-bugs
:
: 2415 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-09 18:46 EDT by Salazar
Modified: 2016-09-20 01:57 EDT (History)
2 users (show)

See Also:


Attachments
wscript file and example application as described above (2.41 KB, application/zip)
2016-05-09 18:46 EDT, Salazar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Salazar 2016-05-09 18:46:31 EDT
Created attachment 2424 [details]
wscript file and example application as described above

While using the bulk-send-application, I enabled PacketMetadata and then proceeded to change the size of the pack from default value of 512 byte to something small, such as 16 bytes. When running the simulation, I get the following error message:

assert failed. cond="IsStateOk ()", file=../src/network/model/packet-metadata.cc, line=877
terminate called without an active exception


I've included two files to help illustrate this error:
wscript - belongs in examples/tcp/
tcp-bulk-send-small-packet.cc - belongs in examples/tcp/tcp-bulk-send-small-packet.cc

Once compiled, you can run the example and try the different values for the size of the packet as follows:

./waf --run "tcp-bulk-send-small-packet --sendSize=16 --maxBytes=0"

For reference, it looks like it fails with a size less than 28 in this example, but I've had this as an error for sizes less than 20 for another example.
Comment 1 Tom Henderson 2016-09-20 01:56:55 EDT
I'm not able to reproduce on ns-3-dev, for various send sizes; e.g.

./waf --run 'tcp-bulk-send-small-packet --sendSize=16 --maxBytes=0'
'build' finished successfully (3.622s)
Total Bytes Received: 11267984 

will leave open until after the 3.26 release and close if no further information is available
Comment 2 Tom Henderson 2016-09-20 01:57:12 EDT
*** Bug 2415 has been marked as a duplicate of this bug. ***