misc/156838: "ipfw pipe show" shows wrong dummynet pipe delay when hz is not 1000

Ji Li lijimlee at gmail.com
Thu May 5 21:50:09 UTC 2011


>Number:         156838
>Category:       misc
>Synopsis:       "ipfw pipe show" shows wrong dummynet pipe delay when hz is not 1000
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 05 21:50:09 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Ji Li
>Release:        8.2 Rel, 8 stable and head
>Organization:
>Environment:
FreeBSD example.example.com 8.2-STABLE FreeBSD 8.2-STABLE #0 r221483: Thu May  5 07:19:30 PDT 2011     example at example.example.com:/usr/home/example/src/freebsd-8-stable/sys/amd64/compile/GENERIC  amd64

>Description:
When one uses "ipfw pipe config" to configure delay for a dummynet pipe, dummynet translates the delay (in ms) to ticks and saves it in its data structure. When one uses "ipfw pipe show" expects the delay shown in ms, dummynet however returns the delay in ticks. When kern.hz is 1000, it is fine, but if hz is not 1000, the delay shown is confusing. 

The problem may exist since 8.1 rel. I checked 7.2 rel and 8.0 rel, dummynet does convert delay back to ms, but that conversion seems missing since dummyent was re-written.
>How-To-Repeat:
1. On FreeBSD 8.2 or 8 stable, set "kern.hz=100" in /boot/loader.conf. 
2. Load ipfw.ko and dummynet.ko
3. Then create a pipe and config the delay to 100, then run "ipfw pipe show", you will see the delay shown is "10 ms", but actual pipe delay is 100ms.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list