Project

General

Profile

Actions

Bug #12661

closed
TM

Increase Maximum Allowable Bandwidth on Limiters

Bug #12661: Increase Maximum Allowable Bandwidth on Limiters

Added by Timo M over 4 years ago. Updated over 4 years ago.

Status:
Needs Patch
Priority:
Normal
Assignee:
-
Category:
Traffic Shaper (Limiters)
Target version:
-
Start date:
Due date:
% Done:

0%

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

Description

This is a continuation from the topic discussed on the forum here:

https://forum.netgate.com/topic/168866/maximum-bandwidth-value-for-limiters

It appears that the current maximum allowable bandwidth limit for setting on traffic shaping limiters is about 4294 Mbit/s or 2^32 bits/s. I'm not sure if this is just a limit on the value that the input field supports or an actual hard limit of the limiter framework. With multi-gigabit connections becoming more common it would be great if allowable bandwidth setting on limiters could be updated to support bandwidth values of 10 Gbit/s and beyond.


Related issues 1 (0 open1 closed)

Related to Bug #7979: Error setting limiter over 2GB/sResolvedLuiz Souza10/20/2017

Actions

KP Updated by Kris Phillips over 4 years ago Actions #1

I can confirm that setting a limiter of 5 gigabit produces the following error in the system logs:

/rc.filter_configure_sync: The command '/sbin/ipfw /tmp/rules.limiter' returned exit code '65', the output was 'Line 2: duplicate token, override bandwidth value! Line 2: bandwidth too large'

VG Updated by Viktor Gurov over 4 years ago Actions #2

current limiter maximums is 4Gb/s, see #7979

related FreeBSD issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194453

VG Updated by Viktor Gurov over 4 years ago Actions #3

  • Related to Bug #7979: Error setting limiter over 2GB/s added

JP Updated by Jim Pingle over 4 years ago Actions #4

  • Status changed from New to Needs Patch

Since this is blocked on an upstream limitation, there isn't anything we can do here at the moment. Once it's fixed in FreeBSD we'll pick it up naturally.

Actions

Also available in: Atom