Package: iproute2
Version: 4.9.0-1+deb9u1
Severity: minor
Dear Maintainer,
The documentation for the 'delay' option in the netem manual page indicates
that delay values are in units of 'ms', that is, milliseconds. Experimentation
suggests the actual units used by the option are microseconds.
* What led up to the situation?
I was repeatedly pinging the Raspbian host from a second machine, and
was observing "time" values which consistently less than one millisecond
(e.g., "0.847 ms").
* What exactly did you do (or not do) that was effective (or
ineffective)?
On the Raspbian host, I executed the following command:
sudo tc disc add dev eth0 root netem delay 1000
* What was the outcome of this action?
The "time" values reported by ping on the second machine changed to
being consistently between one and two milliseconds (e.g., "1.806 ms").
* What outcome did you expect instead?
The "time" values reported by ping on the second machine to be changed
instead to being consistently between 1000 and 1001 milliseconds (e.g.,
"1000.78 ms").
-- System Information:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.8 (stretch)
Release: 9.8
Codename: stretch
Architecture: armv6l
Kernel: Linux 4.14.98+
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages iproute2 depends on:
ii libc6 2.24-11+deb9u4
ii libdb5.3 5.3.28-12+deb9u1
ii libelf1 0.168-1
ii libmnl0 1.0.4-2
ii libselinux1 2.6-3
Versions of packages iproute2 recommends:
pn libatm1 <none>
ii libxtables12 1.6.0+snapshot20161117-6
Versions of packages iproute2 suggests:
pn iproute2-doc <none>
-- no debconf information
