Project

General

Profile

Actions
Copy link

Bug #10861

closed
JP JP

net.pf.request_maxcount value set in loader.conf not respected on latest snapshot

Bug #10861: net.pf.request_maxcount value set in loader.conf not respected on latest snapshot

Added by Jim Pingle about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Operating System
Target version:
2.5.0
Start date:
09/02/2020
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.5.0
Affected Architecture:

Description

The value of net.pf.request_maxcount is 65535 at boot on the latest 2.5.0 snapshot, despite a higher value being set in loader.conf:

: pkg info -x pfSense-2.5.0
pfSense-2.5.0.a.20200902.0050
pfSense-kernel-pfSense-2.5.0.a.20200902.0050

: sysctl net.pf.request_maxcount
net.pf.request_maxcount: 65535

: grep net.pf.request_maxcount /boot/loader.conf
net.pf.request_maxcount="2000000"

But the value can be set at runtime:

: sysctl net.pf.request_maxcount=2000000
net.pf.request_maxcount: 65535 -> 2000000

: sysctl net.pf.request_maxcount
net.pf.request_maxcount: 2000000

See #10254 for some related history

Actions
Copy link

Also available in: Atom