r/fortinet • • Apr 30 '26

New Fortinet Product

Post image
426 Upvotes

Version 1.0 just released šŸ˜‚


r/fortinet • • Jul 12 '25

So my adventure with fortinet has finally started

Post image
343 Upvotes

left 3 boxes are for my homelab.. ditching tplink omada equipment for: fortigate 50 fortiswitch-148E FAP-221E-E right side project for small business with multiple branch offices that currently uses some mikrotik stuff: 1x fortigate 70g for main office 3x fortigate 40f for remote locations 2x fortiswitch 124F-POE 3x FAP-221-E

I can't wait to get started. Wish me luck šŸ˜‰


r/fortinet • • Oct 23 '26

Other / General Fortinet Happy #FirewallFriday 🫠

Post image
313 Upvotes

r/fortinet • • Aug 22 '26

Question ā“ Best environment for a FortiGate?

Post image
312 Upvotes

r/fortinet • • Mar 20 '26

FortiGraveyard

Post image
275 Upvotes

r/fortinet • • Aug 12 '26

FortiLego

Post image
260 Upvotes

Running a mini tech convention and Fortinet sent us these. Pretty neat!


r/fortinet • • May 19 '21

My FortiGate in Transparent Mode šŸ˜›

Post image
256 Upvotes

r/fortinet • • Apr 13 '26 Bravo

FortiNothing

Thumbnail
gallery
251 Upvotes

Just found in the office, nothing inside. Whats interesting it has all the certifications on the box.


r/fortinet • • Apr 05 '26

Moving to a new house, look what I found while packing up - When life was easier back then..

Post image
241 Upvotes

r/fortinet • • May 14 '22

Thought you might like the cake we made for my bosses birthday

Post image
227 Upvotes

r/fortinet • • Mar 19 '24

Anyone use Fortinet at home?

Thumbnail
gallery
223 Upvotes

Started following this group when I wanted to setup a Fortinet network at home. I’d assume some also use at home but curious how many?

I’m currently using a 60f, with a 224E as my ā€œcoreā€ switch with a 108D on each floor feeding five 231G’s and a 234F outside.

I’m really pleased with the results, my wife definitely likes the device level control and NGFW compatibilities our old soho stuff just didn’t do as well.

While overkill, I’ve enjoyed the learning curve and the stealth support this group has given, so thank you! I have some but fairly limited networking knowledge.


r/fortinet • • Mar 19 '21

Well seeing one of these as the console cable in the Fortigate box made me way happier than it probably should have.

Post image
213 Upvotes

r/fortinet • • Sep 30 '21

All of a sudden we are getting SSL Certificate expired while using deep packet inspection today

204 Upvotes

It seems like the errors are all from R3 authority which from what I am seeing is related to LetsEncrypt. The odd thing is that it says the certificate is expired, but the error message shows that the certificates are within the correct time. This just all of a sudden started happening. Websites like amazon and google have no issues. Anyone else having this issue?

Final Update:

Fortinet KB Article: https://kb.fortinet.com/kb/documentLink.do?externalID=FD53305

Fortinet response: https://www.fortinet.com/blog/psirt-blogs/fortinet-and-expiring-lets-encrypt-certificates

Update your certificate bundle following /u/niffur00 instructions

A root certificate that is used by LetsEncrypt has expired https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

There are workarounds, but please be aware that your security posture may be reduced. It seems as if the old KB for the AddTrust External CA updated KB article has the same workarounds that others are suggesting in this post. https://kb.fortinet.com/kb/documentLink.do?externalID=FD49028. I don’t know what Fortinet is doing, but they updated this KB with info regarding DST Root CA X3, yet now they have removed all references to it. I believe the information is still relevant.

If you do choose to allow invalid certificates, may I suggest that instead of choosing to allow All, that you instead use the ā€œCustomā€ option and choose ā€œTrust and Allowā€ for expired certificates (if that is an option on your version).

Expect Fortinet to release a new certificate bundle, as /u/niffur00 suggests and the KB article describes, please be on the lookout for this new bundle and update when ready. My current certificate bundle reads version 1.00027. Apparently Fortinet has released a new certificate bundle version 1.00028. I am unable to confirm if this works, so please post your results.


r/fortinet • • Aug 16 '26

Question ā“ Got this From Used Market !

Post image
189 Upvotes

I know nothing about firewalls, and I bought this to learn!


r/fortinet • • Jun 30 '24

I have started a new job that uses Palo Alto instead of Fortigates. Boy do I miss Fortigates! Much simpler times! This sub has helped me no end in the past so thank you it seems like goodbye at least for now!

Post image
165 Upvotes

