Hello @Hoamboy and @mplewis299.   Thank you for the heads up. I'll defer this one to @MiriamK as I have transitioned into a new role.  ... View more

Greetings @CHaywood    @jesseb514  nailed it. If the DNS queries are encrypted, the security service is unable to see what the query is and take action based on the query. ... View more

Hey @speakerfritz  and @jesseb514    We apologize for this experience. It is clearly not the intended outcome we want. I'll review the cases in question and be sure we're doing all we can to solve this problem long term.   Contacting support is almost always the right play when facing umbrella license issues for the GX product. If we cannot see the key, we can also verify if the key you have is legitimate or not. ... View more

Thanks for the ping, @Xydocq! I get a notification when this happens, so if I'm not actively lurking the forums this is a good way to get my attention. I should put that in an announcement somewhere.   In any case - @DC3  and @rising_income we've been made aware of the problem and our developers are working on a fix. I understand it is misleading and not clear that the device is actually functioning well, but rest assured our experience thus far tells us this is only a cosmetic issue.   We'll get it patched up ASAP! ... View more

Hello @TobiasFrank ,   This is definitely not working as intended here, then. I'll get a ticket submitted for our developers to fix this issue.  The console log for ap.meraki.com is testing if we can reach the local status page of the device (we use this to provide a button that takes you to the LSP). The 500 error, though, is more interesting and may be related to the issue. The "network" tab may show the offending request that was made and help us dive a bit deeper.   There are still two methods that should be available to contact support: 1. Use the settings menu directly to open a case, and not the "Contact support" button in the troubleshooting flow. 2. Try using the mobile app both the way you've described to reproduce the issue, but also using the settings menu directly.   If you still face problems opening a case using these steps, let me know so we can take a peek and hopefully fix whatever issue it is you are bumping into. ... View more

Hello @TobiasFrank (thanks @Xydocq  as usual),   We just tested the case open feature and found it to be working on the web app. Does this problem persist in an incognito browser? ... View more

Glad to hear that, @speakerfritz! It really does make a big difference, and I'm glad we were able to make the media server connection a bit faster by getting the information to you.   I'll actually bring up the antenna orientation issue with our team. That does make planning your wireless environment more contingent on the dominant band used by client devices.   We'll have an image similar to what you've posted in our documentation before long.  ... View more

Good point @speakerfritz    X is going to be the longest side and Y the shortest side if looking at the access point from the top down. Z, then, is orthogonal to X and Y. I'll update the document to have a guide to show what I mean. ... View more

Hi @speakerfritz ! Sorry it took such a long time to get back to you on this. This has been a common request, so we've added signal coverage patterns to our datasheets. You can find the signal pattern here now: https://documentation.meraki.com/Go/Meraki_Go_Datasheets/Meraki_Go_Indoor_WiFi_Access_Point_-_GR12_Datasheet/Meraki_Go_Indoor_WiFi_6_Access_Point_-_GR12_Datasheet   ... View more

Hey @GroupeBleu thanks for the case number! I'll work with the support representative and we'll have some next steps or insight for you on the case today. ... View more

I have been summoned! (Thanks @Xydocq )   I'm sorry to hear you're having a rough time @GroupeBleu and i'm happy to provide some help. The message you are seeing can be caused by a variety of issues, but it ultimately means that your hardware is set for a different firmware version than what is currently installed. As a result, the hardware is likely trying to upgrade and failing for some reason.  Would you mind sending me a message with your case number? I'll take a look and see if we can't get you straightened out.   We have all of our switch ports (including those on the GX) set to trunk mode with native VLAN set to 1 and allowing all VLANs. The reason for this is that it should be a plug-and-play setup out of the box, and changing these settings may result in improper configuration. We're working on a series of guided flows to help people make best practice network designs by selecting configurable templates in the app. ... View more

Thanks, @speakerfritz! I'll go take a look.  Android doesn't have any additional hoops and should be letting users test things out right away.   I'll update the documentation once we have the code step sorted out. ... View more

