Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What does tc shape?
Date: Tue, 10 Jan 2006 00:04:32 +0000	[thread overview]
Message-ID: <43C2FA10.3020706@dsl.pipex.com> (raw)
In-Reply-To: <1136815589.43c26de57c9fc@mail1.alsenet.com>

PoltoS/ wrote:
> Does tc shape IP traffic only, or all traffic going out of interface (Ethernet 
> headers + IP data)? 

You can shape all types of traffic.

On eth interfaces the qdiscs see ip packets as ip length +14 (there are 
more than 14 overhead on the wire - with htb you can specify 
overheads/mpu) on ppp qdiscs see just ip length - not sure about others.

Andy.

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

      reply	other threads:[~2006-01-10  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 14:06 [LARTC] What does tc shape? PoltoS/
2006-01-10  0:04 ` Andy Furniss [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=43C2FA10.3020706@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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