From: K S Sreeram <sreeram@tachyontech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bandwidth limiting incoming data
Date: Mon, 23 Jun 2003 12:43:07 +0000 [thread overview]
Message-ID: <marc-lartc-105637175123848@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105637139023569@msgid-missing>
On Mon, 2003-06-23 at 05:47, Trevor Warren wrote:
> Hello Sreram,
>
> AFAIK all Traffic Shaping be it Ingress/Egress can be done at your end.
> This will help majorly on the link at your end by prioritising trafic
> appropriately.
>
> You can't possibly change traffic priorities at your isps end.
>
Maybe my mail wasnt clear, but what i wanted to know is how to shape
incoming traffic on my box, and not at the ISP's end, which I cant
control.
>
> On Mon, 2003-06-23 at 17:38, K S Sreeram wrote:
> > Hi
> >
> > I am connected to the internet thru a 128kbps connection, with a single
> > box. There is no separate router.
> >
> > I have a 'cvs update' going on for a rather large repository.
> > Whenever there is any HTTP traffic(browser/wget/apt-get etc), the CVS
> > traffic seems to come to a halt. So it looks like my ISP is giving
> > higher priority to HTTP traffic.
> >
> > Is there any way I can give higher priority to the CVS traffic?
> >
> > I have read lartc, but all the techniques it talks about
> > (cbq, htb etc) works only for outgoing traffic, not for incoming data.
> > I am not sure if the ingress qdisc is suitable for this problem
> >
> > In freebsd, I could use 'ipfw pipes' to control incoming traffic too..
> > Is there a similar mechanism that can be done in linux?
> >
> > Regards
> >
> > Thanks in Advance!
> --
> ( >- GNU/LINUX, It's all about CHOICE -< )
> /~\ __ trevor@clovertechnologies.com __ /~\
> | \) / Pre Sales Consultant - Red Hat \ (/ |
> |_|_ \ 9820349221(M) | 22881326(O) / _|_|
> \___________________________________/
>
--
K S Sreeram
Director of Research
Tachyon Technologies Pvt. Ltd.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-06-23 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 0:29 [LARTC] bandwidth limiting incoming data Trevor Warren
2003-06-23 12:20 ` K S Sreeram
2003-06-23 12:43 ` K S Sreeram [this message]
2003-06-24 3:53 ` K S Sreeram
2003-06-26 19:59 ` Stef Coene
2003-06-26 21:49 ` Bernard Robbins
2003-06-27 5:42 ` K S Sreeram
2003-06-30 18:25 ` Steve Wright
2003-07-01 19:39 ` 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=marc-lartc-105637175123848@msgid-missing \
--to=sreeram@tachyontech.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.