Bugzilla – Bug 2728
ns3::MeshInformationElementVector printing error
Last modified: 2017-04-24 11:00:16 EDT
Created attachment 2835 [details] bug example When you try to print the mesh packets (e.g., by simply printing them in the mesh example), you get this error: 1.00096 *Packet*: ns3::WifiMacHeader (MGT_BEACON ToDS=0, FromDS=0, MoreFrag=0, Retry=0, MoreData=0 Duration/ID=0us, DA=ff:ff:ff:ff:ff:ff, SA=00:00:00:00:00:05, BSSID=00:00:00:00:00:05, FragNumber=0, SeqNumber=10) ns3::MgtProbeResponseHeader (ssid=, rates=[*6mbs 9mbs 12mbs 18mbs 24mbs 36mbs 48mbs 54mbs], DSSS Parameter Set= , ERP information=0|0|0, HT Capabilities=0|0|0|0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 , HT Operation=0|0|0 , VHT Capabilities=0|0 , VHT Operation=0|0|0|0 , HE Capabilities= 0|0|0|0|0) ns3::MeshInformationElementVector (msg="Information element 0 is not implemented", file=../src/wifi/model/wifi-information-element-vector.cc, line=98 libc++abi.dylib: terminating Command ['/Users/pecos/Development/workspace/ns-3-dev/build/scratch/mesh-2'] terminated with signal SIGIOT. Run it under a debugger to get more information (./waf --run <program> --command-template="gdb --args %s <args>"). Either the MeshInformationElementVector is misplaced, or it is misinterpreted.
I forgot to mention: the bug has been reported by Daniel Oliva Domingues in this thread: https://groups.google.com/forum/#!topic/ns-3-users/M9AcGCSJicI
This is a duplicate of 1482 and 2505; see bug 2505. *** This bug has been marked as a duplicate of bug 2505 ***
Created attachment 2837 [details] another test case
Again, this is not a case of bad packet printing. As one can see from the 2nd test case I posted (mentioned here: https://groups.google.com/forum/#!topic/ns-3-users/qVBzEP1A8_k) the problem is different. If one looks at the pcap file, the packet is marked with an HT capabilities tag (802.11n, but the network is 802.11b/g only), and the tag length is wrong (51 bytes instead of 26). This is the root of the bug, even of the printing one.