From: "Serge Maandag" <serge.maandag@staff.zeelandnet.nl>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Bandwidth by port
Date: Wed, 11 Dec 2002 20:12:17 +0000 [thread overview]
Message-ID: <marc-lartc-103963762508412@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103961486811331@msgid-missing>
Hmm,
I'm brand new to both tc and the list, so forgive me if I'm uttering nonsense :)
The example below seems good to me if eth1 is the interface connected to the side your clients are on, not the side the ftp servers are on. Are u sure that is the interface setup you have? I have done a similar setup, but based on ip-range. I both used fw marks and route realm marks and that worked in both occasions.
serge.
-----Original Message-----
From: David Coello [mailto:dcoello@quarkinside.com]
Sent: Wednesday, December 11, 2002 7:16 PM
To: lartc@mailman.ds9a.nl
Subject: Re: [LARTC] Bandwidth by port
Hi
But why the code of above doesn´t work? Anybody knows other systanx thats
works to limit bandwidth by port?
Thanks and regards
David
>Active FTP uses 20/21 tcp on the server side
>
>On Wednesday 11 December 2002 13:38, you wrote:
> > On Wednesday 11 December 2002 09:19, David Coello wrote:
> > > Hi
> > >
> > > I am trying to limit the bandwidth by port buy without success.
> > >
> > > The code is :
> > >
> > > # Disciplina de encolamiento
> > > tc qdisc add dev eth1 root handle 10: cbq bandwidth 10Mbit avpkt 1000 mpu
> > > 64
> > >
> > > # Clase
> > > tc class add dev eth1 parent 10:0 classid 10:1 cbq bandwidth 1kbps rate
> > > 1kbps allot 1514 prio 1 maxburst 10 avpkt 100 bounded isolated
> > >
> > > # Filtro
> > > # tc filter add dev eth1 parent 10:0 protocol ip handle 3 fw classid 10:1
> > >
> > > tc filter add dev eth1 parent 10:0 protocol ip u32 match ip dst
> > > 0.0.0.0 match ip sport 20 0xffff flowid 10:1
> > > tc filter add dev eth1 parent 10:0 protocol ip u32 match ip dst
> > > 0.0.0.0 match ip sport 21 0xffff flowid 10:1
> > >
> > > What am i making bad? I have probed with mark&iptables but with identical
> > > result. When i make ftp i download without band limit.
> >
> > Ftp is very difficult to shape because it can use dynamic ports. Try using
> > active or passive ftp. I'm not sure wich one uses fixed ports.
> >
> > Stef
>_______________________________________________
>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/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-11 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 13:50 [LARTC] Bandwidth by port Paolo Poletti
2002-12-11 8:19 ` David Coello
2002-12-11 12:38 ` Stef Coene
2002-12-11 18:15 ` David Coello
2002-12-11 20:12 ` Serge Maandag [this message]
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=marc-lartc-103963762508412@msgid-missing \
--to=serge.maandag@staff.zeelandnet.nl \
--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