If using Infrastructure mode, see if the Access Point transmits the ARP query at 1Mbps or 11Mbps, not the orginating PC or cell phone. Start your ping test and see if the ARP query packets get transmitted at 1Mbps or 11Mbps. You'll now be able to capture *all* raw Wi-Fi traffic on the given channel, including control frames, corrupt frames, and you'll also be presented with non-frame metadata, including the RSSI and 802.11 physical layer transmission rate. With the "WiFi Scanning Options" dialog still open, switch back to the main window and start a traffic capture. To confirm if your Windows 7 PC or phone are incorrectly sending broadcasts at 11Mbps, use a second PC with Wi-Fi (or the Windows 7 PC when testing your cell phone), download Microsoft Network Monitor 3.4 (free), setup a capture on your Wi-Fi adapter (only), Click "Global Options.", Click "Scanning Options", Check "Switch to Monitor Mode", choose the appropriate Wi-Fi channel (normally channel 1 for Ad-hoc networks), and then hit "Apply" (not Close and Return to Local Mode).
Your problem certainly isn't related to IPv6, which is an entirely separate protocol stack and operates in parallel with IPv4. The Airpcap family is an open, affordable and easy-to-deploy wireless packet capture solution for MS Windows environments. The AirPcap family is an open, affordable and easy-to-deploy wireless packet capture solution for MS Windows environments.
It commmunicates just fine with the MRF24WB0M modules in both infrastracture and Ad-hoc mode. Free Downloads: Airpcap Adapter For Intel. I have an Atheros AR9287 based Wi-Fi card in my Windows 7 laptop. Therefore, if your Windows 7 PC and cell phone are both transmitting broadcasts at 11Mbps, it isn't going to work. By default, Widnows 7 doesn't modify its ARP cache in response to Gratuituous ARPs, unlike Windows XP. Are you trying to use an Ad-hoc network? If so, then most likely the same ARP broadcast issue you mentioned in an earlier thread is the reason it doesn't work.
0 kommentar(er)
