I have /28 Public IP pool and set my security appliance in NAT mode and given rest of the public IP addresses to my client through MS 220, 350 & 425. Clients are complaining that they can't ping and access public IPs from other ISPs.
Kindly help me to fix this issue.
Regards
Khurram Shahzad
I would suggest opening a case with Meraki Support for configuration assistance. Not sure if I understood your exact design requirement, but sounds like may want to configure the MX in NAT mode as an Internet-facing firewall and then have a DMZ VLAN configured with public-facing machines like a web server perhaps, along with internal VLAN(s) and some 1:1 NAT rules. Perhaps this Support doc might be useful. https://documentation.meraki.com/MX-Z/Firewall_and_Traffic_Shaping/Creating_a_DMZ_with_the_MX_Securi... But I'd suggest opening a case with Support and include a network diagram with your addressing and describe the pings that are failing to you public IPs. If applicable, also check out the separate support docs on 1:1 NAT and port forwarding. https://documentation.meraki.com/MX-Z/NAT_and_Port_Forwarding/Configuring_1%3A1_NAT and https://documentation.meraki.com/MX-Z/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_M... Hope that helps!
Is your security appliance doing DHCP and giving your clients private IP addresses (which will then be NATed)?
Yes my security appliance is assigning Private IP addresses to my client through DHCP but I have assigned Public IPs to some customers through that internet works fine but they cannot ping Public IP from other ISPs.
Security Appliance > Firewall
When you setup the Public IP to LAN IP NAT you have to set the allowed inbound connections rule to:
Protocol: ICMP
Remote IPs: Any or a subnet if you want to be more specific on who can ping.
Dear I am not assigning Private IPs to my client. I am assigning them public IPs.
Ah so you are having issues pinging out? Any difference if you ping the IP directly vs name to make sure it isn't a DNS issue?
I have putted my case in cisco meraki but they are not providing me any solution even not bothering to reply on my emails. Kindly suggest the solution as I am losing my clients.
Like @Adam, I can not clearly understand your configuration which is making it very hard to help you. Lets get specific.
Please answer these questions:
For the ping that does not work;
Kindly see the topology diagram below and 5.5.5.0 is Public IP subnet.
Thank you for the diagram. Now give me an example of which of one of the devices depicted cannot get to what kind of destination?
"whenever I tried to ping 5.5.5.3 from other ISP always get "request timed out" message."
So you mean if some external source tries to ping the 5.5.5.3 client they get request timed out or no replies?
If you are wanting publicly accessible IPs on your private clients I think you'd want to do either of the following.
1. Set the MX to passthrough mode
2. Keep the MX set to NAT mode and give your internal client machines some internal DHCP range of static IP's. For example if PC-PT had an internal static IP of 10.0.0.3. Then go to Security Appliance>Firewall and setup your 1:1 NATs and with selective "allowed inbound connection" firewall rules. Here would be a screenshot example.
Agreed with @Adam suggestion. It sounds like the MX is running in NAT mode and doing exactly what it should be doing.
If I set MX in Pass Through Mode should I still manage to apply layer 7 Policy?
Kindly reply if we set the MX in pass-through-mode do we still apply policies?
@khurram wrote:If I set MX in Pass Through Mode should I still manage to apply layer 7 Policy.
It looks like the policies should be applied in passthrough mode. It would be worth a try; however, I would recommend creating DMZs and NATting to private IPs to allow for more firewall rules to be managed more easily.
"An MX/Z1 in passthrough mode can be configured to perform a number of functions like when in NAT mode. However, the appliance acts as an invisible third party, only touching traffic when required by a configured function. It can passively perform intrusion detection and collect statistics about traffic passing through it without taking action. It can also perform traffic shaping and content/security filtering functions to intercept and manipulate traffic as needed:"
Hi Khurram,
Did you ever figure this one out?