All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rio Martin." <rio@martin.mu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] shaping incoming with ingress
Date: Thu, 31 Jul 2003 03:55:16 +0000	[thread overview]
Message-ID: <marc-lartc-105962350319121@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105960881709594@msgid-missing>

On Thursday 31 July 2003 10:00, Martin A. Brown wrote:
> Well....(you'll love this) the reason everyone is saying "you can't shape
> incoming traffic" is because you can't shape incoming traffic (without
> IMQ).

Well, i shape incoming traffic without IMQ (:
I made my bandwidth.manager is on top of every router in my organization, so 
every traffic coming or leaving my organization must be processed by my 
bandwidth.manager first.. 

> Well, in short, what we're really saying is that you can't control what
> you receive (without IMQ).  As the recipient of frames/packets, you have
> no control over how fast they arrive in your device's input queue.

In my bandwidth.manager eth0 would be upgoing packet that needs to be manage, 
while eth1 would be the incoming packet to my LAN network.

Regards,
Rio Martin.
-- 
Game of love, we play, we win only to loose.

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

  parent reply	other threads:[~2003-07-31  3:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 23:45 [LARTC] shaping incoming with ingress Damion de Soto
2003-07-31  3:00 ` Martin A. Brown
2003-07-31  3:55 ` Rio Martin. [this message]
2003-07-31  5:50 ` smohan
2003-07-31  9:46 ` Stef Coene
2003-07-31  9:46 ` Stef Coene
2003-07-31  9:56 ` Rio Martin.
2003-07-31 11:34 ` Stef Coene

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-105962350319121@msgid-missing \
    --to=rio@martin.mu \
    --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.