Meraki

alemabrahao · ‎Nov 10 2022

Can you give us more information? What kind of authentication? Does this happen with only one SSID or all? what tests have you done?

alemabrahao · ‎Nov 10 2022

Go on Meraki dashboard, go to help and cases.

alemabrahao · ‎Nov 9 2022

MS225's just have limited Layer 3 capabilities like inter-VLAN connectivity - they don't have full Layer 3 routing abilities.

alemabrahao · ‎Nov 9 2022

Nope, It supports L3 routing, and limited Layer 3 capabilities like inter-VLAN connectivity - they don't have full Layer 3 routing abilities.

alemabrahao · ‎Nov 9 2022

Open a support case.

alemabrahao · ‎Nov 9 2022

Change encryption for AES, and follow these recommendations: Security & SD-WAN -> Configure: Site-to-site VPN -> Non Meraki VPN settings: Preshared secret must be greater than 14 characters Authentication cannot be MD5 Diffie-Hellman Group must be 14 Phase 2 encryption cannot be NULL PFS can be configured to be either off or 14

alemabrahao · ‎Nov 9 2022

There is an option to update users: Update Network Meraki Auth User Operation Id:updateNetworkMerakiAuthUser Description:Update a user configured with Meraki Authentication (currently, 802.1X RADIUS, splash guest, and client VPN users can be updated) PUT /networks/{networkId}/merakiAuthUsers/{merakiAuthUserId}

alemabrahao · ‎Nov 9 2022

If you configure some port on your MX or switch in the same VLAN, and connect a notebook with the internet cable, Do you have this issue?

alemabrahao · ‎Nov 9 2022

Who Is your DHCP server and Default gateway. Have you performed a packet capture?

alemabrahao · ‎Nov 9 2022

I think that it can help you: https://developer.cisco.com/meraki/api-latest/#!create-network-meraki-auth-user

alemabrahao · ‎Nov 9 2022

Is it a MX? If yes downgrade to version 16.16.6, the version 17.x is not stable yet.

alemabrahao · ‎Nov 9 2022

Hi @fcbob, It should have to work behind NAT. Try define the remote ID on Meraki side with the Sonicwall IP: The Remote ID of the remote peer. This is an optional configuration and can be configured to the remote peer’s UserFQDN (e.g. user@domain.com), FQDN (e.g. www.example.com) or IPv4 address as needed. Which of these values you use is dependent upon your remote device. Please consult its documentation to learn what values it is capable of specifying as its remote ID, and how to configure them (e.g. crypto isakmp identity for ASA firewalls https://documentation.meraki.com/MX/Site-to-site_VPN/MX_to_Sonicwall_Site-to-Site_VPN_Setup

alemabrahao · ‎Nov 9 2022

In terms of routing the answer is yes.

alemabrahao · ‎Nov 9 2022

No, if it's a new organization you have to perform the configuration again, but you can use API get the configuration then put it on a new organization. You can move the licenses as @MyHomeNWLab informed.

alemabrahao · ‎Nov 8 2022

This is very subjective, if we are going to talk in terms of RF, the ideal would be to disable it so as not to be "polluting" the air. But that doesn't mean it will necessarily cause any problems. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/3se/security/configuration_guide/b_sec_3se_3850_cg/b_sec_3se_3850_cg_chapter_010110.pdf https://meraki.cisco.com/blog/2017/09/rogue-access-point/

alemabrahao · ‎Nov 8 2022

Yes, but you have to use a different ssid name. You also can classified It as a friendly Access point.

alemabrahao · ‎Nov 8 2022

The standalone combined network name is limited to 38 characters for the combined network due to the network type suffix (MX, MS, MR) getting appended to the name without visibility. The validation limitation is 50 characters. I remember that in the past I had problems with devices Meraki to update the config on the dashboard because they had a very large name configured. So just be careful not to cause any kind of problem for you.

alemabrahao · ‎Nov 8 2022

No MX does not support Anyconnect for Lan clients.

alemabrahao · ‎Nov 8 2022

There is no information about It.

alemabrahao · ‎Nov 7 2022

Also, check It: https://community.duo.com/t/meraki-vpn-azure/11093

alemabrahao · ‎Nov 7 2022

Maybe It can help: https://duo.com/docs/azure-ca

alemabrahao · ‎Nov 7 2022

Check this article: Duo Two-Factor Authentication for Meraki Client VPN https://duo.com/docs/meraki-radius

alemabrahao · ‎Nov 7 2022

Meraki switches do not support QinQ tagging.

alemabrahao · ‎Nov 7 2022

We use hostname convention in our enterprise: AAABBCC-NN where AAA is the first 3 letters of the city or location BB is the state CC is the first 2 digits of the platform/model NN is the order of the device for example FLNSCMS-01 FLN - Florianopolis SC - Santa Catarina MS - Maraki switch 01 is the first device on that location or LAN The Tags you can use to identify the location too.

alemabrahao · ‎Nov 7 2022

So sad Brazil is not an eligible country. 😢

About alemabrahao

alemabrahao

Alessandro Abrahao

Community Record

Badges