An Assertion Failure occurs from a packet size of 1472 Byte

74 views
Skip to first unread message

Peter Riedemann

unread,
Jan 12, 2016, 12:01:11 PM1/12/16
to ns-3-users
Hi,
I use ns3.22 with BRITE Integration. I have generated a BRITE Topology with NixVectorRouting like described in the BRITE Example 'brite-generic-example.cc'. A Client sends a message to an echo server that directly answers with the same message (UDP Echo Client/UDP Echo Server).

Everything works fine with a package size below 1472 Byte. Once I change the packet size to a value greater than 1472 Byte, the program terminates with the following exception:
At time 6.5s client sent 1473 bytes to 192.168.0.4 port 9
assert failed. cond="nixVector", file=../src/nix-vector-routing/model/ipv4-nix-vector-routing.cc, line=627
terminate called without an active exception
Command ['/home/peter/workspace_hs/ns3/ns-3.22/build/scratch/mydsl'] terminated with signal SIGIOT. 


Is this a bug of ns3.22? Or what should I do to solve the problem?

Best regards
Peter

Tommaso Pecorella

unread,
Jan 12, 2016, 1:08:42 PM1/12/16
to ns-3-users
Hi,

can you try with 3.24.1 ?
If it still doesn't work, please post a sample script so we can check it.

Thanks,

T.

Peter Riedemann

unread,
Jan 14, 2016, 4:07:24 AM1/14/16
to ns-3-users
Hi,

thank you very much for your answer. I have not tried it with ns3.24.1 so far. But I will do this today.
I've attached a small example and another file (.conf file) that is needed for generating a BRITE Topology. To run the example just copy both files into the "scratch" folder.
I will write
again as soon as I've tried the same example with ns3.24.1.


Thank you,
Peter
brite-example.cc
testFile.conf

Peter Riedemann

unread,
Jan 14, 2016, 5:05:12 AM1/14/16
to ns-3-users
Ok, using ns3.24.1 is no solution. The same Assertion Failure occurs once I change the packet size to 1473 Byte.

EDIT for using the example that I've uploaded above: You can change the packet size in line 122 of the example file (brite-example.cc).

Tommaso Pecorella

unread,
Jan 14, 2016, 11:37:50 AM1/14/16
to ns-3-users
Ok, I figured out what's happening.
The description and proposed solution is here: https://www.nsnam.org/bugzilla/show_bug.cgi?id=2266

It will be "live" as soon as I do all the checks.

Cheers,

T.
Reply all
Reply to author
Forward
0 new messages