Instead of levering a "legacy" on-site proxy, you could take a look at current SASE (Secure Access Service Edge) offerings like Umbrella.   The integration with Umbrella provides you with DNS security and cloud-based firewalling- / proxy-capabilities without having to backhaul traffic from other locations or even VPN clients. Therefore, it doesn't matter where your endpoints are located, be it sitting ion your HQ or at a nice beach somewhere in the world. ... View more

Welcome to the forums Cyriel! ... View more

Hi aus NRW! 🙂   Schön, dass du dabei bist! ... View more

Have you tried activating DHCP relay on the Vlans your endpoints are behind? You should be able to point them to your DHCP server then. ... View more

Yes, it could do that but will deliver any security features like a small MX would do. ... View more

These attributes are being sent by default, there's nothing to configure. Please see https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Configuring_RADIUS_Authentication_with_a_Sign-on_Splash_Page   "Supported RADIUS Attributes When a sign-on Splash Page is configured with RADIUS server, authentication is performed using PAP. The following attributes are present in the Access-Request messages sent from Dashboard to the RADIUS server.   Note: Please refer to RFC 2865 for details on these attributes, additional notes for certain attributes are included below. User-Name  User-Password Called-Station-ID: Contains (1) the MAC address of the Meraki access point (all caps, octets separated by hyphens) and (2) the SSID on which the wireless device is connecting. These 2 fields are separated by a colon.  Example: "AA-BB-CC-DD-EE-FF:SSID_NAME". Calling-Station-ID: Contains the MAC address of the wireless device (all caps, octets separated by hyphens).  Example: "AA-BB-CC-DD-EE-FF". Acct-Session-ID Framed-IP-Address NAS-Identifier NAS-IP-Address NAS-Port-Id NAS-Port-Type Service-Type" ... View more

How does your setup look like? ... View more

@BlakeRichardson: it's possibly cheaper than having a phenomal breach. 😉   @DarrenOC: Whoa, I guess you put a lot of work into that one! ... View more

I believe the only way to get rid of those would be blocking access to your network unless specific apps are installed on their device(s). ... View more

What kind of speciality should Meraki switches have in this regard that should let you run into any issues? ... View more

From a technical perspective, the data sheet / sizing guide is all you need.   When it comes down to RfPs that include maximum sessions, I don't know any way to calculate (or get) these numbers for Meraki MX. ... View more

Upgrade went smooth this weekend on MR45 and MR46 ... View more

Your MX simply shouldn't respond to DHCP requests in that subnet. Your existing DHCP server will handle it automatically. ... View more

Correct. DHCP will send a broadcast, therefore there's no need to relay within the same broadcast domain. ... View more

Well, the Meraki advantage here is clearly that when you've got somebody on the phone, he / she will be able to assist you way better than the Tier 1 guy on the "legacy" Cisco hotline.   And please don't get me wrong: if it's that urgent, it shouldn't be an issue to wait a few minutes on the phone... 😉 ... View more

Same here. I've never waited for more than ~5-10 minutes. ... View more

Hi Cleas,   wow, that sounds like a lot of stuff you‘re doing! Welcome to the community 🙂 ... View more

First and foremost: are messages received on the agent? ... View more

We‘re also eagerly waiting for that feature. It‘s something that other vendors handle since „ages“ and is a showstopper at least in many RFPs regarding SD-WAN. 😞 ... View more

Fantastic achievement gentlemen! Special congrats to @Tadpole86 and @vassallon!   @BrechtSchamp: Strictly speaking, your API scavenger hunt is even greater than many solutions! 👍 ... View more

Leveraging the commercial variant of OpenDNS you could configure the Roaming Client / Anyconnect Module to handle this situation: https://docs.umbrella.com/deployment-msp/docs/appendix-d-internal-domains-steps ... View more

It’s kinda clearly explained on https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Using_Layer_3_Firewall_Rules ... View more

I don't completely understand 1) and 2) because a) why shoudön't it work and b) what does licensing have to do with where you are using the products?   As for 3) and 4):   3) Yes, please see https://documentation.meraki.com/zGeneral_Administration/Other_Topics/Returns_(RMAs)%2C_Warranties_and_End-of-Life_Information https://meraki.cisco.com/support/#policies:return https://community.meraki.com/t5/Off-the-Stack/Hardware-warranty/td-p/41773   4) You can set the regulatory domain for APs using the Dashboard: https://documentation.meraki.com/MR/Radio_Settings/MR_Wireless_Regulatory_Domains ... View more