No worries. Have a great one! ... View more

Are both links from the same supplier? ... View more

You can try it with OpenDNS. https://domain.opendns.com/wechat.com ... View more

I actually tried with four computers, two corporate and two personal, Its funny how the issue was causing.   -two Personal laptops no issue at all, works with corp-SSID[only preshared-key] -Corporate laptop, gives issue connecting to CORP-SSID[Radius Authentication] and CORP-SSID[PSK] -removed all 6 AP from the network and put it back after 5 minutes, corporate laptop started to work, after 30 minutes, when AP started moving user from one AP to other, issue again. -deleted the IP lease from the DHCP server, cleared Ip from windows[ipconfig /release], i see User machine is getting dummy IP[169.254.XX.XX]  -got the meraki support in the call, he started doing a packet capture on the uplink of the meraki Switch connecting wan router, in less than a minute, whole site Internet Access and Phone went off the air. Including connectivity of all Meraki Devices from that main site to the dashboard -DNS server which was directly connected to the same Meraki Switch was dropping external DNS return packets, and Internet wasn't working for all the users in the network, as that is the primary DNS server, another strange thing internal DNS was working  -i proved customer that from PaloAlto which is in DC and MPLS internet link is not dropping DNS packets, DNS server in the DC itself was able to resolve external FQDN from it. -after one hour of troubleshooting, narrowed problem is no where else but the meraki distribution switch, customer agreed to reboot distribution meraki Switch from which Meraki Support engineer did a packet capture. service was restored as soon the switch was power cycled. -Now old issue re-surfaces, IP phones locked out, when rebooted it stops at 40% as it is waiting for DHCP servers to assign IP address - last year around October, Meraki engineering team found this as a bug, and applied a temporary fix, seems they had informed customer that rebooting may remove that fix from the switch. -customer increases the DHCP scope from 100-200 to 100-250, couple of phones immediately restored as it gets the new IP, but the DHCP statistics in the DHCP server shows instantly, 0% IP address available[somewhere this IP is being assigned or Switch sucking up all the IP address from that Phone Vlan and dropping it] -ringed Meraki support, this engineer checks the switch and confirms code is still in the rebooted switch but good idea to upgrade the firmware and check if that fixes the problem.    =================== This was a kind of whole story yesterday...  ... View more

Here is a specific configuration guide covering what you are doing.   https://documentation.meraki.com/MR/Splash_Page/Configuring_RADIUS_Authentication_with_a_Sign-on_Splash_Page ... View more

I'd like to hear what the root cause was, did you get an incident summary at all? ... View more

No. ... View more

Exactly. My point view should be have any function to enable on portal for example if I can enable level session of logs ( like Cisco ) in order to see more logs in some events. Like level 7 - debugging, level 3 - information, so similar in this way. I believe will do " Make wish " 🙂 ... View more

In fact in my country we have a "Section 252" of the crimes act that makes it illegal to access any computer system without authorisation - which would cover all former employees.  Up to a 2 year jail term for that.  And if you actually cause damage the term can start going up with other charges.   http://www.legislation.govt.nz/act/public/2003/0039/latest/whole.html#DLM200273   ... View more

@PhilipDAth wrote: By default AutoVPN traffic permits all traffic.  The firewall for this are located: Security Appliance/Site to Site VPN/[scroll down to Organization-wide settings]   There's a wrinkle to the way this is being deployed that might have an impact on this recommendation.  The MX65 is in the path of a DMVPN solution but is only providing encryption.  In other words, the GRE tunnels are based on Cisco routers and terminate on ASR head end routers in each of our data centers.  Traffic to/from the Meraki mgmt network trombone on the 2921 at the branch.  For instance, traffic inbound to the branch (from the DC) would follow this path to get the Meraki MGMT network:   DC -> HE (GRE) -> MX600 -> Internet (IPsec) -> MX65 -> (GRE) -> 2921 -> MX65 (native IP) -> MGMT_Net.  The only network in the tunnel is a /30 between the MX65 and the router and effects only the GRE traffic.   ... View more

I like this upgrade, thanks.  ... View more

True @Uberseehandel, I guess I only really refer to uplinks as any port that has the up arrow on it in the dashboard.  Everything else I just refer to as an access or trunk port.   ... View more

PM'd @MRCUR we can start an offtopic thread if desired.   ... View more

@pjc  @Adam   Thanks for your help! ... View more

i figured it out. My poe adaptor is passive and use pin 4,5,7,8. The meraki ap use pin 1,2,3 and 6. Operating Input Voltage Range, V 36 57   This is for active PoE so it will not accept 24V anyway ... View more

Agreed with the above assessment.  If you don't have vlan tagging enabled then it'll just use the default vlan or whatever you have setup for the vlan on the AP interface.   ... View more

I agree, if security is such a concern use 802.1x.   Otherwise, set the default policy to block everything.  Then create a group policy called something like "Authorised", and apply it to every client that is allowed to be on your network.   Anything new that appears will be blocked.     Another option would be to deploy Systems Manager on your machines.  You could then have it auto assign the policy "Authorised". Only machines with the Systems Manager installed would be able to connect. ... View more

I also believe if you contact support they can check the temperature and verify if your interpretation of "very hot" is indeed out of the norm. But most likely as @PhilipDAth indicated, they'll process an RMA.  ... View more

Thank you! ... View more

Until you have an order number for the trial, you can't add demo devices to Dashboard. You can use the demo networks that Meraki provides - see the link in @PhilipDAth post.  ... View more

If you are creating a guest network, and by that you mean a network that does not allow access to the local network isolates guest users from each other then it does not have to extend across all sites. If fact that just adds extra complications. The guest network at each site/location can require the same user credentials across all the sites.   Isolated guest network creation -  Go to Wireless > SSIDs  If the SSID you wish to use for guests does not exist, set it up, or edit the settings for that SSID. Then on the Access Control page set up the environment Under the section headed - Addressing and traffic you will see  Client IP assignment  - this gives you the option to select   - NAT mode: Use Meraki DHCP Clients receive IP addresses in an isolated 10.0.0.0/8 network. Clients cannot communicate with each other, but they may communicate with devices on the wired LAN if the SSID firewall settings permit.   Then ensure that guest users never access the local network. Usually I apply a group policy that stops guests running peer-to-peer applications (file sharing) and adjust the minimum network speed so that 802.11b is not supported as that severely restricts throughput. ... View more