| Solution |
Toplogy:
Local Subnet ---> FortiGateA <--> IPSec Site-Site <--> FortiGateB ---> Remote Subnet
Observations:
- The IPSec Site-Site configuration is appropriately configured on both the FortiGate devices with relevant Firewall Policies and Routes for Local and Remote Subnets
- It can be seen that the Ping traffic is successfully processed by both the FortiGate between Local and Remote machines. However, there would be a 'Request timed out' in the Command prompt.
- In the Flow Debug and Sniffer outputs, it can be seen that the Ping Traffic is flowing in and out of both the FortiGate through corresponding Firewall Policies however, there will be no response from the end machines.
Solution:
- Disable Windows Firewall and AntiVirus (optionally) Or, implement the steps below to create a Custom rule in Windows Defender Firewall with Advanced Security:
- Log in to the Windows machine.
- Go to Windows Defender Firewall and select Advanced Settings.
- On the Windows Firewall with Advanced Security screen, select Inbound Rules and select the New Rule link located at Actions Pane.
- Select Custom and then select 'Next'.
- Select All programs, then on Next.
- Select the Protocol type as ICMPv4 and click on the Customize button.
- On the next screen, select Specific ICMP types and then Echo Request. Select 'OK', and then Next.
- Select either Any IP address or These IP Addresses under the 'Which local IP addresses does this rule Apply to?' and 'Which Remote IP addresses does this rule Apply to?' Options. When selecting These IP addresses, specify the IP addresses to be allowed.
- Once the necessary settings are done, select the Next button.
- On the next screen, Allow the Connection and Next.
- On the next screen, select the profile name (Domain, Private, Public) to which this rule should be applied, and then select Next.
- On the next screen, type the name of the rule and specify the description (optional). Select Finish.
Note:
By default, the ICMPv4-In rule only allows for local subnet only. In order for ping traffic to work, enable NAT on policy or change to scope to 'Any'.
|
