Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
apart from no longer being able to use the combined dashboard.. so everything needs to be configured in 3 places instead of 1... we also noted that since switching to IP the host name of devices are less likely to be identified... and there is no way...
Why sniff them? why cant we just add our internal DNS server and have the meraki do a revers IP lookup ?what we do manually when trying to identify an IP good old "Ping -a <IP>"
You are in the same position as we where, except our L3 device was our VPN. Had to split the network and set it to Track by IPImmediately resolved the issue.. but now the dashboard is a PITA to use... we are planning on going global so this is FAR fr...
OK, So We are still experiencing slow website lookup and external service connection timeouts on v18.106 and had to roll back AGAIN! I have been informed by Meraki support that in our case, we have clients behind a non Meraki L3 device (our VPN) and ...
