1. m0n0Wall Introduction to Traffic shaping by Kristoffer Støvring

2. Sorting order Physical connections - fx. 4096kbit / 768kbit ADSL line Pipes - 1. 3000kbit download (ordinary download) - 2. 1000kbit download (reserved for VPN) - 3. 500kbit upload (ordinary upload) - 4. 256kbit upload (reserved for VPN) Queues - Weighting & Prioritzing & Sorting in Pipes - Weights decide which order the packets are sent in Rules - Sorting of packets into Queues & Pipes

3. Sorting & Prioritizing Physic al connec tion Pipe Down Queue Down Importa nt Rule DNS query Rule ACK packet Queue Down Ordinar y Rule WWW trafic Rule Email trafic Rule Catch all Queue Down Slow Rule P2P trafic Pipe VPN Down Queue VPN Down Rule VPN trafic 53 143 465 25 993 110 500 995 1701 1723 4500 Ports

4. The packets route The packet arrives to m0n0wall First the packet is compared to the list of RULES, when a match is found fx. a DNS packet to/from port 53 matches rule ”DNS query” and is put in QUEUE ”Important”. Queue ”Important” has a WEIGHT of 50 Queue ”Ordinary” has a WEIGHT of 30 Queue ”Slow” has a WEIGHT of 5 So our DNS packet gets a WEIGHT of 50, and is sent out 10 sooner than a similar packet in the ”Slow” queue. PIPES are seen as a string of packets, where the packets in one end are sent onto the network as fast as the pipe allows, Queue weights decide which order the packets have in the Pipe. So a packet with weight 50 which has been waiting for 2ms, comes before a packet with weight 5 thats been waiting for 19ms, but a packet with weight 30 thats been waiting for 4ms will come be sent first.

5. Reserved bandwidth Critical / important connections VPN IP Phones SSH & similar If you have connections that are not to be disturbed under any circomstance, then there is a posibility of making a fx. 1mbit PIPE and there by dedicating 1mbit of the internet connection to a specific type of traffic. A dedicated PIPE could also be used for connections to / from other offices.