r/fortinet • • Oct 21 '26

Other / General Fortinet Fortinet Releases Security Hardening Release for Multiple Products

Thumbnail fortinet.com
159 Upvotes

Get ready to patch


r/fortinet • • Jul 03 '25 This

Guide ā­ļø The Truth About Why DARRP Sucks and How to Make DARRP Actually Useful

153 Upvotes

It's widely experienced by FortiAP admins for many years that Fortinet's Distributed Automatic Radio Resource Provisioning (DARRP) algorithm is so awful that it's not even worth trying to use it, so we just resort to static channel planning instead. The default DARRP settings will frequently put adjacent FortiAPs on the exact same channel, and CCI is the WORST possible thing for WLAN health, and SHOULD be the most preventable. I myself have experienced this, and static channel planning was fine for small WLANs. But as we get involved in larger and larger deployments, in more dynamic environments, this is no longer tenable. So I decided to dive in deeply to DARRP, understand how it works, why it doesn't work well (and specifically why it puts adjacent FortiAPs on the exact same channel when there are clearly many better choices to pick from), and what can be done to make it work better.

What I discovered shocked me deeply, and I think it will be extremely surprising to many of you as well. I've shown this to numerous other engineers, and no one seemed to know these details. So I want to share this with the community and get your feedback. If the community tries what I will recommend in this post and has dramatically improved results, we will have a viable way to make DARRP work, and can ask Fortinet for improvements to the default values in future versions.

The first thing to highlight is that the default DARRP schedule is once a day, at 1am, for 30 minutes, which can maybe help work around persistent interference sources, like CCI from other WLANs with APs with unchanging radio settings. But this schedule is completely useless for dynamic conditions, like fluctuating client usage, human bodies introducing extra attenuation, sources of non-WiFi interference (e.g. 2.4 Ghz microwave ovens that run at lunch time, or 5 Ghz motion detectors for security systems that spike their Tx power only when humans are moving about, etc.) etc. etc.

The official docs article, Configuring Distributed Radio Resource Provisioning, gives the rationale for this schedule is given as follows:

Ā "During DARRP optimization, the FortiGate may change the operating channels of managed FortiAP units and cause connected Wi-Fi clients to experience intermittent service disruption. Therefore, we do not recommend running DARRP optimization too frequently to avoid disrupting clients with unnecessary channel changes. The default value of darrp-optimize is 86400 seconds (24 hours), which means DARRP optimization is run only once per day. Additionally, we recommend scheduling DARRP optimization to avoid peak periods of heavy wireless traffic. The default schedule, default-darrp-optimize, runs DARRP optimization during a low-traffic period of 1:00am to 1:30am every day."

In my opinion, this is misguided, because of the reasons I mentioned above. Sure, you don't want all your APs changing channels every 5 minutes, but they need to change much more frequently than just once a day, in the middle of the night when there are no human users around. Furthermore, because all current-gen FortiAPs are DFS certified, we know they have to support 802.11h, which includes Channel Switch Announcements (CSAs), to let the clients to know that a channel switch is coming in N beacon intervals, and to either roam to another AP or follow the channel switch on the same AP. Because 802.11h was ratified in 2013, it's WIDELY supported on client devices in 2025, and it works quite well. You combine this with 802.11r fast-roaming, and most clients should do just fine. Before publishing this, I did a bunch of CSA tests on my home lab, and most devices saw no packet loss on a continual ping, just a small bit of extra latency (maybe 30-40ms or so). One of my cheaper Android tablets lost 1 ping. In my opinion, it's much more preferable to have some client lose, at worst, a ping or two, during a DARRP-induced channel change than to be continuously be experiencing poor Wi-Fi quality all day long.

And sure, way back in the day (E-gen and older) we didn't have dedicated scanning radios, so it wasn't good to burn radio airtime on DARRP listening, especially during peak utilization times, when the radio needs to be busy servicing clients. But we've had dedicated scanning radios on all FortiAPs since F-Gen back in like 2019. With a dedicated scanning radio, you can do DARRP listening as much as you want, any time you want, without affecting the clients.

So I would definitely recommend having a more frequent DARRP schedule, at least twice a day, DURING times that the human users are actually using the WLAN. I'd say even once an hour is not too frequent. As far as clock cycles are concerned, know that the algorithm is running on the AP, rather than the FortiGate, so it really comes down to the AP's compute and RAM, so that is what we have to account for in we want to process DARRP at peak utilization times. For older/weaker APs like, E-gen or even some F-gen, they didn't have a lot of compute & RAM to work with, and DARRP was pretty resource intensive, hence why you might not want them to not do this calculation during the day, when they're busy serving clients. But for G-gen, and ESPECIALLY for K-gen, we've got way more resources to work with. Shouldn't be a problem, but this can be monitored when first rolling it out to groups of APs.

