Bugzilla – Full Text Bug Listing |
Summary: | False duplicate frame detection using EDCA QoS data frames | ||
---|---|---|---|
Product: | ns-3 | Reporter: | CHep <hepner> |
Component: | mesh | Assignee: | Tom Henderson <tomh> |
Status: | NEEDINFO --- | ||
Severity: | normal | CC: | ns-bugs, sebastien.deronne, tomh |
Priority: | P5 | ||
Version: | ns-3.25 | ||
Hardware: | All | ||
OS: | All |
Description
CHep
2016-03-05 06:53:01 EST
Could you attach your scenario? Thanks! It looks like a mesh-related problem, as the referenced bug points to the mesh module. Can this bug be moved to the mesh module? This has more chance to be fixed if it is correctly assigned. The Bug occured in a Mesh Scenario that's right, however I don't think that it is just related to MESH as the Bug is in MacRxMiddle. I have not tested it but what would happen, if STA2 would be an AP and STA1 and STA3 the associated Clients? The Bug should occur as well. The Bug occurs in MacRxMiddle::IsDuplicate which is called in MacRxMiddle::Receive However the Problem is in MacRxMiddle::Receive if (!hdr->GetAddr1 ().IsGroup ()) {originator->SetSequenceControl (hdr->GetSequenceControl ()); In this part only Group adresses are neglected and the last sequence number is saved. There is a check needed if the currently received packet belongs to the receiving station. I just see this back in our basket. I unfortunately miss time to investigate mesh related issues, so I really think mesh people should have a look first and if it is confirmed to be pointing to wifi then I can have a look. Once again, it seems at first sight a mesh-related problem: - issue is seen since changes done in the mesh module; - reproduction case concerns a mesh scenario. If you want wifi people to investigate this, you should come with a better understanding about why this is for sure a bug in the wifi module. Moving back to mesh in the meantime... (In reply to sebastien.deronne from comment #5) > Once again, it seems at first sight a mesh-related problem: > - issue is seen since changes done in the mesh module; > - reproduction case concerns a mesh scenario. > > If you want wifi people to investigate this, you should come with a better > understanding about why this is for sure a bug in the wifi module. > > Moving back to mesh in the meantime... I will take this and look further into it.. it is not really in the mesh code but triggered by mesh use case, but anyway, we shall see. (In reply to Tom Henderson from comment #6) > (In reply to sebastien.deronne from comment #5) > > Once again, it seems at first sight a mesh-related problem: > > - issue is seen since changes done in the mesh module; > > - reproduction case concerns a mesh scenario. > > > > If you want wifi people to investigate this, you should come with a better > > understanding about why this is for sure a bug in the wifi module. > > > > Moving back to mesh in the meantime... > > I will take this and look further into it.. it is not really in the mesh > code but triggered by mesh use case, but anyway, we shall see. Thanks Tom. I am ok to take over investigation if you confirm this is a wifi bug. |