 | 1 | initial version |
With the updated configuration information, this is a common issue of captue setup. The source of the data to the printer is most likely using unicast communications to send data to the printer; another host, even when on the same subnet, will not usually receive that unicast data unless actions are taken. See the link on capture setup for some ideas on how you might go about this.
The wireless infrastructure will not forward unicast frames destined for other hosts directly to a third party; even if that third party can observe the frames in the air, which it might be able to, it will not pass them up the network stack without some action - might need configuration, setup, possible new hardware, etc.
Best thing to do is decide what the end goal is - some ideas - do you want to verify the traffic sent to the printer? If so, move Wireshark to the sending host directly instead of just some other host on the network.
Do you want to verify what the printer is receiving after network traversal? Then move the printer off wireless to wired, and install a network tap right at the printer. If it is a wireless printer only, consider installing a wireless capture system that supports monitor mode and has some decryption capability.
Other options of varying complexity are available depending on the actual problem to solve.
