SDWAN polices not working on wireless WHY

AnkitSharma1
Here to help

SDWAN polices not working on wireless WHY

We’ve noticed that when we apply SD WAN policies on our Meraki MX, they work correctly on wired connections but have no effect on our Verizon wireless (cellular) uplink. Latency is not getting reduce on wireless.

 

Can anyone explain why SD WAN policies don’t apply or don’t have any impact on the Verizon wireless router

 

We have MX connected to Verizon Internet Gateway and I am trying to apply VPN traffic

AnkitSharma1_0-1747401622071.png

 

5 Replies 5
alemabrahao
Kind of a big deal

Hi,

 

Verizon and other mobile carriers often use carrier-grade NAT, which hides the real public IP behind a shared IP, and this can interfere with VPN performance, path selection, and latency-based routing as the MX may not get accurate uplink telemetry.

 

But it would be interesting to contact support to confirm this.

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.
RaphaelL
Kind of a big deal
Kind of a big deal

What do you mean : they work correctly on wired connections but have no effect on our Verizon wireless (cellular)

 

You mean the cellular uplink on the MX ?

AnkitSharma1
Here to help

I mean we have some other with leased line. VPN polices works fine, we are able to reduce the site to site latency however it does not work on wireless connections 

RaphaelL
Kind of a big deal
Kind of a big deal

Exactly what do you mean by "wireless connections" ?

 

WAN 1 is WAN 1 and WAN 2 is WAN 2 , the MX doesn't "care" what ever you use on the back. It can be a DSL link or a cradlepoint with a LTE connection , it doesn't matter ( or shouldn't matter )

AnkitSharma1
Here to help

Exactly what do you mean by "wireless connections" ?

 

Verizon Wireless Business Gateway

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.
Labels