@BlakeRichardson    I mean, sure, there's a lot of moving pieces. But unlike windows client VPN which has A near infinite combination of configuration variables (both on the windows side and 3rd party VPN side...) on top of 1000's of different NIC driver combination  in a software package that itself has a million different moving parts owned by 100s of different teams....   This is more one-sided, Meraki owns the process from start to finish. The Software, hardware and management plane are owned by Meraki There are only two dev teams that would have a stake in this feature. MR and Dash. A KB that dictates exactly how to set this up results in an error   So while yes, it's impossible to test for every bug, this bug in particular showcases a glaring flaw/breakdown in internal communication and QA. MR-PM released a feature yet didn't properly test the one page in which the feature would be configured.   The most basic QA would have been to test an SSID in it's default state. No Encryption w/ Meraki NAT. Even moving from that to WPA3 w/ 802.11r fails.   @BlakeRichardson Have you found any config permutation that would allow the feature to be set?   ... View more

Just submitted one, very curious how such a basic issue was not noticed during QA. Does Meraki now just commit feature additions without verifying the feature can actually be configured on existing networks? The most basic of basic QA would have caught this.   QA Step 1: Upgrade existing network to MR 30.1 QA Step 2: SSID-A (Existing WPA2 Config): Attempt to configure WPA3 and 802.11r QA Step 3: SSID-B (Existing WPA3 Config): Attempt to configure 802.11r. ... View more

This looks to be a feature request for SM.   It's definitely possible via MDM but SM doesn't support it yet for Android.   Samsung Knox SDK Docs.   ManageEngine Docs   It's possible it's a feature already being worked on. I would reach out to your SE. 🙂 ... View more

Hey @Porcap ,   1-2Mbps is an incredibly low throughput rate that makes me believe these clients are connecting using 2.4Ghz. If you take a client that historically has high throughput and put it next to the client that has low throughput, and the device that has high throughput continues to have high throughput (even after cycling it's wireless adapter)... Try this.   On the device with low throughput go to ap.meraki.com OR Go to network-wide > clients, select the client with low throughput, and check it's overview page. If either says it's connected using 2.4Ghz AND the clients summary page shows that the client supports 5Ghz. You need to focus on why it's connecting to 2.4Ghz as the decision is more or less up to the client with minimum bitrates set as low as yours are.   Since you have AX APs and mentioned the net adapters are older...Two things you can try   Under the RF Profile, Disable AX for both 2.4Ghz and 5Ghz. See if the client connects at 5Ghz and see's improved speed afterwards. Ideally this should NOT be your permanent solution as you lose the benefits AX provides. UPDATE THE NIC DRIVERS. I can't tell you how many times I've seen issues with older clients connecting to AX APs that were caused by having old drivers. Intel has a tool that will find outdated intel NIC drivers and install them for you. Link Alternatively, if that doesn't find anything. grab the Wireless Card Model number under windows device manager and search for the drivers on Intel's support site. ... View more

[deleted] ... View more

There's a lot of ambiguity here.   Some questions that need to be answered   Is the issue that clients are unable to automatically discover these printers? Are you able to print to this printer on the GR10 if you manually setup the client PC printer config with the printers IP address? If the answer is no to both of the above. Then your focus right now should be on layer 3 roadblocks such as firewall rules, VLANs and NAT instead of Client roaming behavior and L2 mDNS/bonjour.   Do you receive the same IP address when connected to the GR10 that you do when connected to the MX65W? Yes? Check switch ACL's Check MX Outbound rules, I'm not actually sure if the MX outbound rules can apply to traffic bridged between wired/wireless in a similar fashion to the MR L3 rules. You can throw in an Allow Any Any at the top of the MX outbound rule set and see if behavior changes. ) No? Is the GR10 SSID clients are connecting to configured with Guest Mode enabled? Yes? Disable Guest Mode (or throw in an exception for the printer IP if one's configured) Are VLAN's configured? Yes? Check MX outbound firewall rules. Last rule is allow any any. If you have any custom L3 rules throw in allow any any above them to see if that resolves the issue. ... View more

Great job guys and gals!   F@H User: Ryan_Ludwig   For anyone that folds/BOINC's regularly... Check out gridcoin! They give you crypto (GRC) based on how much you contribute to BOINC projects. It doesn't come anywhere close to offsetting the electricity costs but at least it's something. A vote just passed to tie in FAH work as well!    Gridcoin ties your BOINC CPID to your wallet through a "beacon", a unique key that you temporarily flip one of your BOINC project usernames to. It's the ACME DNS challenge equivalent of inserting a unique DNS txt record to prove ownership and generate a SSL cert.   BOINC projects worth taking part in (IMO): Rosetta@Home Work: Protein Structure prediction gpugrid (Has GPU Work Available) Work: full-atom molecular biology simulations utilizing Nvidia CUDA cores. A lot of their recent research has been focused on incorporating pytorch based ML techniques found in ACEMD4 World Community Grid (Has GPU Work Available) Work: Various problems in public health and clean energy   If you plan on deploying BOINC out to multiple clients. I highly recommend the management tool BoincTasks. It's UI looks like something out of the 90's but it's incredibly useful at managing BOINC clusters.   Happy Holidays! ... View more