FireBrick Traffic Shaping: Difference between revisions

*The FireBrick 2700 has been used as a 'black' box traffic shaping device in shared offices. It's quite easy to configure a FireBrick for a 'serviced office' scenario where tenants pay for a slice of a fast pipe. -this would be great for leased lines, ethernet services, FTTC, FTTP etc.

*The FireBrick can shape based on parameters such as source/target IP/port/protocol, giving flexibility.

*When shaping, CWLCQM graphs are produces for each 'shaper', giving a visual representation of the traffic.

If you want the Firebrick to be 'invisible' on your LAN, iei.e., you have machines on the LAN which use the gateway IP of your router, and you do not want to use the FireBrick as the router, then setting proxy-arp on the subnets is required. - this will then proxy arps between the FireBricks LAN and WAN, both ways. -Note broadcast traffic is not passed through the FireBrick - so the router won't be able to do DHCP - the FireBrick can, or another host on the LAN can instead.

Here we have defined 2 shapers, one with 500Kb500kbit/s up/down, and one with 3Mb3Mbit/s up/down.

These shapers can then be used in rules, ege.g.:

Here we have set specific IP addresses to go through specific shapers, so 192.0.2.2 will get 500K/bs and 192.0.2.3 will get 3Mb3Mbit/s.