From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] (no subject)
Date: Wed, 07 Apr 2004 23:02:26 +0000 [thread overview]
Message-ID: <001201c41cf4$6542a180$030aa8c0@t> (raw)
In-Reply-To: <marc-lartc-98373938216902@msgid-missing>
Udp forwarding mostly cannnot be controled.
you can drop udp packets but server will not stop sending then to you
anyway.
(of course this depends on server software)
tcp can be controled so do not have this problem
----- Original Message -----
From: "Ibrahim Cherri" <ibrahim_cherri@hotmail.com>
To: <lartc@mailman.ds9a.nl>
Sent: Wednesday, April 07, 2004 5:12 PM
Subject: [LARTC] (no subject)
> Hello
>
> I was testing HTB using IPerf TCP traffic and the results were very good.
> Until I tried to add some UDP traffic the results were a little strange.
> this is my setup
>
> tc qdisc del dev eth1 root
> tc qdisc add dev eth1 handle 1:0 root htb default 2
>
> tc class add dev eth1 parent 1:0 classid 1:1 htb rate 1mbit
> tc class add dev eth1 parent 1:1 classid 1:2 htb rate 500kbit ceil 1mbit
> tc class add dev eth1 parent 1:1 classid 1:3 htb rate 500kbit ceil 1mbit
>
> tc filter add dev eth1 protocol ip parent 1:0 prio 2 u32 match ip protocol
> 17 0xff flowid 1:3
>
> tc qdisc add dev eth1 parent 1:2 handle 20 pfifo limit 10
> tc qdisc add dev eth1 parent 1:3 handle 30 pfifo limit 10
>
> This simple setup should split the 1mbit bandwidth between TCP and UDP.
> I run 2 IPerf clients simultaneously
> Server:
> iperf -s -p 200
> iperf -s -p 400 -u
> Client:
> iperf -c $ServerIP -p 200
> iperf -c $ServerIP -p 400 -u
>
> then UDP traffic takes about 750kbit and TCP traffic takes about 250kbit
> Can anyone tell me why is that?
>
> thanx,
> Ibrahim
>
> _________________________________________________________________
> Protect your PC - get McAfee.com VirusScan Online
> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid963
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-04-07 23:02 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <marc-lartc-98373938216902@msgid-missing>
2000-12-06 0:19 ` [LARTC] (no subject) sun
2001-04-06 19:37 ` siddhardha garige
2001-04-06 19:46 ` linux
2001-07-03 17:22 ` Jose Miguel Varet
2002-03-13 14:16 ` Rajesh Revuru
2002-03-29 8:19 ` Vahan Grigoryan
2002-03-29 11:03 ` Vahan Grigoryan
2002-03-29 11:15 ` martin f krafft
2002-04-19 12:42 ` Emil Terziev
2002-04-19 12:56 ` Alex Bennee
2002-04-20 9:18 ` Waters
2002-04-20 13:10 ` Mihai RUSU
2002-04-20 19:56 ` Stef Coene
2002-04-20 22:07 ` Re[2]: " Waters
2002-04-20 22:44 ` pof
2002-05-03 9:09 ` Nandan Kaushik
2002-05-03 10:21 ` Stef Coene
2002-05-03 14:52 ` Adrian Chung
2002-05-03 16:38 ` Lei Bao
2002-05-18 15:21 ` William L. Thomson Jr.
2002-05-19 18:05 ` Martin Devera
2002-05-23 9:38 ` Karasik, Vitaly
2002-05-23 9:43 ` Alexey Talikov
2002-06-06 11:58 ` alouini khalif
2002-07-25 2:31 ` Alfred Quah
2002-07-25 5:52 ` Stef Coene
2002-08-18 11:28 ` noroozi
2002-08-18 13:40 ` Eric Leblond
2002-09-30 8:31 ` Fred Thep
2002-10-11 18:40 ` Albuquerque, Marcelo M
2002-10-11 19:36 ` Stef Coene
2002-10-11 21:17 ` Albuquerque, Marcelo M
2002-10-15 18:40 ` Stef Coene
2002-10-25 9:46 ` Andreani Luca
2002-10-25 11:15 ` raptor
2002-10-26 23:20 ` zoop
2002-11-16 21:54 ` Waters
2002-11-16 22:18 ` Stef Coene
2002-11-17 6:11 ` Ashok N N
2002-11-21 12:41 ` ajay
2003-02-26 8:02 ` Kjell Chris Flor
2003-03-02 0:54 ` Martin A. Brown
2003-03-02 10:51 ` Kjell Chris Flor
2003-03-08 20:16 ` Stef Coene
2003-03-21 22:38 ` Kjell Chris. Flor
2003-03-21 22:54 ` Nickola Kolev
2003-03-22 3:03 ` Kjell Chris. Flor
2003-03-22 10:22 ` Nickola Kolev
2003-04-06 18:19 ` GoMi .
2003-04-18 17:21 ` rio
2003-04-18 19:19 ` Stef Coene
2003-04-21 19:30 ` larry lefthook
2003-04-21 20:24 ` Martin A. Brown
2003-06-05 10:33 ` Alejandro Sager
2003-07-30 17:04 ` Daniel Ardelian
2003-07-30 19:02 ` Stef Coene
2003-09-01 18:05 ` Gabriel Corcodel
2003-09-01 19:10 ` Stef Coene
2003-09-04 2:20 ` Randolph Carter
2003-09-25 6:37 ` Senthil Nathan V
2003-10-23 10:47 ` Edmund Turner
2003-10-27 8:08 ` Edmund Turner
2003-10-30 5:51 ` Edmund Turner
2003-10-30 10:12 ` Stef Coene
2003-10-31 5:10 ` Edmund Turner
2003-11-27 17:08 ` Emmanuel
2004-01-12 18:14 ` james jones
2004-02-26 22:53 ` Georgi Moskov
2004-03-06 18:44 ` Sam
2004-04-07 14:12 ` Ibrahim Cherri
2004-04-07 23:02 ` Roy [this message]
2004-05-26 13:21 ` Amita Maheshwari
2004-07-19 9:19 ` Anton Glinkov
2004-07-19 12:04 ` Ed Wildgoose
2004-08-16 8:29 ` Alin Nonosel
2004-09-07 14:22 ` james jones
2004-11-15 11:41 ` tepesu
2005-01-03 3:03 ` Oswin Budiman
2005-02-12 18:57 ` naveen andrew
2005-04-26 15:46 ` Stanislav Nedelchev
2005-07-12 9:34 ` Supratim Mitra
2005-10-10 3:13 ` KOMUNIKA SYSTEM
2005-10-15 16:59 ` KOMUNIKA SYSTEM
2005-10-15 20:31 ` Marek Kierdelewicz
2005-10-20 22:21 ` comp.techs
2006-02-20 13:11 ` Greg Scott
2007-03-28 6:27 ` Leigh Sharpe
2007-09-29 8:59 ` Anirudh Gottumukkala)me in Google Accounts (Anirudh Gottumukkala
2002-10-12 16:28 [LARTC] <no subject> Samuel Kerschbaumer
2002-10-12 16:55 ` Stef Coene
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001201c41cf4$6542a180$030aa8c0@t' \
--to=roy@xxx.lt \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox