Re: LARTC digest, Vol 1 #725 - 2 msgs

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I will be out of the office from 8/19 until 8/23.  I will be returning on Monday
afternoon, 8/26, and will reply then.

Thank you,

Michael Pellegrino
Softerware, Inc.

___________________________________________________________________________
Subject: LARTC digest, Vol 1 #725 - 2 msgs
From: lartc@mailman.ds9a.nl
Date: 08/19/02 01:27:39

Send LARTC mailing list submissions to
	lartc@mailman.ds9a.nl

To subscribe or unsubscribe via the World Wide Web, visit
	http://mailman.ds9a.nl/mailman/listinfo/lartc
or, via email, send a message with subject or body 'help' to
	lartc-request@mailman.ds9a.nl

You can reach the person managing the list at
	lartc-admin@mailman.ds9a.nl

When replying, please edit your Subject line so it is more specific
than "Re: Contents of LARTC digest..."


Today's Topics:

   1. VoIP and QoS (Patrick Chan)
   2. Re: filter in-cache traffic  with tc (Alexey Talikov)

--__--__--

Message: 1
From: Patrick Chan <patrick_chan@mtelnet.com>
To: lartc@mailman.ds9a.nl
Date: Mon, 19 Aug 2002 10:01:18 +0800
Subject:  VoIP and QoS

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C24724.4EFA3390
Content-Type: text/plain;
	charset="iso-8859-1"

There are two Linux routers, a 64K leased line is used
to connect these two machines. Now, we would like to run
Voice over IP between two machines. We have to run QoS and 
tag voice packet's TOS field,
otherwise, the voice quality is terrible if we transfer file
and make voice call at the same time.

I am not familiar with tc in Linux. But I have copied a script
from LARTC archives. If the following config is used, the situation
is better than nothing used. The voice packets can be tagged as 
TOS=0x21:

tc qdisc add dev hdlc0 parent 1:1 handle 2: pfifo limit 512
tc qdisc add dev hdlc0 parent 1:2 handle 3: pfifo limit 512
tc qdisc add dev hdlc0 parent 1:3 handle 4: pfifo limit 512
tc filter add dev hdlc0 parent 1:0 protocol ip prio 1 u32 divisor 1
tc filter add dev hdlc0 parent 1:0 prio 1 u32 match ip tos 0x21 0xff flowid
1:1

I don't know what it means exactly. But this is used, the voice quality
is bad at the beginning when file is transferred. The voice quality will
"converge" to be good after about 30 seconds.

However, this is not acceptable. Can anyone tell me what is the best
tc config for running VoIP? Thanks very much.

------_=_NextPart_001_01C24724.4EFA3390
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>VoIP and QoS</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>There are two Linux routers, a 64K leased line is used</FONT>
<BR><FONT SIZE=2>to connect these two machines. Now, we would like to run</FONT>
<BR><FONT SIZE=2>Voice over IP between two machines. We have to run QoS and </FONT>
<BR><FONT SIZE=2>tag voice packet's TOS field,</FONT>
<BR><FONT SIZE=2>otherwise, the voice quality is terrible if we transfer file</FONT>
<BR><FONT SIZE=2>and make voice call at the same time.</FONT>
</P>

<P><FONT SIZE=2>I am not familiar with tc in Linux. But I have copied a script</FONT>
<BR><FONT SIZE=2>from LARTC archives. If the following config is used, the situation</FONT>
<BR><FONT SIZE=2>is better than nothing used. The voice packets can be tagged as </FONT>
<BR><FONT SIZE=2>TOS=0x21:</FONT>
</P>

<P><FONT SIZE=2>tc qdisc add dev hdlc0 parent 1:1 handle 2: pfifo limit 512</FONT>
<BR><FONT SIZE=2>tc qdisc add dev hdlc0 parent 1:2 handle 3: pfifo limit 512</FONT>
<BR><FONT SIZE=2>tc qdisc add dev hdlc0 parent 1:3 handle 4: pfifo limit 512</FONT>
<BR><FONT SIZE=2>tc filter add dev hdlc0 parent 1:0 protocol ip prio 1 u32 divisor 1</FONT>
<BR><FONT SIZE=2>tc filter add dev hdlc0 parent 1:0 prio 1 u32 match ip tos 0x21 0xff flowid 1:1</FONT>
</P>

<P><FONT SIZE=2>I don't know what it means exactly. But this is used, the voice quality</FONT>
<BR><FONT SIZE=2>is bad at the beginning when file is transferred. The voice quality will</FONT>
<BR><FONT SIZE=2>&quot;converge&quot; to be good after about 30 seconds.</FONT>
</P>

<P><FONT SIZE=2>However, this is not acceptable. Can anyone tell me what is the best</FONT>
<BR><FONT SIZE=2>tc config for running VoIP? Thanks very much.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C24724.4EFA3390--

--__--__--

Message: 2
Date: Mon, 19 Aug 2002 09:05:12 +0500
From: Alexey Talikov <alexey_talikov@texlab.com.uz>
Reply-To: Alexey Talikov <alexey_talikov@texlab.com.uz>
Organization: Fortek
To: Fabian Gervan <fabian1@inter-k.com.ar>
Cc: lartc@mailman.ds9a.nl
Subject: Re:  filter in-cache traffic  with tc

Hello Fabian,
I recomend you use squid delay pools or WRR qdisc with patch for
squid.
see this links
http://wipl-wrr.sourceforge.net/
http://squid-docs.sourceforge.net/latest/html/x2116.html


Monday, August 19, 2002, 7:31:05 AM, you wrote:

FG> Hello lartc, I am using squid in transparent mode, and bandwith control
FG> with tc (htb). (redhat 7.3).
FG> Currently I mark packets comming from 3128 (squid
FG> port) to users, there are any way to filter the trafic if the object
FG> that user request alreay is in the squid cache (hit)?
FG> sorry for my english.


-----------------------------------
mailto:alexey_talikov@texlab.com.uz
BR
Alexey Talikov
FORTEK
-----------------------------------



--__--__--

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc


End of LARTC Digest


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux