The Meraki is local, to make the VPN possible you need to create a setup on the Fortinet. In my case, the Fortinet appliance is a virtual machine in an Azure subscription. Today I had this kind of case and it’s not so great to find some information about how to make this vpn tunnel working propperly. It’s not common for me to configure a site to site VPN tunnel between a Fortinet device and a Meraki device.
Splunk is able to ping the FortiGate LAN interface.īack to the Splunk instance, now we are able to see logs from FortiGate. If we may not see FortiGate logs on Splunk, we need to type the commands below to change the source-ip address to send log from using the “management interface” to using the LAN interface “172.16.1.254” config log syslogd settingĪlso, enable PING Access, HTTP, and HTTPS on tunnel 1 interface of FortiGate. Log out of FortiGate and log back in to generate logs. Enter the IP address of Splunk on the IP Address setting, and click choose All for “Event Logging” and “Local Logging”. Be default, FortiGate is using UDP port 514 to send log to Syslog.Īpp Context: Fortinet FortiGate App for SplunkĬheck the UDP 514 port is running in the instance.īack to FortiGate, configure Fortigate to send logs to Splunk on AWS. Select new Local UDP.Įnter 514 on the port setting. Install FortiGate App for Splunk and Fortinet FortiGate Add on Splunk.Ĭlick on the Settings tab and configure Splunk to get FortiGate logs. RDP to Windows instance and disable Firewall to send logs from FortiGate.ĭownload Splunk Enterprise for Windows and install it into this instance. On Security Group, add a couple of rules to allow ICMP and all traffic on FortiGate LAN subnets to access this instance. Launches a new Windows 2016 VM instance to install Splunk. Pings from Kali machine to the Linux VM instance on AWS. On FortiGate, configure a new static route to AWS LAN subnets.Ĭonfigure access rules to allow FortiGate LAN subnets to communicate with AWS LAN subnets. This machine is used to test VPN site-to-site.Ĭonfigure a new static route to allow LAN subnets on AWS to access LAN subnets on FortiGate. Notes the set “mtu 1427” and set “mtu-override enable” does not available on FortiGate 6.2īack to AWS and launch a new Linux VM instance.
This is a diagram that I have used for this demonstration.Ĭreate a new Internet Gateway and attach it to your VPC.Ĭreate a new route to 0.0.0.0/0 to your Internet gateway.Ĭreate a new Customer gateway with the public IP address of FortiGate.Ĭreate a new Virtual Private Gateway and attach it to your VPC.Ĭlick Download Configuration to configure on your FortiGate.Ĭopies these commands and pastes them into FortiGate.
0 kommentar(er)
