Bug #4325

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

Added by Adam Hirsch over 5 years ago. Updated over 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


Steps to reproduce:

  1. Firewall -> Traffic Shaper -> Limiter
  2. Create new limiter with a memorable bandwidth. (In my example, 300 Gb/s)
  3. Save, apply changes
  4. In the CLI:
    ipfw pipe show
  5. 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

Associated revisions

Revision f95cdbea (diff)
Added by Chris Buechler over 4 years ago

Gbps isn't interpreted correctly by ipfw for limiters, remove the option. Ticket #4325


#1 Updated by Phillip Davis over 5 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

#2 Updated by Chris Buechler about 5 years ago

  • Status changed from New to Confirmed
  • Assignee set to Ermal Luçi
  • Affected Architecture added
  • Affected Architecture deleted (i386)

#3 Updated by Chris Buechler over 4 years ago

  • Status changed from Confirmed to Resolved
  • Assignee deleted (Ermal Luçi)
  • Target version set to 2.3
  • Affected Version changed from 2.2 to All

removed the Gb option

Also available in: Atom PDF