|
Bugzilla – Full Text Bug Listing |
| Summary: | Wrong argument for ResetBa in QosTxop::AddBaResponseTimeout | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Rediet <redieteab.orange> |
| Component: | wifi | Assignee: | sebastien.deronne |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs, tomh |
| Priority: | P5 | ||
| Version: | ns-3-dev | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | Patch to apply | ||
Similar patch pushed by Sébastien in changeset 13868:80bf979d57c9 |
Created attachment 3223 [details] Patch to apply There is a small typo in QosTxop::AddBaResponseTimeout: when scheduling ResetBa, current header's information is used instead of recipient. However, since AddBaResponseTimeout itself is scheduled, another packet can currently be handled upon expiry of the timeout. In our case, it was a broadcast frame which lead to a failed assert when calling ResetBa (non-existent agreement). Attached is a simple patch correcting this.