Hi Rangi, Bandwidth ist
important, but VoIP needs more than this. Voice traffic needs low latency of packets.
That’s why traffic shaping maybe not lose your problem. in this a HFCS queuing
descipline is used instead of HTB, because this can separate between bandwidth
and delay. For more Information about this can you find here: http://linux-ip.net/articles/hfsc.en/ bye Simo Von:
lartc-bounces@xxxxxxxxxxxxxxx [mailto:lartc-bounces@xxxxxxxxxxxxxxx] Im
Auftrag von Rangi Biddle Dear List, I am wanting to perform some traffic
shaping as the subject of this email suggests. What I am wanting to do is this; I
would like to have traffic shaping performed on the following protocols:
HTTP, RDP, GRE, PPTP, SIP and IAX. Obviously I would like to have highest
priority set for voice packets so much so that the general http traffic does
not impede on the voice packets. I would like to have ample bandwidth
available for RDP so that I am able to connect to a remote site and not have
too much lag but ample enough that most tasks can be done. HTTP traffic
would possibly have the lowest priority of all the protocols that I have
listed. So to clarify priority would be something such as this: 1.
IAX 2.
SIP 3.
GRE 4.
PPTP 5.
RDP 6.
HTTP I have a linux gateway that I will use for
performing the traffic shaping and is setup in the following way:
-------------
------------
---------
| ADSL | <---------->
| LINUX | <----------> |
LAN |
-------------
------------
--------- I plan to have the ADSL router forward all
traffic to the linux gateway using something similar to a BIMAP rule where all
incoming and outgoing traffic is made to appear to come from the public IP
address. I welcome any and all suggestions but would possibly prefer the
most elegant of solutions J Many thanks in advance Rangi |
_______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc