User manual BARRACUDA BARRACUDA NG FIREWALL HOW TO TRAFFIC SHAPING REV1.1

[. . . ] How To: Traffic Shaping Barracuda NG Firewall Revision 1. 1 Barracuda Networks Inc. Winchester Blvd Campbell, CA 95008 http://www. barracuda. com Copyright Notice Copyright 2004-2010, Barracuda Networks www. barracuda. com v4. x-090623-06-1119 All rights reserved. Information in this document is subject to change without notice. Trademarks Barracuda NG Firewall is a trademark of Barracuda Networks. All other brand and product names mentioned in this document are registered trademarks or trademarks of their respective holders. 2 Barracuda NG Firewall - How To: Traffic Shaping Contents Chapter 1 - I n t r o d u c t i o n . [. . . ] In order to achieve this, open the Forwarding Rules of your forwarding firewall and create a new rule or edit an existing one. Most likely, every kind of traffic will be passed through this rule due to the fact that this is an ISP setup without restricting rules for the customers. If you want to assign specific traffic to a Shaping Connector, choose the designated Shaping Connector in the Forward Band field. All correctly introduced connectors will be shown in this list. Note: You should not forget to correctly assign the bands, otherwise auto-assigning may appear in a wrong way. 6. Active Traffic Shaping If this Traffic Shaping scenario has been configured and is up and running, the status monitor of your forwarding firewall service looks like this:. Fig. 4­28 Active Traffic Shaping 27 Example: Internet Service Provider 7. Table 4­4 Issue To Check Completion Checklist Shaping Tree created and configured?You are done! 28 Barracuda NG Firewall - How To: Traffic Shaping Chapter 5 Example: Fast VoIP & RDP Throughput Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Step-By-Step Guidance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 29 Example: Fast VoIP & RDP Throughput 5. 1 Overview Fig. 5­29 Mini ISP Setup Zurich HTTP Client SIP Client RDP Client Munich HQ NG Firewall RDP Client HTTP Client SIP Client HTTP Client This scenario makes use of the features, namely the setting NoDelay as Priority of a Shape Connector, and, on the other hand, Priority as the Operation Mode of a Virtual Interface. The aim of these operation modes is to guarantee the fastest possible throughput for specific traffic types. Typically, this would apply to voice-over-IP (VOIP / SIP) applications, which rely on real-time full duplex connections in order to enable smooth voice communication. Another typical example are remote desktop protocol (RDP) applications, where a fast real-time connection is also of essential importance. While some of them will need absolutely flawless realtime connections in order to reach a designated grade of quality, minor delays may be acceptable to others. For example, during a phone conversation, any delay will lead to interruptions and irritations in the stream of speech, therefor having a noticeable impact on the service quality. On the other hand, a few dropouts in the data stream of a remote desktop session will have no further impacts. You should carefully decide whether which of the both prioritising methods introduced in the next chapter you will use for a particular appliance. 5. 1. 1 Step-By-Step Guidance There are two different ways to assure priority passing of certain traffic through a Shaping Tree. The - as it were - old way would simply mean feeding the priority traffic directly into the root node. However, in some cases, this solution has highly visible drawbacks, especially in a more complex Shaping Tree. That's why it is possible to design Shaping Trees comprising Virtual Interfaces with an Operation Mode setting of Priority. Moreover, there is also the possibility to create Shape Connectors with a Priority setting of NoDelay. Both methods yield the same effect: prioritising of traffic with the intent of minimal latency. [. . . ] · Through the regular interface, premium traffic is given high priority and bulk traffic low priority. · Through the fallback interface, premium traffic goes the same way as through the regular interface, while bulk traffic is to be blocked to have enough bandwidth left for the other types of traffic. Thus, you need an additional, different Shaping Tree for the fallback connection. Note: All configuration work is to be done on a Barracuda Control Center box. A globally valid Traffic Shaping Tree is created on this box and then assigned to the interfaces directly on the remote managed boxes. [. . . ]