|
Bugzilla – Full Text Bug Listing |
| Summary: | WiFi script (candidate 802.11p test script) works in ns-3.19, not in ns-3.20 | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Scott Carpenter <scarpen> |
| Component: | wave module | Assignee: | Daniel L. <nikkipui> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs |
| Priority: | P5 | ||
| Version: | ns-3.20 | ||
| Hardware: | PC | ||
| OS: | Windows | ||
| Attachments: | VANET routing compare script (for debugging) | ||
Fixed locally. 802.11p PHY mode was set up to use an invalid device rate. ns-3.20 now logs this as incompatibility, and drops packets for unsupported rates (thanks, whoever added that!) |
Created attachment 1850 [details] VANET routing compare script (for debugging) I have a candidate WAVE/WiFi/802.11p example script which works for me in ns-3.19, but not for ns-3.20. I suspect this is some kind of side-effect of changes to ns-3.20???? I cannot easily find the issue, but I suspect it has something to do with the way I am sending and/or receiving the WAVE packets and/or the routing data (i.e. AODV). When I run the script using ns-3.19, there is output (10 simulation seconds, and an output line for each second showing non-zero PDR and Goodput. However, when I run the same script in ns-3.20, the output is always PDR=0 and Goodput=0 (indicating that sent pkts are not being received in my code). Can others please test and confirm, guide me, help? I just drop the script in scratch, and run as ./waf --run scratch/vanet-routing-compare-test