I hope you've read http://shorewall.net/traffic_shaping.htm completely.
On 11/16/06, Macram Zaarour <[EMAIL PROTECTED]> wrote: > Setting the device OUT-BANDWIDTH on NAT side to below 128k(my download > speed) will surely affect the internal calls voice quality knowing that ulaw > takes up to 80k per call and all calls are proxied on the server. So two > internal calls traffic consumption will far exceed my download speed of 128k You *don't* need traffic shaping on the LAN side. Typically it's very unlikely that you're going to saturate that link. You *must* always shape on the most-constrained link. And if you don't have the most constrained link (because of massive queues at the ISP), then you must reduce the incoming bandwidth and make it the most constrained link to be able to effectively shape the traffic. On the WAN side (128K link) it doesn't need to be far less than 128K. Just enough less that queuing is on the shorewall box and not on the ISP box. > tcclasses ( I am limiting default traffic to 20k on NAT side) > eth1 1 30kbps full 1 > eth1 2 full full 2 default You can't say give 30kbps guaranteed to class 1, and say "full" to class 2!! Please drop the guaranteed bandwidth to 128-30K. > eth0 1 30kbps full 1 > eth0 2 20k 20k 2 default These are not necessary, if you shape correctly on the WAN side. Prasanna. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
