About ww

ww

10.128.128.128 is a meraki AP ip. any fw rules configured?

ww

No bgp routing in the meraki switches

ww

No, but its also not a problem or is it? Your provider next hop is 2.2.x.x. you have to ask your wan2 provider for details. They maybe use this kind of ip to save public ip space. Or they want to avoid the possibility that your mx wan2 uplink is in the same range as one of you private range lan subnets. Your wan1 has a real public routable ip. Thats why the local (uplink)interface and wan1 shows the same ip

ww

Not in your device. Your provider does it in his network

ww

166.140 is the ip meraki dashboard is receiving data from. 2.2.2.2 is you private (or public) real local interface adres, in this case its doing nat somewhere.

ww

You can disable at appliance status > uplink > wan1

ww

You dont need a trunk. Create the vlan and assign the ip. Set the port to access and assign the vlan you just created

ww

if the dot is directly under AP, it could be the the case that device is only seen by that AP.

ww

It looks like your mikrotik supports more then 1 IP on the interface/default vlan. Meraki only support 1 IP/subnet for each vlan interface. So you need to (re)design your network based on vlans

ww

Where are the clients connected and what vlan is on the access port and on the trunk port connected to the mx? What ip and gateway has client 1 and ips1 ?

ww

When Static ip is set you have the vlan field empty?

ww

i dont know. But i "think" meraki does not use the rate limit on their DAI implementation. but its just a guess...

ww

In think its: Local, remote and static routes. It just does not learn routes send from the nexus. But if i read the first few lines of documentation , it should work how you described it..

ww

The second solution i gave you should also work

ww

Highest vlan in vpn https://documentation.meraki.com/MX/Other_Topics/MX_and_Z1_Source_IP_for_RADIUS_Authentication

ww

its some kind of dummy demo dashboard that does not really have a internet connection. if i login there i also cant ping 8.8.8.8 or use dashboard throughput test. so i guess that part of the demo is not working .

ww

when its "down" the mx does not function anymore? or is it the management part that cant connect the meraki cloud? The wan port is using a static assigned IP or DHCP?

ww

With autovpn https://documentation.meraki.com/MX/Site-to-site_VPN/Meraki_Auto_VPN

ww

https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-site_VPN_Firewall_Rule_Behavior

ww

Did you set the wan bandwidth correct on the mx? You cant see any queuing , i dont know if support can. EF however don' t use one of the 3 configurable queues anymore https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Using_Packet_Prioritization_on_a_Traffic_Shaping_Rule Is the mx reporting packet loss or high latency when you have voip problems?

ww

No

ww

I think only meraki support can help with this. Next time don't delete anything before succesfully added devices/licences to your new network/org.

ww

Yes, but based on ip. For example Source 10.10.10.0/24 dest: any uplink: wan2

ww

I assume pa2 takes over the Ip of pa1.(vrrp)

ww · ‎06-11-2020

There are some other topics about this. however at some switch types this works or worked before and some types do not work at all, but its recommended to have the management ip of the svi/core switch in the uplink subnet. https://community.meraki.com/t5/Switching/Management-VLAN/m-p/19025

ww

Community Record

Badges