Hello, I am trying to mess with a prio type qdisc, and must be missing something. Here''s my sample code: tc qdisc add dev eth0 root handle 1: prio tc filter add dev eth0 parent 1:0 prio 1 protocol ip u32 \ match ip dst 208.0.0.0/8 flowid 1:1 tc filter add dev eth0 parent 1:0 prio 3 protocol ip u32 \ match ip dst 0.0.0.0/0 flowid 1:3 I would assume that any traffic going to 208.x.x.x should be getting priority over all other traffic. But when I set up two simultaneous FTP uploads, one to a server in the 208.x.x.x block and one to another not in that block, both end up at the same transfer rate.. This is going into an ADSL line. What am I missing? Bob
Two questions 1.) When you type tc class ls dev ethx - Do you see that both ftp streams are flowing into their proper class; 1:1, 1:3? 2.) Are you sending enough traffic to reach the point of congestion on you link? - If your not then it will service all the traffic at the same rate. Jon Flechsenhaar Boeing WNW Team Network Services (714)-762-1231 202-E7 -----Original Message----- From: Bob Puff [mailto:bob@nleaudio.com] Sent: Sunday, February 18, 2007 3:32 PM To: lartc@mailman.ds9a.nl Subject: [LARTC] prio not seeming to work Hello, I am trying to mess with a prio type qdisc, and must be missing something. Here''s my sample code: tc qdisc add dev eth0 root handle 1: prio tc filter add dev eth0 parent 1:0 prio 1 protocol ip u32 \ match ip dst 208.0.0.0/8 flowid 1:1 tc filter add dev eth0 parent 1:0 prio 3 protocol ip u32 \ match ip dst 0.0.0.0/0 flowid 1:3 I would assume that any traffic going to 208.x.x.x should be getting priority over all other traffic. But when I set up two simultaneous FTP uploads, one to a server in the 208.x.x.x block and one to another not in that block, both end up at the same transfer rate.. This is going into an ADSL line. What am I missing? Bob _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Flechsenhaar, Jon J wrote:> Two questions > > 1.) When you type tc class ls dev ethx > - Do you see that both ftp streams are flowing into their proper > class; 1:1, 1:3? > > 2.) Are you sending enough traffic to reach the point of congestion on > you link? > - If your not then it will service all the traffic at the same > rate.Hi John, 1. Hmm, I guess not: [root@bob ~]# tc class ls dev eth0 class prio 1:1 parent 1: class prio 1:2 parent 1: class prio 1:3 parent 1: Am I missing something in my short & sweet little script? Again, it is: tc qdisc add dev eth0 root handle 1: prio tc filter add dev eth0 parent 1:0 prio 1 protocol ip u32 \ match ip dst 208.0.0.0/8 flowid 1:1 tc filter add dev eth0 parent 1:0 prio 3 protocol ip u32 \ match ip dst 0.0.0.0/0 flowid 1:3 2. I''m definitely saturating my 384k upstream. Bob
Bob, Sorry, actually you need this command tc -s -d class ls dev ethx. Just so you know you can sub "class" out with "qdisc" or "filter". This will show stats in detail. Ex. Packets flowing through your queue. Do you have a priority assigned to the class also? I see one filter has a higher priority so it should get more packets than the other; which I know is what your trying to do. Jon Flechsenhaar Boeing WNW Team Network Services (714)-762-1231 202-E7 -----Original Message----- From: Bob Puff@NLE [mailto:bob@nleaudio.com] Sent: Monday, February 19, 2007 9:58 AM To: Flechsenhaar, Jon J Cc: lartc@mailman.ds9a.nl Subject: Re: [LARTC] prio not seeming to work Flechsenhaar, Jon J wrote:> Two questions > > 1.) When you type tc class ls dev ethx > - Do you see that both ftp streams are flowing into their proper> class; 1:1, 1:3? > > 2.) Are you sending enough traffic to reach the point of congestion > on you link? > - If your not then it will service all the traffic at the same > rate.Hi John, 1. Hmm, I guess not: [root@bob ~]# tc class ls dev eth0 class prio 1:1 parent 1: class prio 1:2 parent 1: class prio 1:3 parent 1: Am I missing something in my short & sweet little script? Again, it is: tc qdisc add dev eth0 root handle 1: prio tc filter add dev eth0 parent 1:0 prio 1 protocol ip u32 \ match ip dst 208.0.0.0/8 flowid 1:1 tc filter add dev eth0 parent 1:0 prio 3 protocol ip u32 \ match ip dst 0.0.0.0/0 flowid 1:3 2. I''m definitely saturating my 384k upstream. Bob