I disagree with the assessment that it does not affect functionality.   Here is my scenario..... I connect to the network using the correct password and have selected "Auto Connect".  I open a web browser and go to a website. The website loads. Everything working. Nice...I can get some work done.... Oh wait... Wifi connection just dropped, and I am no longer online. I try to connect to Wifi network again, and it will not let me connect... says Bad Password.... try again, nope. Bad password.  Keep trying... finally it connects and im online. Get back to work, and then boom, dropped wifi again. Logs all show Bad password as the culprit, even though the password was typed in correctly.   How is that "not affecting functionality" ? By the way, that even happened on a brand new computer as well as established devices that had been on the network for some time.   I would like this to be properly investigated by the meraki Support Engineers. We took our entire Campus of 350,000 Square feet (and over 100 Meraki AP) away from Ruckus to Meraki because of how well the system seemed to work and the level of support we were getting.... not instilling confidence at the moment. ... View more

Also having this issue.. we have over 100 MR33 APs, running  26.6.1 Firmware   Surely there is a solution to this issue?? ... View more

Okay, yeah that makes sense.   I plan on tagging an empty port (19 i think) as VLAN 2.  That port will lead to all the AP's and hard lined devices that will be using the Charter internet.   So what you are saying,(correct me if im wrong) is that once I make that physical link, and tag that port as VLAN 2, the current settings we talked about in above replies, are good to go and the Clients that will be using Charter should be good. ... View more

I guess Im having an issue understanding the purpose of the MX I.P then....   I only have the one MX250 and it has an IP of 172.20.0.1   So how is setting VLAN 2, with an MX IP of 10.20.0.1 going to do anything? 10.20.0.1 doesnt actually exist, I just made up that subnet....   Also, currently, the MX250 (172.20.0.1) is acting as the DHCP server. With this is mind, and having Charter traffic go across WAN 2, how will they get IP addresses in to 10.20.0.1/20 ranges?     Maybe this is a case of a lack of understanding on my part, of how this works ? ... View more

I put the subnet in as the MX I.P. for now so I could save it..... If I try and put the actual I.P of the MX (172.20.0.1) it gives an error (which makes sense, because it is on the other VLAN).... ... View more

Hey Phillip, I have another question about this one....   Under Routing, What do I put as the MX I.P. for my leased out internet, on WAN 2, using a subnet of 10.20.0.1/20?  I tried using the true IP address of the MX and it threw an error....         ... View more

  Realized I had to put "Any" in Destination instead of leaving it blank ... View more