- Products
- Learn
- Local User Groups
- Partners
- More
Quantum Spark Management Unleashed!
Check Point Named Leader
2025 Gartner® Magic Quadrant™ for Hybrid Mesh Firewall
HTTPS Inspection
Help us to understand your needs better
CheckMates Go:
SharePoint CVEs and More!
So, as it became evident starting from R80.40 USFW is now automagically enabled on some appliances even if they have lower than 40 amount of CPU cores - 4,8,16. Also, few people reported increased amount of CPU usage on such systems.
Bug or a feature ?
Share your thoughts, expectations, observations, curses, etc...
On 3.10 kernel (R80.40) UMFW is enabled by default.
I can confirm similar behavior on some firewalls. What surprises me is that the basic process is already producing about 10%-20% CPU load (without firewall traffic).
In UMFW the fw instances are threads of the fwk0_dev_0 so by default the top shows all the threads cpu utilization under the main thread. Top has the option to present the utilization per thread as well.
A small calculation sample for the utilization of process fwk0_dev_0:
max_CoreXL_number max_CoreXL_number
fwk0_dev_0 = ∑ fwk0_x + ∑ fwk0_dev_x + fwk0_kissd + fwk0_hp
x=0 x=0
Thread from process fwk0_dev_0:
- fwk0_X -> fw instance thread that takes care for the packet processing
- fwk0_dev_X -> the thread that takes care for communication between fw instances and other CP daemons
- fwk0_kissd -> legacy Kernel Infrastructure (obsolete)
- fwk0_hp -> (high priority) cluster thread
More read here:
R80.x - Performance Tuning Tip – User Mode Firewall vs. Kernel Mode Firewall
Let me be the first to report...
Mine is 4-core 3600 appliance. It came from CheckPoint with R80.30 and USFW was enabled by default. Recently I upgrade it to R80.40. Because most of our users are working from home now load on appliance is really low so can't say about CPU usage...
On 3.10 kernel (R80.40) UMFW is enabled by default.
I can confirm similar behavior on some firewalls. What surprises me is that the basic process is already producing about 10%-20% CPU load (without firewall traffic).
In UMFW the fw instances are threads of the fwk0_dev_0 so by default the top shows all the threads cpu utilization under the main thread. Top has the option to present the utilization per thread as well.
A small calculation sample for the utilization of process fwk0_dev_0:
max_CoreXL_number max_CoreXL_number
fwk0_dev_0 = ∑ fwk0_x + ∑ fwk0_dev_x + fwk0_kissd + fwk0_hp
x=0 x=0
Thread from process fwk0_dev_0:
- fwk0_X -> fw instance thread that takes care for the packet processing
- fwk0_dev_X -> the thread that takes care for communication between fw instances and other CP daemons
- fwk0_kissd -> legacy Kernel Infrastructure (obsolete)
- fwk0_hp -> (high priority) cluster thread
More read here:
R80.x - Performance Tuning Tip – User Mode Firewall vs. Kernel Mode Firewall
I just wanted to share my quick experience with USFW, as this is something to be aware of since it is automatically enabled in R80.40.
If you have high F2F traffic, be careful enabling USFW. We were running around 40% F2F traffic and probably an average CPU load of around 60% during peak usage. We got a new firewall that had USFW enabled by default. When we hit peak loads, our firewall started dropping at least 1/3 of the packets, if not more. This happened even though our overall CPU usage was lower. As soon as we disabled USFW, everything worked great. So make sure you fix any F2F traffic issues before enabling USFW and disable USFW on any new firewalls if needed. Also note that even though TAC confirmed the process for us to disable it, it kept turning back on after reboot and required TAC to edit some files for us.
We eventually figured out our high F2F issue and we should be able to run USFW just fine now.
GAIA version/ Kernel/ Cores | Firewall mode | Check |
R80.30 kernel 3.10 more then 35* cores | UMFW is enabled | checked on HP DL 380 G10 2 * Platinum 8180MProcessor 28 cores = 56 cores |
R80.30 kernel 3.10 less then 35* cores | KMFW is enabled | checked on HP DL 380 G10 1 * Platinum 8180MProcessor 28 cores |
R80.30 kernel 2.6 | KMFW is enabled | checked on VMWare with 30 cores and with 46 cores |
R80.40 (default 3.10 kernel) | UMFW is enabled by default | checked on VMWare with 4 cores |
I came across this article that gives a clue why is USFW efficient even on small amount of CPU cores:
https://netdevconf.info/2.1/papers/netdev.pdf
Btw, cpview calls this "zeco" 😀
Let me share my experience..
I have customers with 6200 appliances running R80.30 and USFW was enabled by default..
On R80.30 with 3.10 kernel it is enabled by default.
In preparation for release of the R80.40 addendum for my book, I had an very enlightening discussion with a member of R&D about USFW. I will alert him to this thread privately so he can correct anything that I missed.
Whether USFW will be enabled by default is actually much more dependent on specific hardware/appliance type than Gaia kernel or number of cores. So assuming at least version R80.30 here we go...
This criteria for whether USFW is enabled by default seems to have changed over time, which may explain some early 16000's that don't have USFW enabled by default that were mentioned in this thread.
The explanation that USFW depends mostly on hardware type (I assume here processor family) and at the same time is enabled on any virtualized environment kind of contradicts by itself.
I think USFW actually depends mostly on whether hardware architecture is suitable for running efficiently hypervisor or not.
Otherwise, our 3600 seems to cope very well with USFW on R80.40.
Hi all,
I understand there is a bit of confusion regarding USFW status on R80.30 3.10 and R80.40.
I will make sure to post in the upcoming days a clear information about this.
In the meantime i would like to clarify regarding the question above
R80.40 is not USFW by default, USFW status is depend on
I'm currently collecting all the USFW questions and will answer all of then in a single post
Thanks,
Shai Shabat - Framework group manager ,CheckPoint
This USFW is really cool!
I am on R80.40 and today one of the firewall processes went nuts on policy install and crashed. It was quickly restarted and there was no reboot, only minor loss of connectivity to here and there.
I am two Takes behind and I know at least one of them fixes something like that but that's not the point.
@shais wrote:R80.40 is not USFW by default, USFW status is depend on
- Hardware type, for example 6900 appliance or VMs will run in USFW by default (since R80.30 3.10)
- Number of cores - Kernel is limited to 40 instances, above can only run in USFW
Just an FYI... I installed R80.40 on a 4400 and 4800 and USFW turned on by default. I noticed my CPU load was twice as high as on R80.40 as it was on R80.30. I had a ticket with CP here recently on an unrelated issue and the tech noticed USFW was on and disabled it. When they did that, my CPU load dropped by 50% immediately.
There is clearly something wrong in the code in R80.40 install that is causing it to turn on when it shouldn't be. I installed R80.40 using the latest BLINK image on March 20th, 2020.
Hi,
I'm sorry to hear that USFW resulted in CPU spike on your system, may i please get the ticket you had with support? i would like to see the information collected.
As for the 4400/4800 appliance running by default in USFW - I will verify this in our lab as this appliance should not run in USFW
6-0001980814
All, there is a new SK available for the matter:
Linking thread with answers from CheckPoint:
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 | |
5 |
Fri 12 Sep 2025 @ 10:00 AM (CEST)
CheckMates Live Netherlands - Sessie 38: Harmony Email & CollaborationTue 16 Sep 2025 @ 02:00 PM (EDT)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - AmericasWed 17 Sep 2025 @ 04:00 PM (AEST)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - APACWed 17 Sep 2025 @ 03:00 PM (CEST)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - EMEAThu 18 Sep 2025 @ 03:00 PM (CEST)
Bridge the Unmanaged Device Gap with Enterprise Browser - EMEAFri 12 Sep 2025 @ 10:00 AM (CEST)
CheckMates Live Netherlands - Sessie 38: Harmony Email & CollaborationTue 16 Sep 2025 @ 02:00 PM (EDT)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - AmericasWed 17 Sep 2025 @ 04:00 PM (AEST)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - APACWed 17 Sep 2025 @ 03:00 PM (CEST)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - EMEAThu 18 Sep 2025 @ 03:00 PM (CEST)
Bridge the Unmanaged Device Gap with Enterprise Browser - EMEAAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY