- About ClaytonMeyer
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
ClaytonMeyer
Here to help
Member since May 30, 2018
Tuesday
Kudos given to
Community Record
15
Posts
6
Kudos
0
Solutions
Badges
Tuesday
Thanks again all for the replies. I advised the MX100 admin of the NIC changes but haven't heard back yet. I'll have to wait & see what they say. Hoping for a Meraki/Anyconnect like client in the near future that will address some of these issues going forward.
... View more
3 weeks ago
Thank you both! I suspect that will fix it. I was hoping for another method that didn’t require touching all of the workstations though. I’ll post a follow up after testing.
... View more
3 weeks ago
I believe I know the answer to this question but I'm hopeful there is an easier method to address this. I've got a new MX100 implementation with Client VPN configured. Users are able to authenticate and access the network just fine via Client VPN. The issue is that Windows Users are not using the internally defined DNS server as their preferred DNS server. In other words, when they attempt to resolve a corporate hostname, their local ethernet adapter's DNS server is being used rather than the VPN adapters DNS servers. Is the only way to address this by changing the network adapters metric so that the VPN adapter is preferred? Note: this is NOT an issue with the DNS suffix. Also note that on MacOS this is a non-issue. On Mac's it automatically prefers the the VPN adapter's DNS servers. Thanks in advance!
... View more
04-30-2019
11:38 AM
I was told recently, by a Meraki SE, that IKEv2 was in fact supported but was a hidden feature. You have to contact Meraki Support to enable. I've tried that twice and both times the Support person had no idea what I was talking about.
... View more
02-20-2019
08:00 AM
That makes sense. Good point. This particular scenario is a large residential environment so I would consider it low density.
... View more
02-20-2019
07:54 AM
@GreenMan wrote: I can't answer your specific question, but remember too that the dedicated WiFi radio, from MR33 upwards, provides all the background channel analysis to feed Auto RF functions; ensuring your APs find the best channel and Tx power settings for your changing environment, without needing to take a radio away from serving clients, to conduct that analysis (some competitive solutions recommend dedicated APs, purely for the same functions). GreenMan, thats an excellent point. Are you saying the the Auto Channel Assignment is dependent upon the 3rd radio?
... View more
02-20-2019
07:41 AM
I'd like to hear from people who are already running MR20's in production & what their experience has been. I understand the only difference is the lack of dedicated radios for WIDS/WIPS as well as the Bluetooth beacon/radio. I'm primarily curious if anyone who has run both MR20's and MR33's have noticed any differences. I've got a use case that doesn't really require WIDS/WIPS or bluetooth features so it may be worth saving the $100 and going with MR20.
... View more
12-28-2018
10:09 AM
What Client IP Assignment are you using for your SSID's? I had a similar issue. I changed it from "L3 Roaming" to "Bridge Mode" & issue went away.
... View more
12-28-2018
09:58 AM
3 Kudos
Nolan is correct but there is more necessary configuration. You'll need to make sure that all of the corresponding AP switch ports are configured as trunk ports. You'll need to trunk/tag VLANs 100-400 on those ports. Lastly, if the AP itself is in a separate "management" VLAN e.g. 2, you'll need to make VLAN 2 the native VLAN on those switch ports. Also, make sure that the uplink ports from those switches are also tagging those VLANs all the way back to wherever the SVI exists. Mode: Trunk Native: 2 (example) Trunk: 100, 200, 300 400 So your clients' traffic will get tagged for their respective SSID and then that traffic will be properly handled at the switch level.
... View more
12-28-2018
09:43 AM
1 Kudo
Korey, that is incorrect. I have been troubleshooting this same thing & finally got confirmation. The "Channel Width" column on the client page is displaying the client's capabilities, not what they are actually connected at. This is bad design on the part of the meraki dashboard. For example, I'm using a single RF Profile that is applied to all of my AP's. The RF Profile designates 40MHz wide channels for 5GHz. If you look at my wireless clients, most of them say 802.11ac capable and 80MHz wide channels. I submitted a feature request for this to be changed.
... View more
12-19-2018
11:21 AM
You know...I tested it out a while back but then the requirement for this was no longer needed so I lost track on it. I thought that it did work but like I said I haven't tested it in a long time.
... View more
12-19-2018
11:15 AM
I was looking for the same thing and cannot locate the client's connected data rate. I don't know if this changed since your previous posts but its not there now. The "Capabilities" column only shows 2.4 or 5 GHz. In other words, it only displays the client's capabilities...not what they are actually connected at. Is there somewhere else this information can be seen?
... View more
09-24-2018
10:49 AM
1 Kudo
Thats an excellent idea! I'm going to give this a try. Thanks
... View more
09-07-2018
08:03 AM
I would like to have the ability to restrict specific users or specific groups of users once they are connected to Meraki Client VPN. I realize I can apply firewall rules but these firewall rules apply to the entire Client VPN subnet. Since I cannot use an external DHCP server for Client VPN, I don't have a way of doing DHCP reservations for specific clients and therefore I can't filter based on specific source IP's. Obviously Meraki doesn't have anything like ASA Group Policies. Are there an other mechanisms I can try to do this?
... View more
Labels:
05-30-2018
07:32 AM
1 Kudo
Another vote for IKEv2 support
... View more
Kudos given to
My Top Kudoed Posts
