Hi Guys,
Great product! I just installed to see the speed on my N+ wireless router and was surprised to see Max Rate as 54 rather than 300N. Is there any chance it could be reading it wrong from inSSIDer?
Thanks
Khalid
Hi Guys,
Great product! I just installed to see the speed on my N+ wireless router and was surprised to see Max Rate as 54 rather than 300N. Is there any chance it could be reading it wrong from inSSIDer?
Thanks
Khalid
Definitely possibleIf you can get a packet capture our way, that would help us a lot.
I'm seeing the same thing 54 (n). I have Dlink Dap-2553 that is 300N.
inSSIDer 2 is also reporting my Netgear WNR2000 (version 1) as having a Max Rate of 54 regardless of what rate the router is set. inSIDEer has no trouble spotting my neighbors' D-link as 130(N) and Linksys as 144(N). The Netgear software does detect the high rates, presumably correctly.
Sorry, but I have no clue on how to capture a packet. Probably no tool either.
As others have noted, my Netgear WNDR3700's Max Rate is shown as 54N when it is actually 300N. Privacy is displayed as RSNA-CCMP, it should be WPA2/PSK-AES. Using WireSHARK I have captured packets using the Cisco Linksys AE1000 wireless adapter. How do I get the capture to you? The file's extension is .pcap and is 1,921 KB in size . . .
Last edited by NatRay; 10-24-2010 at 01:03 AM.
Best regards,
Nat Ray
___________________
Netgear Firmware v1.0.4.68WW NxGenBeta
Cox Communications > Motorola SB5120 > Netgear RangeMax WNDR3700 > Ooma Telo / Cisco Catalyst 2924 XL
Telo Handset / Panasonic KX-TG6445 + 7 other handsets: 12 Total
3 Desktops / 4 Laptops / XBOX360 / Wii
VoIP QoS managed by router via Ethernet port . . .
Optimize your network: Disable IPv6
Some people get confused by RSNA-CCMP, it is WPA2-AES.
I suppose you could send the capture to support _at_ metageek _dot_ net.
The capture has 802.11 beacons in it, right?
Best regards,
Nat Ray
___________________
Netgear Firmware v1.0.4.68WW NxGenBeta
Cox Communications > Motorola SB5120 > Netgear RangeMax WNDR3700 > Ooma Telo / Cisco Catalyst 2924 XL
Telo Handset / Panasonic KX-TG6445 + 7 other handsets: 12 Total
3 Desktops / 4 Laptops / XBOX360 / Wii
VoIP QoS managed by router via Ethernet port . . .
Optimize your network: Disable IPv6
Tyler, I am still doing some home work, but I could not see any info in the beacons for our CISCO APs. I beleive the N150 v N300 will be based in the ability to support 40Mhz over the standard 20Mhz.
I am still looking, but I could not see any info in the beacons that would show faster speeds. I did see the 54Mbps values, but as each of those values MUST be stored in a single byte, that would make reporting anything above 255 very hard.
I beleive that the selected "Modulation Coding Scheme (MCS)" Will tell you what can happen.
eg: Have a look at : http://www.cisco.com/en/US/products/...80a3443f.shtml
eg: 64-QAM on 40Mhz = 300Mbps, 64-QAM on 20Mhz = 150Mhz.
The APs could simply advertise the basic set, then negotiate at connection to upto 64-QAM on 40. This you may not see it until you connect.
For the 20/40Mhz, this can be found in the HT Capabilities info 2nd (lowest) Bit (Bit 1). If set it will support both 20/40.
Bit 7 (8th lowest) in the same field also shows "Short GI for 40Mhz), then Bit 13 shows if 40Mhz can be used for DSSS/CCK
, But for info I am thinking 2nd bit would be enough.
Now, this is just a guess.
Under "HT Capabilities" there is a subsection "RX Supported MCS Set"
"IF" we can take those bits and match to the table from the above link, It would show that my ap supports all 15 MModulation and Coding Schemes.
Since I know it supports 40Mhz as outlined already, I could assum that the max speed would be 40Mhz 64-QAM, thus 300Mbps.
At this point the link between the above and the table is just a guess....
Edit: Have a look at this table as well. Seems to match : http://mcsindex.com/
Last edited by mwalker; 10-25-2010 at 11:23 PM.
inSSIDer currently uses the MCS index with the guard interval and the channel width to calculate the speed of the AP.
We just need to figure out why certain APs aren't reported correctly. If it's because the rates aren't advertised until connect, then there is no way for inSSIDer to detect the speeds.
In my sniff (via AirPCap) I can see the info in the beacon.
ie:
IEEE 802.11 Wireless LAN Management Frame
- Tagged parameters
-- HT Capabilities
--- RX Supported Modulation and Coding cheme Set
---- Tag Interpretation (RX Modulation and Coding Scheme)
Which, in my case has the low 16 bits (0-15) all set.
Did you get a valid trace yet ? If not, PM me and I will sent you a dump.
Cheers
Bookmarks