NON MERAKI PEER IS NOT WORKING

[ArteckMX]

We are trying to stablish a tunnel bettween MX100 and a Fortigate D and we can't see Froti side, the vpn tunnel show as available but in VPN ststus is not active, and the ping is not recognized and we think they have to NAT their Fortigate but we are not sure.

Some one knows if meraki could work with a Fotinet or if theres something in meraki side thta is not working, the tracert shows my next hop but it doesen't find the fortinet public IP. Is something on their side that stop us?

[alemabrahao]

Try this setup:

[ArteckMX]

Let us try, I think we have, but let me try.

[DarrenOC]

Hi @ArteckMX , you shouldn’t have to use IKE1 as it’s the least secure option available.  I’ve integrated Meraki VPN with Forti before so it’s most certainly possible but I do remember the remote partner struggling with their Config.

[ArteckMX]

ok thank you!

[alemabrahao]

I agree, but remmember, unfortunately, there are known compatibility issues to certain vendors (yes, I know that Fortinet is not one of them). So, they can use whatever works best for them.

[BlakeRichardson]

Is the tunnel standing up at all? Your OP seems to suggest it has and that it's a routing issue now.

Have you created rules on the Fortigate to allow traffic such as ping?

[ArteckMX]

Hello Blake I don't control the Fortigate, we ask them the Portforwarding and the same encryption method, I don't know if they need another rule. They say all is confugrated but I don't think so.

[BlakeRichardson]

I would ask them to supply screenshots of the configuration. If they can't supply that your chances of getting this working are pretty slim. 

[DarrenOC]

Agree with @BlakeRichardson , the Meraki side is as simple as it gets so you’re reliant whom ever is configuring the Forti to get their part right.

[amabt]

We have Meraki to Fortigate working. We control both ends. However have recently retired that. Sounds like issue is on fortigate end.