- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Where to configure "inbound" filter on the MX device
Hi,
I notice there's an API for getting inbound filters on an MX device:
GET 'https://api.meraki.com/api/v0/networks/{networkId}/appliance/firewall/inboundFirewallRules'
Successful HTTP Status: 200
{
"rules": [
{
"comment": "Allow TCP traffic to subnet with HTTP servers.",
"policy": "allow",
"protocol": "tcp",
"destPort": 443,
"destCidr": "192.168.1.0/24",
"srcPort": "Any",
"srcCidr": "Any",
"syslogEnabled": false
}
],
"syslogDefaultRule": true
}
However, I can't find where on the dashboard to configure this. There's a Note on the firewall page that says:
Inbound rules | Inbound traffic will be restricted to the services and forwarding rules configured below. |
But the forwarding rules does not look like the output above. Is there another section where this is configured?
Thanks,
-Jerome
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>That's the reason why I think I can't do NO-NAT.
And part of the reason you can not edit inbound firewall rules.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm a little hazy on this, but I think when you configure the MX for NO-NAT mode (aka it becomes just a router) it enables the inbound rules section. Or it might be you need to open a support ticket to get it turned on.
I'm pretty sure it is related to using NO-NAT.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't have any NAT configured. I guess I have to open up a support case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
By default, you will have outbound PAT configured.
Check out from this post down:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Maybe that's the problem. I'm running version 14.40.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't think I have articulated this well.
You will not get the ability to use the inbound firewall rules unless you have NO-NAT configured and enabled.
Otherwise in your configuration - all inbound initiated traffic is blocked unless you have created a NAT rule to allow that traffic in.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry that might be my fault. In the link you provided above it says:
"NO-NAT is available in the 15.x code, which you can deploy to your device right now via the dashboard."
That's the reason why I think I can't do NO-NAT.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>That's the reason why I think I can't do NO-NAT.
And part of the reason you can not edit inbound firewall rules.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
how can we enable inbound rules on meraki mx64 device
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@diablo24 yes you can run No-NAT in MX15 but if all you need is to configure inbound firewalling in the same fasion as configuring the outbound rules, open a support ticket and they can enable inbound FW rules for you, it's not visible in the Dashboard UI by default (although I have requested that it should be).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You should also be able to configure Layer 7 rules to block inbound connections from a "remote IP range" (or single /32 IP). Depending on your needs, it should be just as effective as a Layer 3 rule.
