274
The minimum bandwidth is assigned as follows: The bandwidth required for VoIP
according to the configuration is reserved and subtracted from the total available
bandwidth. Of the remaining bandwidth, 10% goes to empty TCP ACK packets, 50% to
packets with high priority and 20% to packets with normal and low priority respectively.
Inbound traffic shaping treats all non-TCP packets as high
priority.
Priorization of connections
Use this list to assign a higher or lower priority to specific data packets. If more than
one rule matches, the priority of the topmost rule will be used.
The following inputs are available:
Protocol
Selects the IP protocol and port signature. With inbound bandwidth management,
only TCP protocols will actually be processed.
Protocols are defined in menu "Definitions > Protocols".
Local IP/network
Viewed from the perspective of the selected interface, you can enter a local
address here. This corresponds to the source IP of outbound packets (before
SNAT) and the destination IP of inbound packets (before DNAT).
When SNAT or DNAT is involved, restricting a priority rule
to specific local IPs usually requires two rules to catch both,
in- and outbound packets: For inbound packets you would
enter a SX-GATE IP, for outbound packets the internal IP
(of the LAN client or the server addressed with DNAT).
Direction
Decide in which direction the port signature of the selected protocol has to be
applied. Let's take the HTTP protocol as an example. The arrow "-->" means
the HTTP port 80 is on the external side. So outbound bandwidth management
will process packets to port 80, inbound bandwidth management packets from
port 80. With "-->" you will get the opposite: Packets to port 80 are processed by
inbound, packets from port 80 by outbound bandwidth management. The double
arrow "
↔
" combines both directions.
