shorewall-tcdevices(5)

1shorewall-tcdevices(5)                                  shorewall-tcdevices(5)
2
3
4

NAME

6       tcdevices - Shorewall Traffic Shaping Devices file
7

SYNOPSIS

9       /etc/shorewall/tcdevices
10

DESCRIPTION

12       Entries  in  this file define the bandwidth for interfaces on which you
13       want traffic shaping to be enabled.
14
15       If you do not plan to use traffic shaping for a device, don't put it in
16       here  as  it  limits the troughput of that device to the limits you set
17       here.
18
19       A note on the bandwidth definitions used in this file:
20
21       · don't use a space between the integer value and the unit:  30kbit  is
22         valid while 30 kbit is not.
23
24       · you can use one of the following units:
25
26         kpbs   Kilobytes per second.
27
28         mbps   Megabytes per second.
29
30         kbit   Kilobits per second.
31
32         mbit   Megabits per second.
33
34         bps or number
35                Bytes per second.
36
37       · Only whole integers are allowed.
38
39       The columns in the file are as follows.
40
41       INTERFACE — interface
42              Name  of  interface.  Each  interface may be listed only once in
43              this file. You may NOT specify  the  name  of  an  alias  (e.g.,
44              eth0:0) here; see ⟨http://www.shorewall.net/FAQ.htm#faq18⟩
45
46              You  may  NOT  specify wildcards here, e.g. if you have multiple
47              ppp interfaces, you need to put them all in here!
48
49              If the device doesn't exist, a warning message  will  be  issued
50              during "shorewall [re]start" and "shorewall refresh" and traffic
51              shaping configuration will be skipped for that device.
52
53       IN-BANDWIDTH — bandwidth
54              The incoming bandwidth of that interface.  Please note that  you
55              are  not  able to do traffic shaping on incoming traffic, as the
56              traffic is already received before you could do  so.   But  this
57              allows you to define the maximum traffic allowed for this inter‐
58              face in total, if the rate is exceeded, the packets are dropped.
59              You  want  this  mainly if you have a DSL or Cable connection to
60              avoid queuing at your providers side.
61
62              If you don't want any traffic to be dropped, set this to a value
63              to  zero  in  which  case  Shorewall  will not create an ingress
64              qdisc.
65
66       OUT-BANDWIDTH — bandwidth
67              The outgoing bandwidth of that interface.  This is  the  maximum
68              speed  your  connection can handle. It is also the speed you can
69              refer as "full" if you define the tc classes in shorewall-tc‐
70              classes  ⟨shorewall-tcclasses.html⟩ (5).  Outgoing traffic above
71              this rate will be dropped.
72
73              Warning
74
75              This file is currently limited to ten (10)  entries.  Additional
76              entries  will  cause  run-time  errors in the generated firewall
77              script.
78

EXAMPLES

80       Example 1:
81              Suppose you are using PPP over Ethernet (DSL) and  ppp0  is  the
82              interface  for  this.  The  device  has an outgoing bandwidth of
83              500kbit and an incoming bandwidth of 6000kbit
84
85                      #INTERFACE   IN-BANDWIDTH    OUT-BANDWIDTH
86                      ppp0         6000kbit        500kbit
87

FILES

89       /etc/shorewall/tcdevices
90

NAME

SYNOPSIS

DESCRIPTION

EXAMPLES

FILES

SEE ALSO