Bandwidth Limiting HOWTO

Tomasz Chmielewski

tch@metalab.unc.edu

Revision History
Revision 0.9	2001-11-20	Revised by: tc

This document describes how to set up your Linux server to limit download bandwidth or incoming traffic and how to use your internet link more efficiently.

Table of Contents

1. Introduction

1.1. New versions of this document
1.2. Disclaimer
1.3. Copyright and License
1.4. Feedback and corrections
1.5. Thanks

2. Before We Start

2.1. What do we need
2.2. How does it work?

3. Installing and Configuring Necessary Software

3.1. Installing Squid with the delay pools feature
3.2. Configuring Squid to use the delay pools feature
3.3. Solving remaining problems

4. Dealing with Other Bandwidth-consuming Protocols Using CBQ

4.1. FTP
4.2. Napster, Realaudio, Windows Media and other issues

5. Frequently Asked Questions

5.1. Is it possible to limit bandwidth on a per-user basis with delay pools?
5.2. How do I make wget work with Squid?
5.3. I set up my own SOCKS server listening on port 1080, and now I'm not able to connect to any irc server.
5.4. I don't like when Kazaa or Audiogalaxy is filling up all my upload bandwidth.
5.5. My outgoing mail server is eating up all my bandwidth.
5.6. Can I limit my own FTP or WWW server in a manner similar it is shown in the question above?
5.7. Is it possible to limit bandwidth on a per-user basis with cbq.init script?
5.8. Whenever I start cbq.init, it says sch_cbq is missing.
5.9. CBQ sometimes doesn't work for no reason.
5.10. Delay pools are stupid; why can't I download something at full speed when the network is used only by me?
5.11. My downloads break at 23:59 with "acl day time 09:00-23:59" in squid.conf. Can I do something about it?
5.12. Squid's logs grow and grow very fast, what can I do about it?
5.13. CBQ is stupid; why can't I download something at full speed when the network is used only be me?

6. Miscellaneous

6.1. Useful resources

		Next
		Introduction