This is one of the millions of settings your administrator can configure. They might have even marked it "User controllable", so you can configure the action in Cisco Secure Client yourself.
... View more
Hi, I have never tried it on an MX, but you could try using a source-based route at the bottom of addressing and vlans page. just be very specific and careful, as you can take down your whole network.
... View more
Thanks for elaborating on your setup! I did try using a Mac running Windows 10 the other day and there it was no trouble accessing any of the internal websites and having: Synology DNS 8.8.8.8 8.8.4.4 deployed via DCHP. What I did now was to change in Meraki so it only deploys (via DHCP) the DNS coming from Synology. The Synology itself will forward addresses it can't resolve to 8.8.8.8 and 8.8.4.4. Seems to work fine now and I don't get the wired behavior for internal addresses depending on the browser used in MacOS that I described in my original post. At the same time I think it would be good to have a DNS backup in case the Synology goes down. So I'll continue to investigate what this behaves the way it does in MacOS.
... View more
The reason for my trouble in this thread was that we had ”Statics routes” setup in: Security & SD-WAN -> Addressing & VLANs And the IP address for https://securelogin.bmw.com/ was covered within that range and therefore the the traffic was being routed internally instead of externally. Sorry for the confusion and thanks all for trying to help! 🙂
... View more
A bit unsure how to set it up. If I just need VPN tunneling to a few specific IP addresses on our LAN, how do I specify that? Would that help with performance instead of routing all traffic via the VPN (I guess it would)? Sorry for my ignorance and thanks for the help!
... View more
Getting this same problem now and then (”802.11 Disassociation - Unknown Reason”) on MR42 access point running firmware MR 28.7.1. It has been working fine since a couple of weeks ago when the disconnects started. Don't know of anything that has changed on our side. Could it be something with the firmware for the access point? We're running the currently released version as of this writing. Any ideas on what to do to solve this?
... View more
