Meraki

alemabrahao

Take a look at this: https://dunxnew.wordpress.com/2015/09/24/custom-pie-charts-in-meraki/

alemabrahao

It will not work. On event log page you can see just the blockd URL's. Unfortunately the dashboard is quite limited in this regard.

alemabrahao

The dashboard is very limited in this regard.

alemabrahao

The best way is to send the logs to a syslog server.

alemabrahao

By the way, this is a Kindle issue. https://www.amazonforum.com/s/question/0D56Q0000DiG2jvSQC/wifi-splash-page-error-110 https://www.reddit.com/r/kindle/comments/1ep5aon/error_code_110_when_trying_to_get_on_wifi_with/

alemabrahao

You can allow the device to bypass this. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Blocking_and_Allowing_Clients#Allow_List

alemabrahao

You can do this via API and it can save you a bit of time compared to sending out each invite manually. But either way, each user will receive an invite, so there's not much you can do about it.

alemabrahao

Install the software on the new phone and then set it up again.

alemabrahao

Here is all the useful documentation you need. https://documentation.meraki.com/MR/Encryption_and_Authentication

alemabrahao

Here is the documentaion with the first steps. https://documentation.meraki.com/MR/MR_Quick_Start Note that the access points need to have internet connection to communicate with Meraki Cloud.

alemabrahao

Ensure that the Network Security Groups and any Azure firewalls are configured to allow traffic between the subnets and from the on-premises network.

alemabrahao

If you check the documentation you will notice that port forwarding and 1:1 NAT have differences. While port forwarding uses the IP configured on the MX's WAN, in 1:1 NAT you can define another public IP within the block that your ISP provided, obviously if it is not a /30. So there is no priority.

alemabrahao

There is all information that you need: https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Firewall_Settings https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Blocking_Inbound_Traffic_on_MX_Security_Appliances

alemabrahao

The Meraki MX should not typically respond to DNS queries on its WAN interface. You can create a rule to deny inbound DNS requests (port 53) on the WAN interface. If the issue persists, it might be best to contact Meraki Support.

alemabrahao

Did you check the link I sent you?

alemabrahao

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Configuring_DHCP_Services_on_the_MX_and_MS

alemabrahao

Yes, It is probably configured in the MX configuration to use it as a proxy.

alemabrahao

It might be interesting to open a discussion in the Postman community.

alemabrahao

It's not exactly the same error, but maybe it will help you. https://medium.com/@odidaodida/how-to-fix-postman-typeerror-cannot-read-properties-of-undefined-reading-id-on-windows-d83190ded257 https://community.postman.com/t/old-request-updated-typeerror-cannot-read-properties-of-undefined-reading-name/49373

alemabrahao

Is the SSID not configured with DHCP in NAT mode correct? Can you share the SSID and Firewall settings?

alemabrahao

I believe Bonjour is not a problem. Can you at least ping the printers? Check your routing, firewall rules, etc.

alemabrahao

How are Wireless clients accessing LAN configured? https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/MR_Firewall_Rules https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/Bonjour_Forwarding

alemabrahao

You can try contacting Meraki support, but I believe it will not be changed since it is a Meraki policy.

alemabrahao

Is it possible to do a test by changing the ports from trunk mode to access mode? Just to validate one thing.

alemabrahao

Take a look at this: https://learning.postman.com/docs/collections/running-collections/working-with-data-files/

About alemabrahao

alemabrahao

Alessandro Abrahao

Community Record

Badges