![Shaping Shaping](/uploads/1/2/5/4/125499953/231665667.png)
![Fortigate traffic shaping guide Fortigate traffic shaping guide](/uploads/1/2/5/4/125499953/412793059.png)
Hi Guys,I created traffic shaping policy in 5.4 Fortigate firewall for per device that should have min and max bandwidth on our internet pipe. Though we do not have any other traffic shaping policy for other traffic.Now question is- Do I need to create traffic shaping policy for other traffic that share same interface for WAN traffic to make above traffic policy?- If above question answer is Yes (that should have traffic policy for other traffic) to create another traffic shaping policy can create with all and all to that interface. But I do not want to limit bandwidth for all other traffic as it could have -ve impact.ref:Thanks.
In this recipe, you will deploy FortiGate Autoscaling into a new VPC OnDemand license for Amazon Web Services (AWS). If you are not using an existing VPC for. Select Edit to view the new options for each shaper, which include Per policy and For all Policies. 2- Traffic Shaping for reverse traffic FortiOS 4.0 enables you to have separate shapers for reverse traffic on a Firewall Policy.With FortiOS 3.0, the reverse traffic was shaped with the same shaper profile as the originating traffic.
TS in FOS is quite effective if - hosts are using unique source addresses (no NAT of a whole subnet behind just one address) - you can live with non-cooperative throttling Background for the latter: suppose you have 100 Mbps WAN bandwidth, and 10 subnets sharing the WAN line. For fairness you limit each subnet's bw to 10 Mbps.
Now, at night, there's 90 Mbps available - but one subnet cannot use it fully, only the assigned 10 Mbps. That's what I call 'non-cooperative'. Additionally, TS for incoming traffic doesn't really work well. TS uses packet dropping only, TCP cares, UDP doesn't.
But then again, TS comes for free. Always comes in handy to throttle down that occasional leecher.