Possible bug in 1.26 in GET inboundCellularFirewallRules response schema?

daniel_abbatt
Getting noticed

Possible bug in 1.26 in GET inboundCellularFirewallRules response schema?

There are a couple of new endpoints in 1.26 which support Appliance inbound cellular firewall rules

https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-firewall-inbound-cellular-firewall...

 

Is the GET response correct? It's just an array of rules, which in itself is fine, but does not follow the same pattern as the following (along with many other "rules" endpoints)

 

The PUT for the same data

https://developer.cisco.com/meraki/api-v1/#!update-network-appliance-firewall-inbound-cellular-firew...

The GET for cellularFirewallRules

https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-firewall-cellular-firewall-rules

The PUT for cellularFirewallRules

https://developer.cisco.com/meraki/api-v1/#!update-network-appliance-firewall-cellular-firewall-rule...

 

These other endpoints wrap the array in a "rules" property.

 

Can someone at Meraki please either

- confirm that the new GET endpoint is correct as documented and is an exception to this pattern, or

- confirm that the documentation is incorrect and the actual endpoint behaves like the others

1 Reply 1
Mat_Jones
Comes here often

I noticed this too, trying to get an example response back but it keeps being denied. I keep getting the follow error;

 
"errors": [
        "This endpoint only supports MX networks with IPv6 capability"
    ]
 
Confusingly, the example response in the docs shows an IPv4 address coming back in the destCidr field so not sure why IPv6 is a requirement.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.