HOWEVER, all that being said, it's still really important to understand how the DARRP algorithm currently works, because it's not what you think! From the article Understanding Distributed Radio Resource Provisioning, we see the following:

In other words, the FortiAP DARRP algorithm, at least with the default parameters, is not trying to pick THE BEST channel. It's just trying to find at least one channel that ISN'T HORRIBLE, and if there's more than one, well, just YOLO random it. And if you've got two FortiAPs in your WLAN, and say you're using a 40-MHz wide channel plan in the 5 GHz band, well now you've got a 1-in-14 chance that both APs randomly pick the same channel. But if you've got many FortiAPs in your WLAN with this 40 MHz channel plan, now you've got the Birthday Paradox probability of two neighboring APs randomly picking the same channel!Ā 

Now, obviously with APs spaced out, you usually shouldn't have 10+ overlapping APs, but it's not at all uncommon to have 3-to-6 APs with some overlap. So that means you'll have between a 21% chance and a 71% chance of two neighboring FortiAPs picking the same channel. And it will get even worse if any channels have to be excluded because they're above the thresholds, or if they're DFS that must get excluded due to weather/radar being nearby, etc. And THIS is why so many people have observed DARRP making what seems like a poor choice, where it picks the exact same channel for two AP right next to each other. It's because it's just saying "of the channels that aren't HORRIBLE, pick one at random" -- and there's not that many choices to pick from, so there's a very high probability of at least two neighboring APs ending up on the same channel.Ā 

Personally, I'd MUCH rather rely on the "Sub-phase 2" part of the algorithm, which is actually trying to find an optimal channel, rather than just randomly picking from the pool of NOT-HORRIBLE channels. In order to reliably use the "Sub-phase 2" part of the DARRP algorithm, you have to set your threshold values SO LOW in "Sub-phase 1" that ALL the channel get excluded, or else the FortiAPs never even get to Sub-phase 2 evaluation. This seems extremely counter intuitive that you would want to configure DARRP to exclude ALL channels, but we're only excluding all of them from the Phase 1 evaluation, which will assign not-horrible-channels at random.

N.B. that this Sub-Phase 2 score is like golf: lowest score wins. So if you need to adjust these weights, understand that adjusting them upwards will decrease the chance of a given channel getting selected as t he best channel. So far, I have found that the default weightings in Sub-Phase 2 work well enough for most deployments.

Next, there's also the "Channel Quality Monitoring" phase as well, which help help detect issues with changing channel conditions over time by monitoring for Tx and Rx errors after a selection has been made. But the default for threshold-rx-errors is 50%! That's way too high to be tolerable, IMO. 15% would be more reasonable. The threshold for Tx retransmits is a more sensible 30%, but I think 15% would be better here as well. Also, don't ask me why the Rx threshold range is 0-100, while the Tx threshold range is 0-1000... I guess to just give you a few more sig-digits for more granular Tx threshold control? Either way, just keep this in mind when changing the values. They're both percentages, but Rx has 3 sig-figs and Tx has 4 sig-figs.

So, all that being said, how should you configure DARRP!? In my opinion, the below are general best practices that I am seeing great results with so far.

# Run DARRP every hour, 24/7/365, because we have dedicated scanning radios on F-Gen and newer
config wireless-controller setting
    set darrp-optimize 3600
    set darrp-optimize-schedules "always"
end

# I like to create a new arrp profile rather than editing the default
config wireless-controller arrp-profile
    edit "best-practice_arrp"
        set comment "Eliminate all channels from phase1 algorithm and rely only on phase2 weighting defaults"
        set selection-period 600
        set threshold-ap 1
        set threshold-noise-floor "-95"
        set threshold-channel-load 1
        set threshold-spectral-rssi "-95"
        set threshold-tx-retries 150
        set threshold-rx-errors 15
    next
end

# Then don't forget to assign this new ARRP profile to your FortiAP profiles for each radio
config wireless-controller wtp-profile
    edit "<profile-name>"
        config radio-1
            set darrp enable
            set arrp-profile best-practice_arrp
        end
        config radio-2
            set darrp enable
            set arrp-profile best-practice_arrp
        end
        config radio-3
            set darrp enable
            set arrp-profile best-practice_arrp
        end
    next
end

N.b. I'm still using the default values for weights on the DARRP profile; you might decide to edit these based on particulars of your environment (like maybe you might want to de-emphasize DFS channels if you are near radar towers, etc). N.B. also that I set the selection-period to 10 minutes, and left the monitor period at 5 minutes (so the entire DARRP process should take about 15 minutes, and will run once an hour).

