Meraki

Dunky · ‎Mar 14 2024

Roles only apply to SSO. SSO isn't supported in Meraki Display. Hence I am unsure how to create a user and give them access to cameras only?

Dunky · ‎Mar 14 2024

Anyone actually using this? I've got the app OK on the Apple TV box with the intention of using it to display a videowall, but how do you create dashboard users that can access cameras only? What's to stop that user logging in via a Web browser on their PC and seeing cameras they shouldn't be allowed to add other stuff within that network (mx's, Sensors, APs, sensors etc? I created a generic user with a fictitious email address but cannot login as it says invalid credentials. TIA

Dunky · ‎Jan 24 2024

Thanks Philip, that looks like a great solution. I will investigate pricing and look into a trial to confirm it will achieve what we need.

Dunky · ‎Jan 23 2024

Thanks @PhilipDAth & @Ryan_Miles Breaking out the cameras into a separate network, or even organization seems a bizarre approach to address what in my opinion is a fundamental issue with access rights not being granular enough. I wouldn't have thought it unreasonable to be able to prevent some network admins from being able to access video. If say 2 roles were passed across via SAML, the 1st being Full access to network XYZ and the 2nd being a camera/sensor role that denies access to footage on cameras in network XYZ, then the result should be the user being able to access all the network settings for the camera, but just not able to see the image itself (dashboard and vision Portal).

Dunky · ‎Jan 19 2024

We have a number of network admin users that have full organization access, and some that have Organization Read Only Access. I have been asked to look into preventing some of these users from being able to see the MV Cameras (without moving the the cameras out into a separate network). This is to comply with GDPR. Can anyone advise on how I achieve this. We use SAML (SSO via Azure). Thanks in advance.

Dunky · ‎Jan 9 2024

The issue I have is on the Camera & sensor roles page the you cannot restrict what sensors the user can see. The "All sensors" box cannot be changed. Need to be able to select sensors by network, tag or model.

Dunky · ‎Jan 3 2024

Does the remote MS have to be in a different VLAN from the MS's on the local site. We have a Network Mgmnt VLAN where all the MS's, MR's etc have static IP's.

Dunky · ‎Jan 3 2024

Thanks for the prompt reply Ryan. No, there will not be any MR's in the remote building, just VLANs on the switch there. Sounds like a result, many thanks. So I can get away with an MS120/130 in the remote building.

Dunky · ‎Jan 3 2024

@Ryan_Miles I know things have moved on since this thread so just wanted to check out if we can now do this using MR76's. I have a remote building that I need to extend the network into. The remote building will have a switch and needs to support multiple VLANs (cameras and users etc). I don't need any clients to connect to the MR76's (although bonus if they could), I just need my VLANs that are available in the main site to be available on the switch in the remote building (over the road). All interVLAN routing is currently done on MX's.

Dunky · ‎Jan 2 2024

Do we know if/when this will support SAML? All our logins use our Azure.

Dunky · ‎Jan 2 2024

Really?, wow that is not good then. It doesn't matter too much for me as we send traffic from guest subnets over WAN2, it was more to limit the bandwidth from guests on WAN1 when WAN2 failed. Yet again, another reasonable feature that's not available on the MX, it does make me question whether the MX is really fit for purpose as a firewall.

Dunky · ‎Dec 27 2023

Ahhh finally!!! Thanks for sharing 🙂 Yeah, roll on the same info for MT etc. although I see MR is due imminently...

Dunky · ‎Dec 27 2023

I achieve this via the Traffic shaping rules where I limit the total bandwidth available to all clients on specific subnets added together, as per below:

Dunky · ‎Dec 1 2023

I have tested giving the user R/O access to the network that the cameras are in, and yes that ensures that the floorplan shows correctly in the Vision Portal. The problem is though that these are just users - they will just get confused with seeing AP's, switches, Security appliances etc. So its not something we can enable just for the cameras to show correctly on the floorplan. The Google maps display is of no use - it shows cameras in the middle of the river - not having the display at all would be better than the google map without a floorplan to show where the cameras actually are. The site would use this to show contractors where the cameras are physically located when they need maintenance/replacement. I will therefore leave this as-is and submit a Feedback form on the dashboard.

Dunky · ‎Nov 30 2023

Thanks Ryan. I will have a look in the morning although it does seem strange that it isnt displayed by default in the Vision Portal.

Dunky · ‎Nov 30 2023

When logged in as a user with "View and export any footage" rights, I can create exports in the Vision Portal, but when trying to delete them I get "An error occurred while deleting 1 job". I should be able to delete my own exports. Is this another known bug?

Dunky · ‎Nov 30 2023

When logged in as a non-admin user (view and export any footage), the floorplan shown in the Vision Portal is not shown, we just see the Google map onto which the cameras are superimposed. When using an Admin account, the floorplan is displayed correctly when selecting the camera. Is this a known bug or am I missing something?

Dunky · ‎Nov 28 2023

I waited until the switch showed that its config was up to date. The feature just isn't working - changing the VLAN list against a group name in the default profile does not actually change the allowed VLANs on the switchport - you have to go into the port config and select the group again. The port and switchports displays then show the correct VLANs. I've raised a case, so will report back.

Dunky · ‎Nov 27 2023

Will do, gets a little annoying when simple features appear not to have been tested before they are released 🙂

Dunky · ‎Nov 27 2023

When I referred to MX, that was the description "MX Uplink" of a trunk port on an MS. I applied a VLAN group with VLANs 3,4,10 in it. Then amended the VLAN group to remove VLAN 3 but the switchport still showed allowed VLANs of 3,4,10. If you then edit the switchport and reselect the exact same VLAN group for the allowed VLANs, then it updates the allowed VLANs just fine removing the 3.

Dunky · ‎Nov 27 2023

I've been 'playing' with this feature and uncovered what I feel is a 'bug': Have created a Group "MX-Uplink" with three VLANs Applied this to the Allowed VLANs field. All good so far. Now, if I go and amend the VLAN list against the group I was expecting that to be reflected in the port configs that it is applied to. That is not the case, you have to go into the port config and select the same VLAN group again and this time it updates the allowed VLANs list. So what is the point of having a Group if when you amend it, it doesn't update the ports that its applied you - you still have to go and manually update the switchports that its applied to. Am I missing something here?

Dunky · ‎Nov 24 2023

I notice these issues are still there, is there any timeline as to when we should expect them to be fixed so that the Switching/Switch ports display shows the correct values from the profile rather than the ones on the actual port which are overridden?

Dunky · ‎Nov 23 2023

I assume this is still a limitation? We are looking to replace some legacy cameras and NVR etc with Meraki MV's but need to have a VPN to a 3rd party ARC (Alarm Receiving Centre). If we cannot control ingress traffic and the ARC will not allow us to put an MX at their site then it is impossible for us to go down the Meraki MV route without a separate firewall which defeats the goal of managing everything thru the Meraki dashboard. Would welcome any input or feedback.

Dunky · ‎Oct 6 2023

Ahh ok, thanks @cmr That's a shame, lets hope they bring out some MS2nn with mgig ports and physical stacking. The issue i keep coming across is no Profinet Support which limits where we can deploy Meraki switches and have to keep PLC's etc connected to unmanaged 3rd party hubs/switches. Would love to deploy ruggedized Meraki switches with Profinet support inside the factories.

Dunky · ‎Oct 6 2023

Is there any reason why the 24+ port models dont have physical stacking ports (or do they)? Would have been an ideal alternative to the MS210. And secondly do these support Profinet, or are there any plans to across the range?

About Dunky

Dunky

Community Record

Badges