Hi, I have a problem capturing packets on my wi-fi device. I have 2 computers - the first one is an access point and it sends a signal to the second computer. The signal is protected with wpa-psk password. Wireshark is installed on the first computer on which I want to see packets from the second computer. But I don't see them and I don't know why. A step by step description of what I did:
After I click "Start", Wireshark receives packets only for Local Area Connection. There are 0 packets coming for my wi-fi device and I don't know why. I can choose to see Local Area Connection traffic, but it only shows traffic on my computer and I don't want that. Btw, the icon of my Wireless Network Connection in Wireshark is the same as of Local Area Connection (I think it should have an icon of antenna)... Additional info:
ip config (copy/paste): Windows IP Configuration Wireless LAN adapter Wireless Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::20df:7d9e:ed40:91ae%11 IPv4 Address. . . . . . . . . . . : 192.168.1.100 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 Tunnel adapter isatap.{8353D0C0-BDC2-407A-B67D-1C43CE182F41}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 9: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:1811:6551:43fd:f38e Link-local IPv6 Address . . . . . : fe80::1811:6551:43fd:f38e%13 Default Gateway . . . . . . . . . : :: Tunnel adapter isatap.{170C612B-CC07-4916-9E68-82EFDB3ED1EA}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : asked 31 Oct '13, 13:51 myrddin |
One Answer:
Wi-Fi capturing doesn't work well on Windows with WinPcap, and Wireshark uses WinPcap to do capturing. You'd need an AirPcap card or need to run Linux or *BSD. answered 31 Oct '13, 17:40 Guy Harris ♦♦ |
Are you sure it is because of Windows? Because there is a version of Wireshark specifically designed to work under Windows and if it wouldn't work why would they put it on their website. But hey, what do I know...
Did you look at the link posted by Guy? It explains all the issues.
I guess one of those guys who put it on 'their' website is @Guy Harris ;-))
Oh OK, I guess he knows his stuff then :)
So, Linux, we meet again.