- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
60E - Block traffic coming into firewall itself
I am getting hammered by a particular IP address on the WAN interface trying to brute force IPsec VPN (UDP port 500). How do I block traffic inbound to the device itself? I tried adding an IPv4 policy item with source & destination interface of "WAN1", a source address of the offending address, and a destination address of all. This did not work.
Cisco calls this the "control plane" traffic, which can be filtered just like regular interface access lists. Is this possible to do with Fortinet?
OS 6.0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try this as starting Point https://forum.fortinet.com/tm.aspx?m=177311&tree=true
________________________________________________________
--- NSE 4 ---
________________________________________________________
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wow. According to that post, there is currently not a way to block inbound UDP port 500 or 4500 on an IP basis. This is something Cisco has no problem doing......
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What?
config firewall local-in-policy
edit 1
set intf "wan1"
set srcaddr "VPN_origin_countries"
set dstaddr "all"
set action accept
set service "IKE"
set schedule "always"
next
end
works perfectly. Explained: only those IP addresses contained in address group "VPN_origin_countries" will be allowed to open IPsec negotiations.
Augment the service with a service group containing further protocols, like ESP and AH.
Finally, block "ALL" services from "any" address from accessing the FGT.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wil,
I wonder if you didn't read the whole post that Markus shared. This is the full thread: https://forum.fortinet.com/tm.aspx?m=177311
OP "tripley" said that he did what was suggested and it solved his problem, so I'm not sure why you got out of it that it was unfixable...
- Daniel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Note that your logs might not be showing the true picture for local-in and IKE. That is, you may get invalid logs showing that something made it past local-in when in fact it did not.
See bug #0515255 and https://forum.fortinet.com/tm.aspx?m=166107 for details.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
