About alemabrahao

alemabrahao · ‎10-13-2022

Send a documentation explaining that or convert It to per-device licensing. https://documentation.meraki.com/General_Administration/Licensing/Meraki_Co-Termination_Licensing_Overview

alemabrahao · ‎10-13-2022

Well, I suggest you try putting the machine on the allowed group policy and test again, It's not a route problem and probably a rule on your group policies are blocking the connection.

alemabrahao · ‎10-12-2022

Well, like meraki team support said, they have a issue with their Radius server. Is it possible to use a external Radius server (like NPS, freeradius, etc)? Have you tried to performe a packet capture to see more details?

alemabrahao · ‎10-12-2022

Access points intended to form a wireless link or mesh together must be within direct line of sight of each other. Wireless bridges running version 27.X or below only support a single VLAN. If support for multiple subnets is a requirement for the deployment, a layer 3-capable device will be required. MR repeaters will only send/receive untagged traffic on its wired interface regardless of the configuration of the SSID in use. Starting 28.1, Multi-vlan support was added. By extension, wired clients across the mesh link do not support the use of VLANs applied by Group Policies. https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Extending_the_LAN_with_a_Wireless_Mesh_Link

alemabrahao · ‎10-12-2022

Look, I'm pretty sure that's not possible. Is it not possible to connect these switches to your infrastructure via an Ethernet cable?

alemabrahao · ‎10-12-2022

🤔, I just checked another organization and It's ok too. SM 390 on version 14.33. Strange.

alemabrahao · ‎10-12-2022

Yep, It's ok for me. I have a 355 on version MS 14.32.

alemabrahao · ‎10-12-2022

@cellarcaskza Can you show what are you trying to explain?

alemabrahao · ‎10-12-2022

@Vincent61 I didn't understand your question. Do you want to connect Meraki Switches via Wireless?

alemabrahao · ‎10-12-2022

Could you please explain better? The VLAN 120 (10.0.20.0/24) VPN and VLAN 121 (10.0.21.0/24) VPN networks are Client VPN, Meraki VPN or Non-Mreaki VPN.

alemabrahao · ‎10-12-2022

interesting

alemabrahao · ‎10-12-2022

One more information. The IPv6 neighbor discovery process uses Internet Control Message Protocol (ICMP) messages and solicited-node multicast addresses to determine the link-layer address of a neighbor on the same network (local link), verify the reachability of a neighbor, and track neighboring devices. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipv6_basic/configuration/xe-3se/3850/ip6-neighb-disc-xe.html#GUID-A09BEBD3-2E2B-464A-89C2-025BD6D7660D

alemabrahao · ‎10-12-2022

It's under Monitor Appliance Status

alemabrahao · ‎10-12-2022

I don't think that is the case.

alemabrahao · ‎10-12-2022

There is not a specific log to know It was restarted, but you can configure an alert to it when goes offline or you can check the connectivity history on Appliance status page. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alerts_and_Notifications

alemabrahao · ‎10-12-2022

I think it's only possible to GET information about a specific profile: https://developer.cisco.com/meraki/api-v1/#!get-network-sm-profiles

alemabrahao · ‎10-12-2022

Take a look on this recommendations: https://hcsonline.com/images/PDFs/Wi-FI_Apple_Devices.pdf For Apple devices I really recommend a 5GHz only coverage design. https://www.cisco.com/c/dam/en/us/td/docs/wireless/controller/technotes/8-6/Enterprise_Best_Practices_for_iOS_devices_and_Mac_computers_on_Cisco_Wireless_LAN.pdf

alemabrahao · ‎10-12-2022

Why do you want to remove It? Anyway It's not possible.

alemabrahao · ‎10-12-2022

It's not a MX logs on dashboard, It's a reporting for a Syslog servers.

alemabrahao · ‎10-12-2022

Log into Dashboard. Navigate to Configure>Access control or Wireless>Configure>Access control if in Combined view. Select your SSID from the SSID drop down. Under the section Network access, locate the Splash Page section. Select the Click-through radio button. Once selected, captive portal selections will appear. Select your captive portal strength from the Captive portal strength drop down. Allow non-HTTP traffic prior to sign-on: All traffic types except for TCP port 80 are allowed before the splash page is acknowledged. Block all access until sign-on is complete All traffic types are blocked until the splash page is acknowledged. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Block_Listing_and_Allow_Listing_Clients#Block

alemabrahao · ‎10-12-2022

Are you blocking all access until sign-on on SSID configuration like this? Can you show me your SSID configuration?

alemabrahao · ‎10-12-2022

Is it a non-Meraki VPN point or Meraki VPN? If it is a non-Meraki VPN point, does the point on the other end need to allow its local networks? There is an example of the configuration between a Cisco ASA and an MX Meraki ( It's Just a example OK?). https://documentation.meraki.com/MX/Site-to-site_VPN/MX_to_Cisco_ASA_Site-to-site_VPN_Setup

alemabrahao · ‎10-12-2022

unfortunately It's not possible, but, you can block the client If you want. Just to understand, Are you using a external page? Are you blocking all access until sign-on on SSID configuration?

alemabrahao · ‎10-12-2022

I suggest you to perform a packet capture and open a case with Meraki support.

alemabrahao · ‎10-11-2022

Well, I think the first thing you can try is to give something different than in this article, just to review what best practices: https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Channel_Planning_Best_Practices https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Multi-SSID_Deployment_Considerations You can also try creating a new SSID on 5Ghz only, to validate if the behavior is the same. Review your Rf profile configuration, and SSID configuration. On Windows machine you can try modify agressive roaming configuration.

alemabrahao

Alessandro Abrahao

Community Record

Badges