@r3f3r1 for what it is worth, I just mentioned in a design meeting that it is important we add the ability to move the rules around due to the order being important. Which answers your other question that yes, we do a top down format like other firewalls.   It is important to note that pre-existing flows will be honored despite a firewall rule being installed. A way to demonstrate this is start a continuous ping to a computer in another VLAN, and then create a rule to block ICMP to that particular computer on the GX. The ping will continue to function successfully until the flow is destroyed. Rebooting the GX is a sure-proof way to clear the flow tables and test firewall rules are working as expected. Outside of that, some packet captures on the laptop showing particularly what traffic is making it through may shed some light on what to do next. ... View more

@Mendo54 I'd love to hear the end of this saga, everything looks good here.   Definitely set DNS to "Google DNS" and not to proxy to upstream. After that change to the DHCP settings, be sure to do an ipconfig /release and ipconfig /renew to get the new DNS settings. I'd be personally interested in not only seeing the ping results being successful, but also a dig/nslookup command showing proper name resolution. For example: nslookup cnn.com   This should return the IP address for cnn.com if DNS is working.   If ping and DNS is working, but you still can't get to the internet - huh. I wonder if IPv6 is causing an unexpected hard time, you could always try disabling IPv6 outright on your client device to rule out IPv6 (or I guess rule it "in"). ... View more

Thanks for the help @Roel_NL and @Xydocq !   @Bloom  The firmware mis-match is informational and indicates that the firmware set for the site is different from that which is actually running on the hardware. Support is the best path to learn more about why this is happening and how to fix it.   We're working on better firmware upgrade control that would allow you to solve this on your own. ... View more

Hello @TRHH,   We haven't formally tested any AOC cables on the GS110 series switches. The SFP Fiber Transceivers tested with the GS110 series can be found here: https://documentation.meraki.com/Go/Meraki_Go_Accessories/Meraki_Go_Switch_SFP_Overview   These are the Meraki branded SFPs. However, that is not to say other SFP transceivers or mediums would not function (we just don't support them). Your mileage may vary, but so long as the transceiver follows protocol I don't see why it wouldn't work, but I cannot guarantee it'll go as planned. ... View more

Wow! I really am a big fan of those rack mount kits (I have the same set). I've also got an APC in my closet driving the whole thing.   Do you make your own cables? The RJ45 plastic housings look unique, but maybe it's just the photo. ... View more

Hey @NuP and @Hoamboy!   The sonos speakers work at layer 2 for discovery. The guide you have linked is a tool to help users setup their wifi networks in a bridge mode, meaning they pass wifi traffic at layer 2 onto the switch, making the sonos devices discoverable. A guest mode or NAT mode wifi network would strictly prevent this.   That all being said, because the sonos speakers work at layer 2 - they are discovered by any devices on the same network. Let us assume the sonos speakers are on VLAN 100 - any device on VLAN 100 should be able to discover them. If you have a wifi network configured for VLAN 100, any wifi device connected to that wifi network would discover the sonos speakers. If you connect to a different VLAN on a different wifi connection, the devices would not be able to discover the speakers.   Unless Sonos has a way of multi-homing the network access and let certain speakers participate on certain networks, I don't think you can achieve precisely what you want.   You could connect a set of sonos speakers to the "customer" network, and make sure the wifi for customers only reaches these sonos speakers (and not others on another network). However, you couldn't get your 3rd bullet point of having staff see all speakers on one network connection without giving everyone the same level of access. ... View more

Hey @RAV1,   I was working on my lab rack last night when I noticed something similar on one of my GX20s. There is a small chance this is firmware related. I'll do some testing and see if I can get the brightness up on my LED in the lab and report back here. I don't believe we'll be able to do much, but if we can we'll issue a fix. ... View more

Hello @Hoamboy and @Xydocq ,   Thanks for the heads up! Feel free to @mention me for any bugs encountered to get my attention.    There is a possible workaround using the web app (https://web.meraki-go.com/). Try using an incognito window and see if the language flips back to English. If it does, deleting cached site data for the web.meraki-go.com site should fix the problem.   There is still a known issue with language selection that should be soon resolved, despite the above workaround. ... View more