A network engineer is troubleshooting an IPv6 connectivity issue between two sites connected via a 6to4 tunnel. The tunnel is configured on both routers and shows as up/up, but the engineer cannot ping the IPv6 address of the remote tunnel endpoint. The engineer checks the routing table and sees no route to the remote IPv6 prefix. What is the most likely cause of this problem?
Trap 1: The tunnel mode is incorrectly set to ipv6ip instead of 6to4.
Incorrect because 'tunnel mode ipv6ip' is used for manual tunnels, not 6to4. However, the tunnel would still show up/up but might not encapsulate correctly; the primary issue is the source address.
Trap 2: The tunnel destination is misconfigured with the remote router's…
Incorrect because 6to4 tunnels do not use a tunnel destination; they use automatic destination derivation from the 6to4 prefix. A misconfigured destination would not cause the tunnel to come up.
Trap 3: The IPv6 address on the tunnel interface is not in the 2002::/16…
Incorrect because the tunnel interface IPv6 address is not required to be in 2002::/16 for the tunnel to work; the tunnel endpoint addresses are derived from the source IPv4 address.
- A
The tunnel source interface is configured with a private IPv4 address, causing the 6to4 prefix to be invalid.
Correct because 6to4 requires a global IPv4 address to form a valid 2002::/16 prefix. A private address leads to an invalid 6to4 address, preventing proper routing.
- B
The tunnel mode is incorrectly set to ipv6ip instead of 6to4.
Why wrong: Incorrect because 'tunnel mode ipv6ip' is used for manual tunnels, not 6to4. However, the tunnel would still show up/up but might not encapsulate correctly; the primary issue is the source address.
- C
The tunnel destination is misconfigured with the remote router's IPv6 address instead of its IPv4 address.
Why wrong: Incorrect because 6to4 tunnels do not use a tunnel destination; they use automatic destination derivation from the 6to4 prefix. A misconfigured destination would not cause the tunnel to come up.
- D
The IPv6 address on the tunnel interface is not in the 2002::/16 range.
Why wrong: Incorrect because the tunnel interface IPv6 address is not required to be in 2002::/16 for the tunnel to work; the tunnel endpoint addresses are derived from the source IPv4 address.