Hi, I have a Fortigate 60E firmware 7.4.1 I have a public subnet that very often tries to connect via IPSEC VPN to the firewall. I therefore created a local-in-policy to deny the connection to this subnet, but I continue to see the logs and I also receive emails from an automation that notifies me of unsuccessful VPN connections. Shouldn't the local-in-policy block the source connection so it doesn't even create the log? The firewall navigates with a public IP directly on its WAN.
set uuid 006d9cf8-500d-51ee-cdb6-363058ded725
set subnet 126.96.36.199 255.0.0.0
config firewall local-in-policy
set uuid d69d2fdc-500d-51ee-9cb8-ff27447660f2
set intf "WAN-Fibra"
set srcaddr "Attempt_ipsec_188.8.131.52"
set dstaddr "all"
set service "IKE" "ALL_ICMP" "VPN_SSL_9443"
set schedule "always"
Hi Abdel, thanks for the reply but what you tell me I think is more of a workaround because if I have a local-in-policy that blocks IPSEC traffic, why is the log created in the VPN events section? If traffic is blocked on the WAN interface it must not be processed by the CPU. As you can see it is as if the package has been processed. It should be discarded directly.
This seems to be an expected behavior because this is not a proposal received from remote peer but an ESP packet with incorrect SPI... This packet is being dropped before local-in-policy by the kernel and iked logs it..
Is you FortiGate support acl? check with the command show router access-list
I tried to create it, I've almost never used them, I hope I did it right (I'm not sure whether I should put deny or permit in the access list as the route map is already in deny) :D I'll keep you updated
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.