Here's what the DARRP profile looks like if I do a "show full-configuration" such that it shows even the default values.

config wireless-controller arrp-profile
    edit "best-practice_arrp"
        set comment "Eliminate all channels from phase1 algorithm and rely only on phase2 weighting"
        set selection-period 600
        set monitor-period 300
        set weight-managed-ap 50
        set weight-rogue-ap 10
        set weight-noise-floor 40
        set weight-channel-load 20
        set weight-spectral-rssi 40
        set weight-weather-channel 0
        set weight-dfs-channel 0
        set threshold-ap 1
        set threshold-noise-floor "-95"
        set threshold-channel-load 1
        set threshold-spectral-rssi "-95"
        set threshold-tx-retries 150
        set threshold-rx-errors 30
        set include-weather-channel enable
        set include-dfs-channel enable
        set override-darrp-optimize disable
    next
end

I've been running this on the environments I manage for a while now and am seeing great results. At no point am I seeing adjacent FortiAPs select the same channel. Also, I am not noticing any problems with client interruption when FortiAPs decide they should change channels; CSAs seem to be working as expected.

Please give this a try in your environment and let us all know how your results turn out. Remember: the goal is that we have DARRP that actually works reasonably well. If this configuration works well for the community, we can take it back to Fortinet to make this MUCH easier and much better in future versions.

Thank you!!

Ā ______

Update: Some history on the DARRP algorithm, as best I can tell from looking at historical release notes.

- DARRP appears to have been first introduced somewhere in FortiOS 5.4.x (2016-06-09 at the earliest)
- In this early version, you could not control any of the DARRP parameters, let alone have multiple DARRP profiles. All you could do was either enable it or disable, and if it was enabled, you could control when it runs. Furthermore, nothing in the documentation seems to describe anything about how the DARRP algorithm actually works.
- Looking at the CLI references for FortiOS versions 5.4 through 6.2, there does not appear to be any ability to control DARRP parameters. As far as we can tell from the outside, no changes were made to DARRP during this period of time.
- In FortiOS 6.4.2 (released 2020-07-30), we see for the first time the ability to control the parameters of DARRP via CLI, and to have multiple DARRP profiles:
- There's still no clear documentation at this time about how the DARRP algorithm actually works under the hood, but the presence of those CLI parameters gives us some basic hints for the first time.
- It's not until FortiOS 7.0.4 (released 2022-02-15) that we first see documentation about HOW the DARRP algorithm actually works (which is the exact same article that I based this OP on, and appears unchanged until 7.6.3).
- In the "What's New" for this 7.0.4, there's also a generic statement of "Improves DARRP channel selection."

So as best I can tell...
- Before 2016: Pre-DARRP era
- 2016 to 2020: Proto-DARRP era (on or off, no configurability, total black box)
- 2020 to 2022: Paleo-DARRP era (configurability, some clues in CLI reference)
- 2022 to Present: Classical DARRP era (configurability, basic explanation in documentation)

The reason for documenting this history is to try to better understand why some of the assumptions were made based on when they were made.


r/fortinet • • Jan 17 '26

Well, let the fun begin

Post image
144 Upvotes

r/fortinet • • Nov 28 '23

Collection of Fortigate automation stitches

143 Upvotes

Good day everyone, hope you all are doing well.

I created a Github repo where will collect scripts, tools, anything that helps in daily work with Fortinet products.

So far put a collection of Fortigate automation stitches (21) you may find helpful. Next is the collection of FAZ Incident Handlers.

I hope this to become a community effort, so if you have found a tool or implemented some automation, please share with me via email and I will update the repo.

The repo: https://github.com/yuriskinfo/Fortinet-tools

So far automation stitches:

Send email on admin-level user being created/added

Back up configuration when changed to external server via SFTP

Back up configuration daily to external server via SFTP

Local TLS Certificate is about to expire email alert

Send alert on Fortigate configuration changed by administrator without details

Send alert on Fortigate configuration changed by administrator with details

email alert on Fortigate entering conserve mode

Send email alert on FortiGuard servers becoming unreachable and attach debug output (with VDOMs)

Send email alert on FortiGuard servers becoming unreachable and attach debug output (without VDOMs)

Send an email alert when CPU usage reaches the threshold

Any of Fortigate interfaces goes down, send an email alert

Any of Fortigate interfaces goes up, send an email alert

Fortigate undergoing a reboot email alert

Restart IPS process daily

Restart WAD process daily

