Meraki

Dunky · ‎Jun 1 2023

Surely the time should be derived from the timezone of the network in which the sensor resides.

Dunky · ‎Jun 1 2023

Is it possible to get the download to convert the times to local time? When I download readings for the month from an MT11, it is confusing as each row in the xlsx shows UTC time rather than local time.

Dunky · ‎Jun 1 2023

I've marked this as the solution solely to keep the board from having unresolved topics. We are still trying to identify what these 2 clients are, each are failing association approx 2,800 times/24hrs!

Dunky · ‎May 25 2023

A sensor that had multiple outlets on it thus allowing us to remotely power-cycle devices would be awesome. I can see it being expensive to deploy multiple MT40's to a site especially with the licencing. I would love to get rid of the Schneider IP PDU's !!

Dunky · ‎May 25 2023

Thanks, I will attempt to find out, although all I have are MAC addressed, its not showing the host names which may make it difficult to track them down.

Dunky · ‎May 25 2023

Can anyone tell me what error code 31 actually means, I cannot find any reference to it online. This is the failure reason I am seeing in the Connection Log: auth_mode='wpa3-psk' 11k='0' 11v='0' error_code='31' radio='0' vap='0' channel='1

Dunky · ‎May 24 2023

Any updates on this. We will shortly be implementing MV's at one of our sites, and they want a videowall in the factory. That isnt going to work if it keeps logging out. Or maybe the Vision Portal has a different idle timeout that can be set to never logout?? TIA

Dunky · ‎May 24 2023

Same here, "Access Denied".

Dunky · ‎May 17 2023

+1 here too. We have just purchased a number of MT11's for use in refrigerators in a Laboratory. Naturally the Lab Technicians need R/O access to the Reports. Without this, I fear the other laboratories may go elsewhere and I am trying to push Meraki across our estate.

Dunky · ‎Mar 17 2023

I have 20+ site-site VPN's from MX67's, MX84's, MS85's to Native Azure VPN and they all work without any issues. I assume you have ticked the local subnets that you want to allow access to nothing is blocked in your Site-to-site outbound rules (although they will only apply to traffic from your MX to Azure? If thats all ok then it sounds like an issue at the Azure end which is beyond my expertise 🙂

Dunky · ‎Mar 7 2023

The annoying bit is that in an environment where all I need is site-site VPNs to Azure from my sites using the native Azure VPN, Meraki forces me to create a hub - I have no need for a hub so I then have to create rules to block all traffic to ensure my sites cannot talk to each other via an unwanted hub.

Dunky · ‎Jan 27 2023

Meraki did indeed come back and say they can make the Cellular Failover ruleset apply when failover to WAN2. However, there is no indication on the page that this is in force, and given that we use the L3 rules to provided VLAN segregation then I declined the offer. What is really needed is on the L3 ruleset to have a dropdown on each rule where you can specify which WAN interface it should apply to (1, 2 or All)

Dunky · ‎Jan 10 2023

Support say this cannot be done. I have clicked on "Give your feedback" and sebmitted: "I need the ability to block a specific IP or subnet from using WAN2. This is because we have Cell Boosters that form a VPN to the cell provider and they whitelist the public IP. If the public IP changes (which it does when MX fails over to WAN2), they blacklist the box. Same could be achieved by allowing us to specify the WAN Interface or ALL on each of the L3 firewall rules (so I can deny the devices outbound traffic on WAN2)"

Dunky · ‎Jan 6 2023

Thanks, I'll open a ticket and see what they say.

Dunky · ‎Jan 6 2023

I have a Boostbox at a site that is used to generate a local cellular signal which the cell phones connect to and traffic is then tunnelled over a VPN from this boostbox to the cell provider. However, should the source public IP change, the provider locks out that box as they think it has changed location. So the question is how can I prevent a specific IP and/or subnet from using WAN2 (i.e. when WAN1 fails). .

Dunky · ‎Jan 3 2023

That's great news, sounds like dodgy hardware then. Thanks for letting me know, I will sleep easier knowing that I dont have to worry about hitting the same issue on my MX84's

Dunky · ‎Dec 22 2022

@AlexP Are there plans to allow us to specify permit/deny and src/dst for the L7 rules? Many a time I want to permit for internal apps but I cant so have to remove the L7 rule for internal apps to work which means its enabled for all traffic, not just between the specific src/dst that I need to permit it for.

Dunky · ‎Dec 15 2022

@fabricio_cp Did you get a resolution or explanation from Meraki

Dunky · ‎Dec 7 2022

Thanks, I appreciate the update and please keep me posted.

Dunky · ‎Dec 7 2022

Thank you for highlighting this. Can you please post how you get on. I am planning on upgrading to 17.10.2 in the New Year and I have a pair of HA MX84's in Poland that have Auto-VPN connections to a vMX in Azure and the last thing I need to to break that. Thanks in advance.

Dunky · ‎Dec 7 2022

"Also, if you have an organizational need to whitelist a detected event, your only option is to whitelist it regardless of source." Yup, I've had to add an exempt rule and although its only from one IP address the MX does not allow you to specify a src IP/subnet. Very basic and sort of defeats the object of a firewall.

Dunky · ‎Nov 30 2022

Ahh, thanks, I can now see if I add a specific rule for IPV4 addresses the D changes to 4.

Dunky · ‎Nov 30 2022

Can anyone tell me what this means (have upgraded from 16.6.6 to 17.10.2) to do some testing but cannot find any documentation anywhere on what "Enforce" actually means? Thanks

Dunky · ‎Oct 19 2022

I guess I could put specific clients into a Group Policy, however that does not address the underlying issue of the L7 rule applying to ALL traffic as we cannot specify src/dst IP's. So what if its Stastistical Peer-to-Peer if it's between internal IP's? I dont care, but we have no way of locking this down so even with a separate Group Policy applied that would still allow Statistical P2P on ALL traffic, not just between my internal endpoints.

Dunky · ‎Oct 19 2022

To the best of my knowledge its always been like that. Until such site as they give us the ability to add ALLOW rules and src/dst IP's its unusable! I have had to permit Statistical Peer to Peer which applies to ALL traffic purely to allow management of an internal phone system!

About Dunky

Dunky

Community Record

Badges