Description

In an EVPN/VXLAN environment, a spoofed or crafted ARP reply matching the IP and MAC address of a remote gateway may cause an inconsistency between the MAC and MAC-IP state maintained by the device.


Under the affected condition, the MAC entry for the remote gateway remains associated with the correct remote EVPN ESI, while the corresponding MAC-IP entry may incorrectly be updated to the local interface on which the spoofed ARP packet was received.


This results in an inconsistent MAC-IP state and can prevent ARP traffic from being correctly forwarded toward the remote gateway, causing loss of gateway connectivity for affected clients.

Symptoms

The following symptoms may be observed:

  • Clients are unable to reach their default gateway.
  • Gateway connectivity is restored when the crafted/spoofed ARP traffic is no longer present.
  • The MAC entry for the gateway continues to point to the expected remote EVPN ESI.
  • The corresponding MAC-IP entry incorrectly points to the local ingress interface.
  • MAC and MAC-IP state may become inconsistent.
  • ARP resolution or forwarding toward the remote gateway fails.
  • The issue can be reproduced when a crafted ARP reply is received for an existing remote gateway IP/MAC.


The issue occurs due to an inconsistency in the handling of MAC-IP updates between L2ALM and L2ALD.

L2ALM could update the existing MAC-IP entry based on the input ARP/NDP interface before receiving acknowledgement from L2ALD. If L2ALD subsequently rejected the update, the previous MAC address, interface index, and MAC-IP flags were not restored correctly.


As a result, the MAC and MAC-IP states could become inconsistent.


Solution

The software correction ensures that changes to the MAC address, interface index, and MAC-IP flags are committed only after successful acknowledgement from L2ALD.

The existing handling for invalid MAC conditions remains unchanged.

The fix is included in the following Junos releases:

  • Junos 23.4R2-S10
  • Junos 25.4R2
  • Junos 26.2R2
  • Junos 26.4R1


If an upgrade is not immediately possible, the following workarounds may be considered:

  1. Configure a static ARP entry for the affected gateway.
  2. Configure an IRB interface on the affected VLAN, where applicable.


Modification History

2026-10-05 : Article Created