nerdexam
Linux_Foundation

LFCS · Question #375

An administrator is capturing traffic with Wireshark and is only seeing ARP traffic. What is the most likely cause of this?

The correct answer is B. The machine is on a switched network and is therefore only seeing local and broadcast/multicast packets. If Wireshark only shows ARP traffic on a machine, it's most likely because the machine is connected to a switched network, which by default only forwards traffic directly addressed to the machine, broadcast, and multicast traffic.

Submitted by manish99· Apr 18, 2026Networking

Question

An administrator is capturing traffic with Wireshark and is only seeing ARP traffic. What is the most likely cause of this?

Options

  • AThe network interface on which the scan is running is not in promiscuous mode.
  • BThe machine is on a switched network and is therefore only seeing local and broadcast/multicast packets.
  • CThe administrator did not enable the TCP and UDP options when starting the scan.
  • DThe network interface on which the scan is running has the ARP_ONLY flag set.

How the community answered

(27 responses)
  • B
    89% (24)
  • C
    4% (1)
  • D
    7% (2)

Why each option

If Wireshark only shows ARP traffic on a machine, it's most likely because the machine is connected to a switched network, which by default only forwards traffic directly addressed to the machine, broadcast, and multicast traffic.

AThe network interface on which the scan is running is not in promiscuous mode.

While promiscuous mode allows an interface to capture all traffic it *sees*, on a switched network, the interface still won't see unicast traffic destined for other hosts unless port mirroring is configured.

BThe machine is on a switched network and is therefore only seeing local and broadcast/multicast packets.Correct

In a switched network environment, a network switch intelligently forwards unicast traffic only to the port where the destination MAC address resides. Therefore, a sniffing station on a switched network will naturally only see its own unicast traffic, as well as broadcast and multicast traffic (like ARP requests, DHCP, etc.), unless specific techniques like port mirroring (SPAN) are employed.

CThe administrator did not enable the TCP and UDP options when starting the scan.

Wireshark captures all packets by default (or based on capture filters), regardless of whether specific protocols like TCP and UDP are explicitly 'enabled'.

DThe network interface on which the scan is running has the ARP_ONLY flag set.

There is no standard 'ARP_ONLY flag' that can be set on a network interface to restrict it to only ARP traffic; this is a fictitious setting.

Concept tested: Network sniffing on switched networks

Source: https://www.wireshark.org/docs/wsug_html_chunked/ChIntroNetworkSniffing.html

Topics

#Network Sniffing#Wireshark#Switched Networks#ARP

Community Discussion

No community discussion yet for this question.

Full LFCS Practice