Bug 935 - 802.11a devices communicate with 802.11b devices
802.11a devices communicate with 802.11b devices
Status: RESOLVED INVALID
Product: ns-3
Classification: Unclassified
Component: wifi
ns-3.8
PC Linux
: P2 normal
Assigned To: Nicola Baldo
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-03 20:16 UTC by Yang Chi
Modified: 2010-06-07 20:54 UTC (History)
2 users (show)

See Also:


Attachments
sample code used to reproduce this bug (4.95 KB, text/plain)
2010-06-03 20:17 UTC, Yang Chi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yang Chi 2010-06-03 20:16:27 UTC
When the channel numbers are set to the same number, 802.11a devices communicate with 802.11b devices in ns-3. This happens in both stable versions: 3.7 and 3.8. Sample codes attached to reproduce this bug.
Comment 1 Yang Chi 2010-06-03 20:17:41 UTC
Created attachment 911 [details]
sample code used to reproduce this bug
Comment 2 Quincy Tse 2010-06-07 01:53:35 UTC
But 11a and 11b devices shouldn't have the same channel numbers.

The lowest channel for 802.11a is Ch. 34, and the highest channel for 802.11b/g is 11.
Comment 3 Nicola Baldo 2010-06-07 04:40:15 UTC
(In reply to comment #2)
> But 11a and 11b devices shouldn't have the same channel numbers.

I agree with Quincy. I am closing this bug as invalid. Yang, please feel free to reopen this bug with further comments if you think that we are in error.
Comment 4 Yang Chi 2010-06-07 17:35:38 UTC
I see. my own mistake. Everytime I install ns-3, I change the base frequency of 11a to 5017 first...(yans-wifi-phy.cc). I forgot this when I reported the bug. Thx for comments.
Comment 5 Quincy Tse 2010-06-07 20:54:16 UTC
Having said that, since I don't know how the channels have been implemented, there may still be a hidden problem later on for the case 802.11p and 802.11a/n devices. I understand that there is an overlap there. 11p uses half the channel bandwidth and really shouldn't be able to communicate with 11a/n.

I won't reopen the bug though.