 | 1 | initial version |
Looking at the specs for that capture device, it is an RTL 8811AU and is 11ac/1SS/SGI (from the vendors' wireless performance table and a lookup on mcsindex.com). According to morrownr, if you believe such things, he says this chipset is not recommended for Linux.
A couple of issues - this probably does not have a default driver in Ubuntu, so where you get your driver matters (likely some place on Github or someone made a package). It is a low performance adapter, and since it can only pick up traffic that it can decode, if the AP and the phone are using more advanced modulation this adapter won't pick it up. We don't know anything about your AP or phone to know what 802.11 standards are supported / in use so no way to know if this capture device is suitable. Common clients over the past years were 11acW2/2SS, but there are others, and newer stuff is 11ax, sometimes even WiFi 6E operating on 6GHz.
Now with all of that, if you can't see ANY traffic from the device, you have bigger problems. Management and control traffic uses low modulations so all hosts can see them (for backwards compatibility) so I can only guess you are on the wrong channel, too far away, or that you have the wrong mac address filter in the capture. Assuming, of course, you have a driver configured and set the device into monitor mode properly and it really is picking up 802.11 monitor mode traffic. Check if you see the beacons from the AP under review.
Getting your adapter to work properly in Windows is not really a Wireshark question.
