Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Grace Baldonasa <gbaldona@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] TC
Date: Mon, 25 Apr 2005 08:08:35 +0000	[thread overview]
Message-ID: <7034e7b5050425010852225839@mail.gmail.com> (raw)
In-Reply-To: <marc-lartc-101764910022606@msgid-missing>

Thanks for the very prompt reply.

I've been googling already for a few days now trying to understand how
bandwidth management works. I came to understand that TC is a utility
that I can use to shape up my local network bandwidth consumption.
Im hoping I will be guided here through.
Here are my questions:
1. Is TC works on an interface of a physical device only?
2. My objective is to limit the upload/download rate of each computer
in our local network attached to CPE. In this case, all PC's are
attached to common interface (let's sat eth0), will I be able to
filter or limit  individiual PC on their UL/DL rate?
Seeing those examples  in the net, tc works on device interface only.
Hope my understanding is not correct.

Thanks.
More question to come......
grace
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-04-25  8:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1980-01-05 16:14 [LARTC] tc Stef Coene
2001-12-04 17:21 ` Sebastian Taralunga
2001-12-06 12:28 ` bert hubert
2002-04-01  0:03 ` Srikanth Goteti
2002-04-30 20:20 ` Waters
2005-04-25  8:08 ` Grace Baldonasa [this message]
2005-04-25  8:48 ` [LARTC] TC Daniel Harold L.
2005-04-25  9:00 ` Grace Baldonasa
2005-04-25  9:29 ` Grace Baldonasa
2005-04-25 10:19 ` Daniel Harold L.
2005-04-25 10:45 ` Grace Baldonasa
2005-04-25 10:55 ` Jesper Lund
2005-04-25 11:21 ` Andy Furniss

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=7034e7b5050425010852225839@mail.gmail.com \
    --to=gbaldona@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox