From: Mohan Sundaram <mohan.tux@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Why not qos for downloading stream??
Date: Sat, 13 Oct 2007 02:58:55 +0000 [thread overview]
Message-ID: <4710319F.2070201@vsnl.com> (raw)
In-Reply-To: <470FEA9F.6020707@swiss-wireless.com.ar>
Beat Meier wrote:
> HI there
>
> Simple question :-)
> Why there is always only qos examples for upload and not download stream
> of adsl?
QoS works on packet queuing at the interface level. We can only queue
what we send out or police/ rate limit what you receive. On edge
devices, normally, a incoming stream on one interface translates to one
or more outgoing streams on other interfaces. Thus applying QoS on an
egress interface is equivalent to doing QoS on the ingress interface.
TCP/IP slows down automatically when some congestions occur. The above
does not hold true for UDP/ICMP and that is why these are commonly rate
limited at ingress.
> I have a linux router which shares 5 wireless "customers" my neighbours
> and me to
> one adsl link 512kbps download 128kbps upload ...
> Now does it make sense to do qos on the linux router for download for us?
> Say if someone is using ssh from outside ...
> So I tried to apply the example 15.10 of Cookbook of the lartc howto on
> the linux router ...
> I have for every neighbour a class which limits its traffic to 128kbps
> and below that
> I addedd the whole tree of example 15.10 on the router ...
> Or does it make more sense this to do on the ap with ingress? I have a
> full linux
> ap router for each neighbour.
>
Shape outgoing traffic on the interface that faces each customer.
Mohan
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-10-13 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 21:43 [LARTC] Why not qos for downloading stream?? Beat Meier
2007-10-13 1:13 ` Andreas Mueller
2007-10-13 2:58 ` Mohan Sundaram [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=4710319F.2070201@vsnl.com \
--to=mohan.tux@gmail.com \
--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.