Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dummynet(4) [posix 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

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
Man Page

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Ipfw2 with mac filtering

Work with FreeBSD with firewall ipfw + dummynet and I need to allow to some IP by MAC address and to deny to the others, since I can do it? Thanks. (2 Replies)
Discussion started by: darknighter
2 Replies

2. Linux

How to interrupts work queue with signals

Hi masters, I am doing a project to regulate network bandwidth. I am using workqueue to implement packets management (I uses kernel threads inside each of these work queue) , netfilter hooks to implement packet catcher . All my modules individually works fine . But when I run my workqueues,... (1 Reply)
Discussion started by: iamjayanth
1 Replies

3. BSD

Using several pipes in ipfw (dummynet)

Hi! I've already posted this on the freebsd-questions mailing list, but I thought I could try it here too. I'm using FreeBSD 7.0 with IPFW DUMMYNET enabled. I've got a problem with creating a ruleset, which allows me to limit the overall bandwidth of a link and afterwards pass the packets... (0 Replies)
Discussion started by: xenator
0 Replies

4. BSD

dummynet problem.

I am using dummynet in bridge mode. and its working fine. Now I have built another box (freebsd 7.1) in router mode. On this box I have two NICs, one for lan and one for wan. both networks are segmented physically and logically i-e both interfaces have different ip pools and connected to... (0 Replies)
Discussion started by: azfar
0 Replies

5. IP Networking

bandwidth utilisation high after implementing firewall

hi, we have one unix server which sends multicast packets in the network, recently we have implemented firewall in between unix server and clients.After implementing firewall we found our lease line utilisation has been increased dramatically. Is this because of firewall or else...please... (2 Replies)
Discussion started by: ajaysahoo
2 Replies

6. IP Networking

New network bandwidth requirements

Many papers, articles and posts about network bandwidth requirements refer to network traffic rules-of-thumb when estimating bandwidth requirements for a new network with an unknown load. I've seen a couple rules for video and VoIP. I'd be thankful if someone could share any rules-of thumb they... (5 Replies)
Discussion started by: redrider
5 Replies