Schedule daily reboot of Fortigate

Schedule reboot of Fortigate one time

Schedule weekly reboot of Fortigate

When only a given interface goes down, send an email alert

SSL VPN tunnel up with condition of remote IP address

Thanks for reading.

EDIT: Wow, thanks a lot for such a positive feedback! I promise to try and implement all suggestions given by you here, in email, and on LinkedIn and update the repo accordingly, as well as try and find answers to your questions.


r/fortinet • • May 09 '26

News 🚨 FortiAP with display

Post image
142 Upvotes

I saw this AP on a LinkedIn post, the FAP-231KD, with a built in display apparently to display ads and for face recognition. Does anyone know anything about this model? Google returned nothing.


r/fortinet • • Apr 28 '20

Fortinet | Free Advanced Training for Security Professionals | Wait!, Whut????

136 Upvotes

Heads up Fortinet community, it seems #Fortinet opened up their NSE course work to all. See below

Free Advanced Training for Security Professionals

The no-cost curriculum includes all courses to support security-driven networking, dynamic cloud security, AI-driven security operations and zero-trust network access. Completion of these courses will help cybersecurity professionals defend their networks against the widest range of ever changing threats.

NSE 4

NSE 5

NSE 6

NSE 7

Other


r/fortinet • • May 27 '25

News 🚨 FortiOS v7.4.8 has been released

Thumbnail docs.fortinet.com
135 Upvotes

Please use this thread for discussion.


r/fortinet • • Jan 22 '26

IPSec VPNs not forwarding traffic unless npu-offloading disabled after upgrade to 7.4.10

134 Upvotes

Hello,

FYI

I think we drew first blood with the latest patch on 7.4. A week ago we scheduled upgrade to the latest 7.4 after consulting the release notes. Nothing in release notes that could be an issue for us. We were in safe haven with all firewall clusters (400E, 1101E and 101F) on 7.2.12 but as we are migrating to new EMS/FCT/ZTNA in a few months we wanted to upgrade the firewalls in advance.

Yesterday our MSP did upgrade to 7.4.10. All went well, everything was up and running under an hour. After the upgrade I tested the usual employee facing services and then called it a day.

This morning I got call from my manager that he got at least 5 calls from random employees and external vendors that their VPN is not working (FortiClient 7.2.12) and various S2S tunnels (mix of IKEv1 and 2)

After initial troubleshooting we have found out that the tunnels will connect to fortigate (400E) but no traffic is forwarded anywhere, blank packet capture and debug flow. Everything else looked exactly how it should, tunnels were negotiated, all phases up, but no traffic coming from either end. The only dialup VPN that was working was newly set up tunnel with all the IKEv2 goodness (IKEv2, AES256GCM, DH Group 20...etc).

Then after som testing and diagnosing the problem we didnt find anything out of ordinary. We forced the failover to secondary cluster node and it started working again, for maybe 15 minutes and the issues came back. After this we have got an echo from another vendor that we could try to disable npu-offload on the specific tunnels. So we tried that and just after we changed the config on all problematic tunnels it started to run again.

config vpn ipsec phase1-interface

edit ExampleName

set npu-offload disable

next

These problems were present only on our 400E. The other firewall that is terminating VPNs (101F) didnt had this problem occuring. The only reason as of why I have right now is that these firewalls have different ASICs (NP6 vs NP6XLite) and there is probably some bug in 7.4.10.

Ticket was opened on support and I am waiting on statement on what could have possibly happened.

UPDATE: I still dont have any answers from fortinet support but I figured out why two of our tunnels were working. The dialup one was using AES256GCM which according to docs the NP6 dont support so its automaticaly bypassing NPU offloading. The other one was S2S tunnel which is using supported ciphers but its in transport mode with GRE tunnel inside IPSec which is also not supported by NP6 and again, bypasses the NPU. So any IPSec traffic which entered the NPU after upgrade to 7.4.10 got lost and never left the ASIC.

UPDATE2: Support got back to us. From the initial looks it is some kind of undocumented bug on any NP6 based platform. Specificaly the issue is with anti-replay detection feature as the NP6 lacks some integrated packet‑ordering engine found in NP6XLite/NP7, which has been implicated in several 7.4.x IPsec issues where disabling offload or anti‑replay is a workaround.

Didnt test this myself but at least you know where to look and what to test.


r/fortinet • • Oct 22 '26

Other / General Fortinet FortiOS 7.4.13 images are being removed from support

Post image
133 Upvotes

While I am in progress of upgrading and downloading other images I just noticed images are disappearing from website, no issues on 80F right now but anyone has some clues? There were all models available before!

update: images are back with the same checksum