1. Debian Handbook
2. 10_network-infrastructure
3. Chinese (Simplified)
4. translate

<primary>traffic</primary><secondary>limitation</secondary>

<primary>流量</primary><secondary>限制</secondary>

Once a network interface is configured, setting up this traffic limitation is achieved by running <command>wondershaper <replaceable>interface</replaceable> <replaceable>download_rate</replaceable> <replaceable>upload_rate</replaceable></command>. The interface can be <literal>eth0</literal> or <literal>ppp0</literal> for example, and both rates are expressed in kilobits per second. The <command>wondershaper remove <replaceable>interface</replaceable></command> command disables traffic control on the specified interface.

配置网络接口后，运行 <command>wondershaper <replaceable>interface</replaceable> <replaceable>download_rate</replaceable> <replaceable>upload_rate</replaceable></command>命令，设置流量控制。可以是 <literal>eth0</literal> 或 <literal>ppp0</literal> 接口，两者的速度均以每秒千位为单位。<command>wondershaper remove <replaceable>interface</replaceable></command> 命令可以在特定接口停用流量控制。

For an Ethernet connection, this script is best called right after the interface is configured. This is done by adding <literal>up</literal> and <literal>down</literal> directives to the <filename>/etc/network/interfaces</filename> file allowing declared commands to be run, respectively, after the interface is configured and before it is deconfigured. For example:

Changes in the <filename>/etc/network/interfaces</filename> file

iface eth0 inet dhcp
up /sbin/wondershaper eth0 500 100
down /sbin/wondershaper remove eth0

<emphasis>GOING FURTHER</emphasis> Optimal configuration

The <filename>/usr/share/doc/wondershaper/README.Debian.gz</filename> file describes, in some detail, the configuration method recommended by the package maintainer. In particular, it advises measuring the download and upload speeds so as to best evaluate real limits.

Standard Configuration

Barring a specific QoS configuration, the Linux kernel uses the <literal>pfifo_fast</literal> queue scheduler, which provides a few interesting features by itself. The priority of each processed IP packet is based on the ToS field (<emphasis>Type of Service</emphasis>) of this packet; modifying this field is enough to take advantage of the scheduling features. There are five possible values:

Normal-Service (0);