Hi @questionyibit ,   We apologize for the reset loop - there was a known issue with the password reset email not generating the proper redirect and this is now resolved as of yesterday evening. You should be able to reset your password now, but if not shoot us an email at help@meraki-go.com and we'll do our best to get you sorted out promptly. ... View more

Hello @Mikymike  and @speakerfritz,   I'd like to note that the GX50 does not support dual WAN setups and this is considered a bug. We're not sure what behavior will occur in your circumstance, and future firmware updates will remove this functionality, so please do not plan on this as a long-term feature in your deployments.   We may change our stance on this in the future with different product lines. ... View more

Hello @InSysPro    I took a look at the case and am only seeing a model GS110-8 switch (no "P"). This switch does not provide PoE. ... View more

Thank you for following up, @Xydocq! I gave what knowledge I have to the support team. We appreciate your help, as well as shedding light on an issue that may impact more customers down the road. ... View more

Good morning @bqueva and @iliadz    The app version 2.81.0 is available on the iTunes and Android stores. Per testing on my android phone this morning the landing pages tool is working as expected. Give it a go and let us know if you are still facing problems. ... View more

Hey @Xydocq - I was perusing the community and found your story. Why did it not work the day before, indeed? I'm right there with you.   We have a very rare, and extremely hard to reproduce port configuration issue on the GX. We've yet to nab it and fix it. What I've seen happen only twice in several years is the ports can be set to drop untagged traffic on the GX LAN. I'm guessing you hit the lottery and encountered this problem, as evidenced by a port config change from Trunk to Access seemingly fixing the issue. I'm wondering if, indeed, that did do the trick.   I never have any luck causing this problem in my lab. I'd hate to put you through that pain again, but if you are able to reproduce that deployment failure we'd love to hear more about it via a support case opened from the app settings menu.   In regards to your question about firewall rules in one direction between two VLANS: currently this is a feature request. However, I'm happy to say it is on our roadmap to be able to set custom L3 firewall rules. You can't do it today, but hopefully you can sooner rather than later. Right now we have the "Secure" toggle on the VLAN which automatically writes L3 firewall rules on the firewall to block any traffic to/from that VLAN on the LAN. ... View more

Hello @iliadz,   We regularly release app updates on a 2 week cycle. The 2.81 version should be released relatively soon barring no unforeseen obstacles. Thank you for your patience as we work towards a fix! ... View more

Good mornin @Image_Acquire!  You can consolidate to a single GX and create a new VLAN that used to exist on the TP-Link router, that should be fine. Devices on VLAN A could get to devices on VLAN B. For example:   Your' current GX50 could hold VLAN X (where X is just your VLAN ID) with network 192.168.11.0/24, GX IP at 192.168.11.1. It could have a second VLAN Y that is 10.1.10.0/24 with the GX IP at 10.1.10.1. In this setup, so long as the secure network toggle is set to false, the devices should be allowed to communicate to each other on the LAN.   If you want the two GX setup, the GX50 that is downstream of the GX50 connected to the internet will act as a firewall (which is good news) and block unsolicited inbound connections to the 10.1.10.x network. Devices on the downstream GX50 could initiate connections upwards just fine (i.e. 10.1.10.50 pings 192.168.11.20 would work), but connections coming into the 10.1.10.x network are blocked unless a port forwarding rule exists.   Finally, if you setup client VPN on the downstream GX50 - the connecting client devices should, in theory, be able to reach both the 10.1.10.x and 192.168.11.x networks. If you configure client VPN on the upstream GX50, it would be able to access the 192.168.11.x network, but be blocked by the downstream GX50 that holds the 10.1.10.x network (unless a port forward rule existed for it).   Was the TP-Link router just routing? If that was the case, it probably would have let traffic through without a second thought, which would be the primary difference between the TP-Link and the GX. ... View more

Hello @Image_Acquire    I like the project! Your approach is correct, in my opinion. We simply did not intend for someone to use two GX devices within the same physical network, but if your desire is to physically segment a network (and not just rely on L3 firewall rules) you have the right idea.    To configure a second GX, you need to leverage multi-site, or in essence set up a new "site" for your second GX. You can then provision and configure the second GX as you see fit. Here are the instructions on how to do so: https://documentation.meraki.com/Go/Features/Managing_Multiple_Sites_with_Meraki_Go#Create_New_Site ... View more

I'm sorry for the experience you've had @LuckyLionTamer  The ability to load balance incoming connections is not enabled on Meraki Go hardware. This means the decision to roam is a client initiated process, which is often dependent of the radio vendor used on the device (be it a smartphone, laptop, or otherwise). We don't push off client associations to other access points in the area.   I wonder if the apple devices are expecting the fast roaming feature 802.11r? ... View more

Hello @LuckyLionTamer    Opening a support case is definitely the correct approach to get to the bottom of the problem. It would be interesting to execute a monitor mode capture while the clients are failing to connect, then again after performing the airplane mode sequence to get the clients back online. Comparing these two monitor mode captures would help elicit what exactly the client and access points are changing and finally allowing a connection.   I understand this may sound like a lot of effort to reach an answer, but it would certainly provide a strong foundation to draw conclusions from. ... View more

Interface counters as well as event logs are on the horizon. CLI is not something we plan on working towards. Anything you might find in the CLI we'd rather include as perhaps an item on the local status page, so do let us know what you might find there and what you would want to see locally. ... View more

