Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dummynet(4) [opensolaris man page]

DUMMYNET(4)                                                BSD Kernel Interfaces Manual                                                DUMMYNET(4)

NAME
dummynet -- traffic shaper, bandwidth manager and delay emulator DESCRIPTION
The dummynet system facility permits the control of traffic going through the various network interfaces, by applying bandwidth and queue size limitations, implementing different scheduling and queue management policies, and emulating delays and losses. The user interface for dummynet is implemented by the ipfw(8) utility, so please refer to the ipfw(8) manpage for a complete description of the dummynet capabilities and how to use it. Kernel Options The following options in the kernel configuration file are related to dummynet operation: IPFIREWALL enable ipfirewall (required for dummynet) IPFIREWALL_VERBOSE enable firewall output IPFIREWALL_VERBOSE_LIMIT limit firewall output DUMMYNET enable dummynet operation HZ set the timer granularity Generally, the following options are required: options IPFIREWALL options DUMMYNET options HZ=1000 # strongly recommended Additionally, one may want to increase the number of mbuf clusters (used to store network packets) according to the sum of the bandwidth- delay products and queue sizes of all configured pipes. SEE ALSO
setsockopt(2), if_bridge(4), ip(4), ipfw(8), sysctl(8) HISTORY
The dummynet facility was initially implemented as a testing tool for TCP congestion control by Luigi Rizzo <luigi@iet.unipi.it>, as described on ACM Computer Communication Review, Jan.97 issue. Later it has been modified to work at the IP and bridging levels, integrated with the ipfw(4) packet filter, and extended to support multiple queueing and scheduling policies. BSD October 28, 2002 BSD

Check Out this Related Man Page

IPFW(4)                                                    BSD Kernel Interfaces Manual                                                    IPFW(4)

NAME
ipfw -- IP packet filter and traffic accounting SYNOPSIS
To compile ipfw into the kernel, place the following option in the kernel configuration file: options IPFIREWALL Other kernel options related to ipfw which may also be useful are: options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_FORWARD options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 To load ipfw as a module at boot time, add the following line into the loader.conf(5) file: ipfw_load="YES" DESCRIPTION
The ipfw system facility allows filtering, redirecting, and other operations on IP packets travelling through network interfaces. The default behavior of ipfw is to block all incoming and outgoing traffic. This behavior can be modified, to allow all traffic through the ipfw firewall by default, by enabling the IPFIREWALL_DEFAULT_TO_ACCEPT kernel option. This option may be useful when configuring ipfw for the first time. If the default ipfw behavior is to allow everything, it is easier to cope with firewall-tuning mistakes which may acciden- tally block all traffic. To enable logging of packets passing through ipfw, enable the IPFIREWALL_VERBOSE kernel option. The IPFIREWALL_VERBOSE_LIMIT option will prevent syslogd(8) from flooding system logs or causing local Denial of Service. This option may be set to the number of packets which will be logged on a per-entry basis before the entry is rate-limited. Policy routing and transparent forwarding features of ipfw can be enabled by IPFIREWALL_FORWARD kernel option. The user interface for ipfw is implemented by the ipfw(8) utility, so please refer to the ipfw(8) manpage for a complete description of the ipfw capabilities and how to use it. SEE ALSO
setsockopt(2), divert(4), ip(4), ipfw(8), sysctl(8), syslogd(8), pfil(9) BSD September 1, 2006 BSD
Man Page