Hi I am having the same issue and have done everything you have recommended and including looking at Wireshark captures but am also still getting 404 errors! Postman seems to be using TLS v1.2 but I have played with the settings to see if it makes a difference and it doesn't.   I simply want to create an SSID via POST in postman... as follows:-   https://n194.meraki.com/api/v0/networks/L_672162244385048740/ssids/0   I have tried without the shard using https://dashboard.meraki.com and https://api.merkai.com aswell and am asusing these both should in theory work as they will just reditrect the https request ? But neither works.   The JSON body part is as follows:-    { "number":0, "name":"TEST", "enabled":true, "authMode":"psk", "encryptionMode":"wpa", "psk":"abcd1234", "splashPage":"Click-through splash page", "perClientBandwidthLimitUp":0, "perClientBandwidthLimitDown":0, "ssidAdminAccessible":false, "ipAssignmentMode":"Bridge mode", "walledGardenEnabled":true, "walledGardenRanges":"192.168.1.1/24 192.168.37.10/32" }   ... View more

Hi asked the same questions myself!  Netflow doesn't work properly with some of the typical monitoring apps out there like SolarWinds which we used where I worked. Was told Stealthwatch did see the Meraki netflow format properly however its not what we wanted. So decided SNMP monitoring via PRTG is what I am trying to get to monitor the WAN interface port to get capacity used.  Meraki do a very poor Job here... netflow that doesn't work and no reporting on the WAN port usage ( why not Meraki crazy ! ) In my experience ISP's aren't great at giving this data either so like me your struggling to find a decent way to show this information which is surely something most Meraki clients want to see. What is my WAN port usage !  ... View more

Hi you are correct ! It sends what appears to be standard Netflow V9  data to the collector and I captured it using Wireshark to our Solarwinds netflow collector however the engineer at solarwinds explained that the exporting process periodically resends templates to ensure that the collecting processes have received them. While IPFIX does provide a sequence numbering facility to allow a collecting process ( in this case Solarwinds )  to roughly estimate how many flow records have been lost during export over UDP this does not protect templates. So a collecitng process that loses a template in the middle of the export may be unable to interpret any flow records until the next template re transmission.    Quite a mouthul!     This article explains it all:   https://is.muni.cz/repo/1181098/flow-monitoring-explained-paper.pdf   Upshot is Solarwinds does not understand the Meraki Netflow data and its only Meraki can fix it by the sounds of it!  This is a major issue for some companies that use Netflow extensively on first and second line support desks!     Over to you Mr Meraki.     ... View more