Skip to content

Commit aa0d1bd

Browse files
committed
OCPBUGS-15307: Clarity around MetalLB address resolution for L2
1 parent 3aaea1e commit aa0d1bd

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

modules/nw-metallb-layer2.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,10 @@
99

1010
In layer 2 mode, the `speaker` pod on one node announces the external IP address for a service to the host network.
1111
From a network perspective, the node appears to have multiple IP addresses assigned to a network interface.
12+
1213
[NOTE]
1314
====
14-
Since layer 2 mode relies on ARP and NDP, the client must be on the same subnet of the nodes announcing the service in order for MetalLB to work. Additionally, the IP address assigned to the service must be on the same subnet of the network used by the client to reach the service.
15+
In layer 2 mode, MetalLB relies on ARP and NDP. These protocols implement local address resolution within a specific subnet. In this context, the client must be able to reach the VIP assigned by MetalLB that exists on the same subnet as the nodes announcing the service in order for MetalLB to work.
1516
====
1617

1718
The `speaker` pod responds to ARP requests for IPv4 services and NDP requests for IPv6.

0 commit comments

Comments
 (0)