Project

General

Profile

Actions

Bug #6553

closed

net.inet.ip.dummynet.pipe_slot_limit can't be set manually, should be automatic

Added by Chris Buechler over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Category:
Traffic Shaper (Limiters)
Target version:
Start date:
06/28/2016
Due date:
% Done:

0%

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

Description

net.inet.ip.dummynet.pipe_slot_limit only exists after dummynet is kldloaded, which comes after the sysctls are applied. That order's the same in rc.bootup as it's always been, and that did apply cleanly from tunables in past versions, but something's changed where dummynet isn't loaded where it was before.

Regardless it shouldn't be necessary to manually set that, we can set it automatically to the appropriate maximum value.

Actions #1

Updated by Chris Buechler over 5 years ago

  • Status changed from Confirmed to Feedback

fix pushed

Actions #2

Updated by Chris Buechler over 5 years ago

  • Status changed from Feedback to Resolved

works

Actions #3

Updated by Chris Buechler over 5 years ago

  • Target version changed from 2.3.1-p6 to 2.3.2
Actions

Also available in: Atom PDF