Bug #4325: GUI for limiter rules turns Gb/s into b/s - pfSense - pfSense bugtracker

Actions

Copy link

Bug #4325

closed

GUI for limiter rules turns Gb/s into b/s

Added by Adam Hirsch about 9 years ago. Updated about 8 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Traffic Shaper (Limiters)

Target version:

2.3

Start date:

01/27/2015

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

All

Affected Architecture:

Description

Steps to reproduce:

Firewall -> Traffic Shaper -> Limiter
Create new limiter with a memorable bandwidth. (In my example, 300 Gb/s)
Save, apply changes
In the CLI:
```
ipfw pipe show
```

Note that the bandwidth for the limiter is 300 b/s

00003: 300.000 bit/s     0 ms burst 0
q131075  50 sl. 0 flows (1 buckets) sched 65539 weight 0 lmax 0 pri 0 droptail
 sched 65539 type FIFO flags 0x0 0 buckets 0 active

Actions

Copy link

Updated by Phillip Davis about 9 years ago

When I do that, /tmp/rules.limiter has the expected stuff like:
pipe 1 config bw 4Gb

But as you say, Diagnostics->LimiterInfo displays it as only bit/s

When I use some Kb/s or Mb/s limiter, my download comes at the expected pace.
When I change to some Gb/s I get a dribble. I even tried 3000 Gb/s, which displays 3000 b/s in Limiter Info. My download manager reports figures very close to 300 Bytes/sec, which is I guess about 3000 bits/sec!

So /tmp/rules.limiter is written OK, but it seems that /sbin/ipfw is not understanding the Gb unit of measure and is just interpreting it as bits/sec

Actions

Copy link