Hi
since I turn on mail notification on VPN event I'm getting the error allot
MY_IP is always my WAN1 IP
UNKNOW_IP is diffrent vevrytime, when i get this error repeatedly the IP is all at the same subnet (only last number change)
---------
Message meets Alert condition date=2018-11-08 time=05:31:26 devname=FG100D devid=FG100D logid=0101037128type=event subtype=vpn level=error vd=root logdesc="Progress IPsec phase 1" msg="progress IPsec phase 1" action=negotiate remip=UNKNOW_IP locip=MY_WAN_IP remport=20550 locport=500 outintf="wan1" cookies="3e35c70729dfedef/0000000000000000" user="N/A" group="N/A" xauthuser="N/A" xauthgroup="N/A" assignip=N/A vpntunnel="N/A" status=failure init=remote mode=main dir=inbound stage=1 role=responder result=ERROR
-------
what this massage indicate? is it attack on my WAN?
what can i do to prevent this error
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Well, it could be someone trying to brute force their way into your network. If you only have site-to-site tunnels configured then you really don't have anything to worry about. If you have client IPSec configured then there is a very small chance they could eventually get in (very small).
If it's definitely always the same remote subnet and you have client IPSec configured, you could always put a block rule for that subnet above your IPSec policies. Or, put a blackhole route for that subnet in your static route table. Or, if you have a router outside your firewall that you have control of, put the blackhole route there.
Mark
Regular FW policies wouldn't block IPSec attempts since the destination is itself. But "local-in-policy" does.
Personally, I would be doing the blocking on the gateway router myself, if the FGT isn't it. Why bog down the FGT with bogus traffic?
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
Hi this massages repeat every night for 2 to 5 AM
I have a few site to site Tunnels but also a remote access VPN
I'm don't know dose IPs,
what is the best way to block dose address?
toshiesumi wrote:Regular FW policies wouldn't block IPSec attempts since the destination is itself. But "local-in-policy" does.
Is this the correct Setup to block IPsec attempts?
config firewall local-in-policy edit <policy_number> set intf Wan1 set srcaddr Can I use Address Group to setup Blacklist group set dstaddr Wan1 IP set action {accept | deny} set service IPsec set schedule Always endSelect Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1710 | |
1093 | |
752 | |
446 | |
231 |
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.
Copyright 2024 Fortinet, Inc. All Rights Reserved.