Hi @I_Naitoh  同様の質問で次のスレッドを確認してください。   https://community.meraki.com/t5/Wireless-LAN/WPA3-announced-Does-Meraki-have-any-plans-to-include/td-p/8945 ... View more

Hi @ShadowoftheDark  I understand we are discussing about "Non-Meraki VPN" Confguration. Constructing tunnels with Meraki Auto VPN (between Meraki Devices) or Non-Meraki VPN (between Meraki and Non Meraki) are kind of easy. I believe the logs displayed on the Dashboard shall be relevant to your VPN only. I could see "failed to get sainfo" event   Did you happen refer to following url (Lists down most of error events) https://documentation.meraki.com/MX/Site-to-site_VPN/Troubleshooting_Non-Meraki_Site-to-site_VPN_Peers   Event Log: "failed to pre-process ph2 packet/failed to get sainfo" Error Description: The tunnel can’t be established and the following error is recorded in the event logs in the Dashboard “msg: failed to pre-process ph2 packet (side: 1, status: 1), msg: failed to get sainfo.” Error Solution: This can result from mismatched subnets in the IPsec tunnel definitions, typically a mismatched subnet mask. Check to be sure that the local and remote subnets match up on each side of the VPN tunnel. ... View more

Hi @martijnwireless   The only information I could search is the following. https://meraki.cisco.com/lib/pdf/eol/meraki_eol_mr34.pdf   Seems MR42 is a replacement of MR34. So I believe "End of Sale Date" ie. October 31st, 2016 seems to be "Release date" for MR 42.   I may not be correct though.   ... View more

Hi @Mule  Could you please verify the "MAC Address" of the "Whitelisted" machine? Is it correctly Identified on the Dashboard?   ... View more

Hi @Wong    I believe this may not be possible. One idea could be. You may install  a "Router" between the ISP and MX84s and share the ISP with both MXes. ... View more

Hi @dmiss    The Meraki documentation suggest the following reason for this event. 802.11 disassociation: client has left AP - A client informed the AP that it should no longer keep the client in its association table. You may see this if the client has potentially gone into a hibernate state, a powered down state, or the client may have chosen to roam to another AP.   Do you think this could be a reason?   Few suggestions. Try "Disabling band steering" if already not. If you see lots of SSIDs in your Air Marshal scans. Try setting the Channel width to 20 if already not.   ... View more

Same here @PhilipDAth . I am in the middle of LDAP integration.         ... View more

Hi @Hubble  What all Meraki Gear do you have in your network? MX, MR , MS?   Please share the Model No. too?   ... View more

Hi @Hubble, The steps suggested by @Nash shall certainly resolve the issue.   You may also  check the following 1. Organization > Change Log [To Verify any Block Events] 2. Wireless > Access Control - Assign group policies by device type [To verify Block policy by device type]   ... View more

Hi @AkilahIS  Two things. One check the Organization - Change Log. To verify if the settings are modified.   Two by any chance the devices are assigned with another VLAN and your Global Policy is applied. ... View more

Hi @CKYI    I am not sure if the following documents helps you with the information your are looking for.   https://documentation.meraki.com/MX/Cellular/3G_-_4G_Cellular_Failover   https://documentation.meraki.com/MX/MX_Overviews_and_Specifications/MX67_and_MX68_Overview_and_Specifications     ... View more

Hi @zrunner626    I have not seen any of our clients wireless network with this behavior. As @PhilipDAth suggested "Block all access until sign-on is complete" should do the job.   A piece of information from the below url says Once a device is authorized this method will not ask for authentication again for the permitted duration.   May be your devices are already authorized. Could you verify this please?   https://documentation.meraki.com/MR/Encryption_and_Authentication/Sponsored_Guest   If a user disconnects and reconnects within the approved time, the device will automatically get internet access. If the user reconnects to the SSID after the approval period is expired the whole process will be repeated again. This function is currently limited to a maximum of 1 day (24 hours) per authorization.   Note: Devices that have been authenticated for a specified duration cannot have their authentication manually revoked, and admins will have to wait for the authorized duration to end for access to expire. Devices are authorized by user accounts, and authorization applies to any device using the approved credentials.  ... View more

Hi @Mostofa    You have various methods of on-boarding Guests on Meraki Wireless Networks Click-through Sponsored guest login (Preferred Option 1) Sign-on with Meraki Authentication (Preferred Option 2) Billing [Vouchers based access] You may choose any of the above options considering your organization policies.   If you want to use vouchers/ coupons please check the following Url [You have all the steps to configure SSID and create vouchers]   https://documentation.meraki.com/MR/Splash_Page/Configuring_a_Prepaid_Card_Billing_SSID   ... View more

Hi @Screasey    Greetings. I am getting ready to deploy a site to Chennai India. This is Ajit from India :). Let me know if you need any assistance.   Is the MX device using DIA circuits reliable enough for this operation? DIAs are certainly reliable. There is an agreed SLA with the operator.   Can I use an MPLS circuit in the MX device? Certainly you can use MPLS. You need internet service in the mpls circuit for MX to reach cloud and establish AutoVPN with other sites.   I have a pair of MX 400's at the head end For HA.. You will need 3 IPs on each link .ie /29.   Is it also possible to terminate an MPLS into the MX400? this would give me direct site to site. Hmmm. You may terminate MPLS on a LAN Interface by creating L3 VLAN. However internet is required for MX Management.   ... View more

Hi @IsraelFilho    Yes I saw a similar message from @Uberseehandel on Monday. Below the is thread   https://community.meraki.com/t5/Dashboard-Administration/One-or-more-of-your-Meraki-devices-are-unable-to-communicate/m-p/53903#M1882 ... View more