Meraki

cfemfrl · ‎May 28 2021

Thanks to you both... You are right, @Bruce, it's right there in that link/document: Default Route When configuring Hubs for a Spoke, there is an option to select a hub as being a Default route. If this option is selected, then that hub will be configured as a default route for the Spoke (0.0.0.0/0). Any traffic that is not sent to a configured VPN peer network, static route or local network will be sent to the default route I checked that box, and outbound traffic is from Building A IP as desired. Thanks again for helping out a novice!

cfemfrl · ‎May 27 2021

Not sure exactly what you are trying to achieve, what IP addresses do you want your internet traffic to come from? I want anyone connected to the Z3 to have Building A's IP. My laptop (non-Z3, connected anywhere) has Building A's IP when I am Client VPN'ed to it. Sorry if I am unclear. Thanks for replying and the link; will check it out!

cfemfrl · ‎May 27 2021

Not sure if my subject line is correct, but here's what I have: Four buildings with hub site-to-site VPN on MX84 - stable for long time An underutilized Z3 that is spoke site-to-site VPN to "Building A" - stable for long time I often connect my laptop from anywhere using Meraki's Client VPN to "Building A" w/ Cloud Authentication. - also stable for long time. What I now need to do: Deploy Z3 elsewhere. I have most things on the Z3 set up as desired.... I can get to data anywhere in the four buildings. My issue is with outbound internet traffic. Traffic going to the internet is broadcast with the Z3's internet provider's IP. Conversely, when I am on my laptop Client VPN-ing, my outbound internet traffic is broadcast with Building A's external IP. I need the Z3 to act this way (broadcast A's IP) but am unsure on how to do this. I was going to try things like VPN Concentrator but it seems some of these changes might have unintended consequences with my VLAN configs, etc. So out of caution, I ask here instead of experiment.

cfemfrl · ‎Jan 9 2020

MX only; thanks! Used to be there.

cfemfrl · ‎Jan 9 2020

Thanks for the info. I suspected it was new html/css (so to speak) that made the change. Didn't know there were tweaked interface pages rolling out. I recognize change happens; just wish I didn't lose functionality (albeit minor). If I'm missing a flag, config, etc that would allow splash auth details to be displayed, please let me know!

cfemfrl · ‎Jan 9 2020

Hello, all - I've noticed that our MX Client Details Page has changed slightly. This change was likely this week (or perhaps over the holidays). I suspect the web based dashboard interface changed, but I see nothing in change logs, "New Dashboard Features", etc. FYI, we have been on 14.40 since Dec 02 2019. One of our VLANs has click through splash auth. That info no longer appears on the Client Details page. Granted, our revoke never seemed to work in our MX environment, but the auth duration / expiration info was occasionally useful. There are other cosmetic changes that make me think this is a change in html coding, and not a "problem" with our system. Anyone else notice changes to Dashboard? Is there a Dashboard changelog that I am missing? How do I recover the presence of the splash auth data? Or did it move? Below is a stolen, edited graphic of how our Client Details used to appear; to its right is current appearance.

cfemfrl · ‎Dec 9 2019

I did see that, and perhaps read too much into "Blocked Splash page is static and is not customizable at this time" and assumed the article was outdated. The reason I did is that the block splash page on an MX is in fact customizable as I mention, and the article does not address "Meraki hosted" vs. custom (self) hosted. Still, I suspect the MX's Blocked page isn't customizable when the splash is custom hosted. At least, I can't figure it out but hoped someone here has.

cfemfrl · ‎Dec 9 2019

Hello, all, I have one VLAN that has click-through splash page for which I've created custom themes and modified the http and css to have customized splash and block pages. By "block page" I'm referring to devices blocked by individual device policy, not content blocking. This setup has been working fine for quite some time. Now I'm setting up another VLAN with the same basic setup, but the splash page is a "Custom-Hosted Splash Page". Initial testing seems successful with access control, walled garden, etc. and have proper click-thru splash and block behaviors. So, my question is: How do I customize the/a block page for this new VLAN?

Meraki

Community

About cfemfrl

cfemfrl

Community Record

Badges

Re: Connect Z3 like Client VPN

Re: Connect Z3 like Client VPN

Connect Z3 like Client VPN

Re: Change in MX Client Details Page? Dashboard update?

Re: Change in MX Client Details Page? Dashboard update?

Change in MX Client Details Page? Dashboard update?

Re: MX64 Customizing Block Page when using Custom Splash URL

MX64 Customizing Block Page when using Custom Splash URL

Re: Connect Z3 like Client VPN