Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

When I capture with Wireshark, why can I see any TCP packets other than packets to and from my machine, even though another analyzer on the network sees those packets?

0
Posted

When I capture with Wireshark, why can I see any TCP packets other than packets to and from my machine, even though another analyzer on the network sees those packets?

0

You’re probably not seeing any packets other than unicast packets to or from your machine, and broadcast and multicast packets; a switch will normally send to a port only unicast traffic sent to the MAC address for the interface on that port, and broadcast and multicast traffic – it won’t send to that port unicast traffic sent to a MAC address for some other interface – and a network interface not in promiscuous mode will receive only unicast traffic sent to the MAC address for that interface, broadcast traffic, and multicast traffic sent to a multicast MAC address the interface is set up to receive. TCP doesn’t use broadcast or multicast, so you will only see your own TCP traffic, but UDP services may use broadcast or multicast so you’ll see some UDP traffic – however, this is not a problem with TCP traffic, it’s a problem with unicast traffic, as you also won’t see all UDP traffic between other machines. I.e., this is probably the same question as this earlier one; see the response t

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123