Due to current events, we are aware that many of our customers adopted a WFH policy. We proactively reached out to our customers to investigate what Dashboard improvements we can implement to assist our customers during this difficult time. Based on our customers’ feedback and review of our support cases, we discovered that we can address many of these concerns with additions to our existing Dashboard UI pertaining Client VPN.
In summary, the new Dashboard UI additions are:
On our current Client VPN page, you will now see descriptions of each Client VPN parameter. This page also includes helpful links to our KB for a more comprehensive configuration guide.
As Client VPN usage increases, we found it beneficial to be able to filter for active Client VPN connections. We can now achieve this on the Network-wide > Clients page by selecting both the Online and Client VPN filter boxes.
Lastly, we added a FAQ tab within the Client VPN page. Here, you will find answers to the most common questions regarding Client VPN.
If further assistance is required, please feel free to reach out to our 24/7 Support. Our Support contact information can be found by navigating to the top right hand corner of Dashboard. Click on Help > Get Help > Still need help > either Submit an email case or Call the Meraki Support team.
We understand that this is a difficult time for all of us. We’re here to help smooth the transition of our customers as we adopt the WFH policy. Please feel free to provide any feedback in the comments. We will actively review your suggestions to see where we can improve to make your user experience better.
As a reference, below lists our current Client VPN KBs:
Great job and kudos to the Meraki team for actively looking for suggestions from the users of your equipment, and great job implementing these changes so quickly. There is one other feature I would love to see added to the dashboard in regards to the client VPN, that being client VPN reporting, it would be really nice to see who was connected, when they were connected, and for how long in a nice user friendly screen without having to dig through the logs. I feel like that would be a much appreciated feature by not only myself but the entire community.
Thank you for your feedback. We are currently looking into these suggestions. Once we have any updates, we will follow up within the Community.
Great job in implementing these features.
I would also like to request the ability of detecting failed attempts to access the client VPN. With the added focus on VPN traffic, it would be really nice to know if someone from <INSERT_FOREIGN_COUNTRY_HERE> is attempting to access our VPN every few hours. Of course, logging/alerting on failed attempts also helps us detect and better help end users who are legitimately having problems.
Alternatively (or additionally) if we could actually search (not just filter) the event logs, manually detecting such attempts would be a LOT easier.