Your team is containerizing a pair of legacy network analyzers that must capture every Ethernet frame on the production VLAN. Each analyzer has to advertise its own unique IP and MAC address on the physical LAN, and the solution must avoid any kind of NAT or host-side port mapping. Which Docker network driver best meets these requirements when you create the container network?
The macvlan driver attaches a virtual interface to a specified parent interface and assigns the container its own Layer-2 identity-its own MAC address and an IP taken directly from the physical subnet. To the rest of the LAN the container looks like a separate host, so promiscuous-mode packet capture and direct inbound connections work without NAT. A user-defined bridge network, by contrast, sits behind a Linux bridge and normally uses IP masquerading; the host driver shares the host's existing stack instead of giving the container a new MAC; and the overlay driver builds VXLAN tunnels for multi-host connectivity rather than putting each container directly on the underlay segment. Therefore macvlan is the only choice that satisfies all stated conditions.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is promiscuous mode, and why is it necessary for network analyzers?
Open an interactive chat with Bash
How does the macvlan driver ensure each container gets a unique MAC and IP address?
Open an interactive chat with Bash
How does macvlan differ from the bridge driver in Docker networking?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Services and User Management
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access