Hello @IanTerry    We typically keep interface and frame counters available on our switches but have not extended that to the Go product line. I see value in that, but it would have to be accessed locally if the hardware is not checking into the cloud. The same goes for the DHCP information in detail, we can definitely make that information readily available too. I've put these items down on the wish list.   Where were you hoping to find these items? ... View more

Thanks for the feedback @IanTerry - we expect the tool to work identically between the app and the webpage. What differences do you see?   When things don't work on a cloud managed product, it almost always means you'll have to be on-site to do any troubleshooting. The only remote diagnostic that can truly be made is denoting the hardware as online and configurable, or offline and requiring some troubleshooting.   A new tool was introduced about a year or so that creates a quick-link to the local status page of the hardware if you are directly connected to it. We should do more to draw attention to this link, as the local status page typically has relevant real-time information about problems with the device.   What is a problem you faced that would have been solved with a missing tool? We can work on getting it in the app for you! ... View more

I hope I count as Cisco @IanTerry  😄   We recently rolled out a fix for the web connection test tool. I'm not entirely certain that is the feature being discussed here, but it should be working without a hitch. If that isn't the case, let me know here and we'll take a closer look. It's working on my lab account as I write this. ... View more

99 times out of 100 the pcap holds the truth. If you have a capture from when the issue was occurring, we could probably get to the bottom of the problem. I think support was the right way to go.   There have been some reports that cases weren't opening properly today - did you happen to get a case properly generated when you contacted support? I'm just curious, making sure there isn't an issue out there. We definitely want to be sure support is getting back to you. ... View more

EDIT: I re-read the description of the issue and see that there is intermittent islands of stability. Take the following post as just some insight from someone hearing your plight, I'm not sure if I'm hitting the mark or not.   I noticed a shift a few years back (a decade now maybe?) where wifi connections were demarcated as failed to connect or no internet connection on the mere premise that DNS is failing. In testament to this, if I block DNS on my home network that my Meraki Go wifi clients use - they start to complain that the wifi is not working. The reality is, this health check on the mobile is entirely based on "is DNS working?". My android devices will connect in these circumstances, but say "Connected, no internet".   I bring all of this up @IanTerry because this shift in the industry has made it harder for us, remotely, to tell if you are having wifi issues (like interference) or an issue on the wire upstream of the access point. Both of these can cause DNS to fail, and have the wifi marked as no good.   If the changes recommended thus far haven't given much insight - it might be time to check the local status page of the GR10 and get more information. Ideally, we'd want to know:   - Which band you are on during the slowness - What is channel utilization during the slowness - What are your speeds directly to the access point - What are your speeds to the internet   The local status page offers info on your connection, like which band, channel utilization, and also provides a speed test to let you see what your local speeds are. We'd want to pair that with the internet speed test taken immediately after the local status page speed test, as well as identify if there is a channel utilization problem or interfering access points in the area.   Also shout out to @speakerfritz and @TyShawn for jumping in. It takes a village! ... View more

Hello @IanTerry and @ZachREC    We don't mind what characters are used in a PSK. The recommendation to not use special characters stems purely from a risk of typos increasing with special characters as compared to longer but easier to remember keys using familiar characters.   If you can reliably demonstrate that special characters in a PSK are causing connectivity issues, please open a support case with the supporting evidence that is the case (i.e. consistent failure with special characters, and consistent success without them). ... View more

Hey @Burt_Macklin    We don't have the UX in the app for easy configuration of DHCP lease timers, but... we do support custom DHCP options now. I suppose in theory you could manually set DHCP option 58 and 59 to control your lease times?   The simple input/dropdown to set the lease timer is still on our to-do list as under consideration.  FYI @hiwamaru2 and @Higgins0  ... View more

@TyShawn this is good to know - interesting our switch is struggling.   @Gotest17 the tried and true method of reaching the local status page on any Meraki switch is as follows: Assign a static IP to your laptop: IP: 1.1.1.99 Subnet: 255.255.255.0 Direct connect to the switch with an ethernet cable. Navigate to 1.1.1.100 in your browser. Meraki switches all have a virtual interface at 1.1.1.100 that is always responsive to local status page requests.    Meanwhile, we'll look into why switch status pages are trickier to reach. ... View more

Hey @Mak    Here is a photograph of my GX50 power adapter brick. Looks like it can take up to 240v - is this what you needed to see?   ... View more

Great question @Franco244    There are Meraki Go Locations (that name may change), and Meraki Go users. Your security license is tied to a Meraki Go Location, and you can swap out the GX20 with a GX50 without any need to update or modify that license.   Meraki Go users can be associated with numerous Meraki Go locations. I just wanted to highlight that the license does not attach to the user, but rather where you setup the hardware. ... View more

@ZeroFoo    The GX does not currently support IPv6 configuration. The underlying firmware requirements are present, and adding IPv6 support to all Meraki Go products is on our roadmap but currently without any fixed timeline. ... View more

Hi @speakerfritz  We put the "plus" in the name to indicate its more than just a security gateway, and it could be more than 500 Mbps in some cases. Client VPN is now being included as part of the GX50 which is new and part of that "plus" label. The 500 Mbps is what we expect the GX50 to be capable of during normal operation. If conditions are ideal (low latency, little to no packet loss), we do not cap the throughput at 500 Mbps. If it can exceed this it will try to! ... View more