 | 1 | initial version |
At the ethernet packet level, I can only see packets between my router and my computer.
...
And this is despite the fact that I put a tick in the check box for promiscuous mode, for my wi-fi adapter
Ethernet and Wi-Fi are different here, even though, if you're not in monitor mode, the packets you see will be "faked" Ethernet packets, with a fake Ethernet header constructed from the Wi-Fi header (Wireshark doesn't do that, the adapter and its driver do that).
For Ethernet, the most likely reason why other hosts' packets don't show up in a capture is that the capture is being done on a switched network. See the Wireshark Wiki's page on Ethernet capturing for a discussion of this.
For Wi-Fi, the most likely reason is that you're not capturing in monitor mode, which is the only mode that supports capturing third-party traffic. See the Wireshark Wiki's page on Wi-Fi capturing for a discussion of this, and note that, on a "protected" network, using WEP or some version of WPA, you will also need to have Wireshark decrypt the captured packets. See the Wireshark Wiki page on decrypting 802.11.
| | 2 | No.2 Revision |
At the ethernet packet level, I can only see packets between my router and my computer.
...
And this is despite the fact that I put a tick in the check box for promiscuous mode, for my wi-fi adapter
Ethernet and Wi-Fi are different here, even though, if you're not in monitor mode, mode - even if you're in promiscuous mode! - the packets you see will be "faked" Ethernet packets, with a fake Ethernet header constructed from the Wi-Fi header (Wireshark doesn't do that, the adapter and its driver do that).
For Ethernet, the most likely reason why other hosts' packets don't show up in a capture is that the capture is being done on a switched network. See the Wireshark Wiki's page on Ethernet capturing for a discussion of this.
For Wi-Fi, the most likely reason is that you're not capturing in monitor mode, which is the only mode that supports capturing third-party traffic. See the Wireshark Wiki's page on Wi-Fi capturing for a discussion of this, and note that, on a "protected" network, using WEP or some version of WPA, you will also need to have Wireshark decrypt the captured packets. See the Wireshark Wiki page on decrypting 802.11.
| | 3 | No.3 Revision |
At the ethernet packet level, I can only see packets between my router and my computer.
...
And this is despite the fact that I put a tick in the check box for promiscuous mode, for my wi-fi adapter
Ethernet and Wi-Fi are different here, even though, if you're not in monitor mode - even if you're in promiscuous mode! - the packets you see will be "faked" Ethernet packets, with a fake Ethernet header constructed from the Wi-Fi header (Wireshark doesn't do that, the adapter and its driver do that).
For Ethernet, the most likely reason why other hosts' packets don't show up in a capture is that the capture is being done on a switched network. See the Wireshark Wiki's page on Ethernet capturing for a discussion of this.
For Wi-Fi, the most likely reason is that you're not capturing in monitor mode, which is the only mode that supports capturing third-party traffic. traffic; promiscuous mode does not support that on Wi-Fi. See the Wireshark Wiki's page on Wi-Fi capturing for a discussion of this, and note that, on a "protected" network, using WEP or some version of WPA, you will also need to have Wireshark decrypt the captured packets. See the Wireshark Wiki page on decrypting 802.11.
