Project

General

Profile

Bug #10838

mask options didn't apply to the sched limiter

Added by Viktor Gurov 8 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Traffic Shaper (Limiters)
Target version:
Start date:
08/18/2020
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.5-p1
Affected Architecture:
Release Notes:
Default

Description

Using the GUI, the mask options didn't apply to the sched limiter.

from ipfw man:

The SCHED_MASK is used to assign flows to one or more scheduler instances, one for each value of the packet's 5-tuple after applying SCHED_MASK.
As an example, using src ip 0xffffff00 creates one instance for each / 24 destination subnet.

The FLOW_MASK, together with the SCHED_MASK, is used to split packets
into flows.As an example, using src ip 0x000000ff together with the
previous SCHED_MASK makes a flow for each individual source address.
Inturn, flows for each / 24 subnet will be sent to the same scheduler instance.

before patch:

sched 7 config pipe 7 type fq_codel target 5ms interval 100ms quantum 300 limit 20480 flows 65535 noecn

after patch:

sched 7 config pipe 7 mask dst-ip6 /128 dst-ip 0xffffffff type fq_codel target 5ms interval 100ms quantum 300 limit 20480 flows 65535 noecn

History

#2 Updated by Jim Pingle 8 months ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0

#3 Updated by Renato Botelho 7 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged. Thanks!

#4 Updated by Steve Beaver 6 months ago

  • Status changed from Feedback to Resolved
  • Assignee changed from Renato Botelho to Viktor Gurov

#5 Updated by Jim Pingle 5 months ago

  • Category changed from Traffic Shaper (ALTQ) to Traffic Shaper (Limiters)

Also available in: Atom PDF