Meraki

SenaAK

Getting a configuration warning about MX67 IPv4 Status "Uplink IP address in conflict with another device", The WAN provider is Starlink. The IPv6 Status is "Active", does anyone know what would cause this?

RWelch

Here is the Meraki and Starlink Deployment Guide for your consideration. The likely culprit is CG-NAT telling the MX there is a IPv4 conflict even if IPv6 is unaffected.

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.

alemabrahao

Starlink uses CG-NAT for most of its plans, which means your MX67 is assigned a private IPv4 address instead of a true public IP. CG-NAT can cause Meraki to incorrectly detect an IP conflict, because multiple devices behind the same NAT may appear to be using the same IP from the perspective of the Meraki cloud.
This conflict warning is false-positive in most cases and does not necessarily indicate a real issue with your local network.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

SenaAK

Looks like this might be the case for us, but we went ahead and opened an issue with Meraki support. We have 15 sites and this is the only spoke that is giving us this warning.