Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Björn Snippe" <bjoern@snippe.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ingress/egress shaping
Date: Mon, 27 Jan 2003 17:20:08 +0000	[thread overview]
Message-ID: <marc-lartc-104368809131036@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104368601427650@msgid-missing>

David Boreham wrote:
> With IMQ you'd have three NICs :)
> IMQ is a virtual NIC.
> So if you can achieve your goals with control on the two real NICs,
> do that.
Yes, that's clear to me (well, quite :)), but I read about the 
limitations of the ingress qdisc and that using a virtual imq device 
would give me the power to use classes even on incoming traffic.
I just wanted to be sure not to be doing something stupid <:)
So there's nothing wrong with my thinking?
What comes in from the WWW, I can shape on my inner NIC, and what leaves 
to the router/WWW, I can shape on the outer one?
What happens with all the traffic coming in on my inner NIC from my LAN 
that gets delayed/shaped in order to leave on my outer NIC?
Will my inner NIC drop it, or will my Linux-router collect more and more 
packets, swell up to giant size and explode? :)

Thanks for any answer,
Björn

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-01-27 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 16:45 [LARTC] ingress/egress shaping Björn Snippe
2003-01-27 17:20 ` Björn Snippe [this message]
2003-01-27 17:57 ` Björn Snippe

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-104368809131036@msgid-missing \
    --to=bjoern@snippe.de \
    --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