> Source: [sk166701](https://support.checkpoint.com/results/sk/sk166701)

# sk166701 - "psl_max_future_segments" parameter value set in fwkern.conf does not survive reboot in R80.30 User-Space Firewall

| Property | Value |
|----------|-------|
| Solution ID | sk166701 |
| Date Created | 2020-06-07 |
| Last Modified | 2020-06-08 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * After setting a global parameter ("psl_max_future_segments=8192") in *fwkern.conf*, the new parameter value did not survive a reboot, and stayed with the default value.
* The issue occurs only in USFW (User-Space Firewall) ( VSX or SGW with more than 40 cores).

## Cause

As a result of modules redesign in R80.30, several global parameters do not survive reboot, despite there appearance in *fwkern.conf*   

Installing this hotfix will ensure that these kernel parameters are kept post-reboot.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content