All of lore.kernel.org
 help / color / mirror / Atom feed
From: Beat Meier <mbe_ml@swiss-wireless.com.ar>
To: lartc@vger.kernel.org
Subject: [LARTC] Why not qos for downloading stream??
Date: Fri, 12 Oct 2007 21:43:59 +0000	[thread overview]
Message-ID: <470FEA9F.6020707@swiss-wireless.com.ar> (raw)

HI there

Simple question :-)
Why there is always only qos examples for upload and not download stream 
of adsl?
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.

Now comes the filtering and I was wondering if there
1. makes sense i.e. it helps us if download speed is at limit to 
priorize ssh, voip etc.
2. what will be the cpu load if you have not only 5 connected clients if 
not say 30
and a lot of filter rules i.e. each customer needs his full filter set ...

Has anybody such a thing in production or is it "useless"?

Greetings

Beat
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-10-12 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 21:43 Beat Meier [this message]
2007-10-13  1:13 ` [LARTC] Why not qos for downloading stream?? Andreas Mueller
2007-10-13  2:58 ` Mohan Sundaram

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=470FEA9F.6020707@swiss-wireless.com.ar \
    --to=mbe_ml@swiss-wireless.com.ar \
    --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.