TutoLivre

Originally published in http://wasare.net on 19/01/2007

The HTB-Tools is an excellent tool to aid in setting up the HTB (Hierarchical Token Bucket) for limiting use of bandwidth. As the first article on the HTB-Tools explaining the use of the tool has generated many queries and concerns of readers decided write a small supplement. Now I will give more concrete examples of specific configurations for everyday use.

IF you do not know WHAT HTB HTB-TOOLS OR FIRST READ THE ARTICLE BEFORE!

THE EXAMPLE BELOW IS A for illustrative purposes!

1. Download and Upload with different rates

Following the example of the article we assume that the customer should have the same rate of download example, but that the upload would be limited to half or 96kbps and 128kbps for upload, and guaranteed maximum, respectively.

Assuming that your LAN is the same interface eth0 we will monitor the upload / download the file creating / etc/htb/eth0-qos.cfg with the following contents:

  eth1-class WAN ( 
          bandwidth 100,000; 
          100,000 limit; 
          burst 64; 
          priority 1; 
          WAN client ( 
                  bandwidth 100,000; 
                  100,000 limit; 
                  burst 64; 
                  priority 1; 
                  dst (XXXX / X # ip / mask your network's WAN 
                  ); 
                  (XXXX src / X # ip / mask your network's WAN 
                  ); 
         ); 

  ); 

  eth1-WAN-class customer ( 
          bandwidth 360; 
          limit 360; 
          burst 8; 
          priority 1; 
          (client DEDICADO_1 
                  bandwidth 360; 
                  limit 360; 
                  burst 8; 
                  priority 1; 
                  (0.0.0.0 src / 0;); 
                  dst (0.0.0.0 / 0;); 
         ); 

  ); 
  default (bandwidth class 8;); 

Understanding: Inside the file eth1-qos.cfg we have two special classes: eth1-WAN (WAN client) and eth1-WAN-client (DEDICADO_1 client). The class-eth1 WAN provides a limit of 100,000 kbps for traffic to its own network (src and dst). The other class eth1-WAN-client will restrict traffic to the "outside world" in both 360kbps for download (STDs) and to upload (src). What should be noticed is that the class-eth1 WAN gives priority and releases its network to any speed WAN traffic while eth1-class WAN-client limit all the rest to 360kbps. The problem occurs when you have seen on the LAN clients competing with each other and even by 360kpbs. This case is dealt with then.

2. Sharing connection to a fixed rate

A common case that can happen is you have a good connection and a customer wants a link with more dedicated server itself. Assuming you have a link to 1Mbps and the client engages 360kbps that must be shared through a client's own server (a Pentium 100 already serving). Let's consider that the interface is the WAN and LAN eth1 to eth0. On the LAN will not need any limitation, however for the WAN interface (eth1) created the following configuration file - / etc/htb/eth1-qos.cfg:

  eth1-class WAN ( 
          bandwidth 100,000; 
          100,000 limit; 
          burst 64; 
          priority 1; 
          WAN client ( 
                  bandwidth 100,000; 
                  100,000 limit; 
                  burst 64; 
                  priority 1; 
                  dst ( 
                          XXXX / X # ip / mask your network's WAN 
                  ); 
                  src ( 
                         XXXX / X # ip / mask your network's WAN 
                  ); 
         ); 

  ); 

  Eth1-WAN-class customer ( 
          bandwidth 360; 
          limit 360; 
          burst 8; 
          priority 1; 
          (client DEDICADO_1 
                  bandwidth 360; 
                  limit 360; 
                  burst 8; 
                  priority 1; 
                  src ( 
                          0.0.0.0 / 0; 
                  ); 
                  dst ( 
                          0.0.0.0 / 0; 
                  ); 
         ); 

  ); 
  ; } ; default (class bandwidth 8;); 

Understanding: Inside the file eth1-qos.cfg we have two special classes: eth1-WAN (WAN client) and eth1-WAN-client (client DEDICADO_1). The class-eth1 WAN provides a limit of 100,000 kbps for traffic to its own network (src and dst). The other class eth1-WAN-client will restrict traffic to the "outside world" in both 360kbps for download (STDs) and to upload (src). This should be noted is that the class-WAN eth1 gives priority and releases its network to any speed WAN traffic while eth1-class WAN-client limit all the rest to 360kbps. The problem occurs when you have seen on the LAN clients competing with each other and even by 360kpbs. This case is dealt with then.

3. Limiting the only connections to the Internet

A case often is a gateway as we have in our network as well as share the Internet provides users of our WAN / LAN other services such as file server, FTP, etc.. If restrict traffic in accordance with the first example we control the use of the Internet link, however all other services provided by the gateway will also be "strangled", made using the network unbearable! What do you do? The second example can solve our problem in part because it limits the overall traffic only for external connections (WAN) connections and the LAN flow freely. On the other hand if we have any service running by next External / WAN and to be used from other external network will be limited to 360kbps. To resolve this problem two alternatives: 1st include the networks of where the services are accessed in the "client WAN" eth1-class WAN (example 2) or 2nd limit the traffic starting from the LAN interface (eth0), without limiting the traffic Internal. The first alternative can become a little inconvenient if customers / users outside access to various networks. The second solution is the most usual for most cases. So let's get the WAN (eth1) with the traffic and we released the control of bandwidth for LAN (eth0), we must create the following file / etc/htb/eth0-qos.cfg:

  eth0-class LAN ( 
          bandwidth 100,000; 
          100,000 limit; 
          burst 32; 
          priority 1; 
          client LAN-LAN ( 
                  bandwidth 100,000; 
                  100,000 limit; 
                  burst 32; 
                  priority 1; 
                  src ( 
                          XXXX / X # ip / mask your network's WAN 
                          ; # ip/máscara da sua rede LAN 192.168.0.0 / 24; # ip / mask of your LAN network 
                  ); 
                  dst ( 
                          XXXX / X # ip / mask your network's WAN 
                          ; # ip/máscara da sua rede LAN 192.168.0.0 / 24; # ip / mask of your LAN network 
                  ); 
         ); 

         LAN0 client-WAN ( 
                  bandwidth 360; 
                  limit 360; 
                  burst 8; 
                  priority 1; 
                  dst ( 
                          0.0.0.0 / 0; 
                  ); 
                  src ( 
                          0.0.0.0 / 0; 
                  ); 
         ); 

  ); 

  ; } ; (Class default bandwidth 8;); 

Understanding: Where the target or the source of traffic for our own network we have a rate of 100.000kbps. For all other destinations and origins (0.0.0.0 / 0) are limiting the traffic to 360kbps.

4. Conclusion

The dual-Tools HTB HTB and give joy to any network administrator! @;)