About ww

ww

what is the destination port in the third screenshot? i cant read it correctly

ww

you are matching on destination ip or port. but your wireshark info shows other destination ip and port

ww

have seen the same on 67c. needed to rma.

ww

warm spare is not active active. you could run both providers to both mx's if you have enough IP addresses between the provider and your MX's . https://community.meraki.com/t5/Security-SD-WAN/Does-MX-device-can-support-dual-active/m-p/64242#M16273 so the WAN ports can be both active, but not Both MX's (in warm spare) at the same time

ww

Note: Layer 3 firewall rules configured in group policy are stateless, and corresponding rules may be required for return traffic. assuming i read this correctly, then its only outbound . but most sessions need 2-way traffic to establish so it would still be blocked in many cases..

ww

https://documentation.meraki.com/MR/Group_Policies_and_Blacklisting/Using_RADIUS_Attributes_to_Apply_Group_Policies https://emtunc.org/blog/02/2014/vlan-tagging-per-active-directory-group-with-meraki-access-point/

ww

yes that is what the spec datasheet says. so you bought the wrong product. maybe you can buy a small (8 port?) switch and connect that for the half duplex clients

ww

now its removed from the dashboard? 😅

ww

https://developer.cisco.com/meraki/api/#/rest/getting-started/rate-limit

ww

Nice. but why not also add the duplex status

ww

https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page

ww

with the group policy you can bypass splash

ww

Network-wide > Configure > General https://documentation.meraki.com/MR/Other_Topics/Manually_Integrating_Cisco_Umbrella_with_Meraki_Networks

ww

supported modems https://documentation.meraki.com/MX/Cellular/3G_-_4G_Cellular_Failover

ww

you could prepare a script to undo you changes using the API. Meraki should make some kind of snapshot/save state where you can revert back to.

ww

https://community.meraki.com/t5/Security-SD-WAN/Traffic-Shaping-Rules/m-p/44155#M11178

ww

use the firewall? https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Firewall_Settings

ww

you dont have a license or order-id that you can claim?

ww

its already for a long time in the change logs. i dont know if this is correct... why would it work in standalone but not in warm spare... did someone test this?

ww

https://documentation.meraki.com/MX/Deployment_Guides/MPLS_Failover_to_Meraki_Auto_VPN

ww

then you need also 100.x subnet on meraki and trunk them both to the juniper. otherwise 0.1 is your only next hop

ww · ‎09-13-2019

maybe you can add some design drawings from your underlay and vpn overlay and explain where you application is hosted and how you route it into your vpn? this issue is new or has been there always? your mpls 1 and 2 run to the same dc/application? problem is with one specific application or more apllications? your hubs are in concentrator mode?

ww · ‎09-09-2019

traceroute to your gateway, fw and beyond your fw to the internet. and look in your fw logs

ww · ‎09-09-2019

your ssid is in bridge mode? your coreswitch connects Wi-Fi AP's? or did you add the vlan to all switches. does the coreswitch send the related dhcp packet to the AD , and the AD receives the dhcp packet?

ww · ‎09-08-2019

looks more like a message regarding a mx from another network in your org? i would call support or create a case on the dashboard at help> cases.

ww

Community Record

Badges