Re: [LARTC] shaping incoming with ingress

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thursday 31 July 2003 05:55, Rio Martin. wrote:
> 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..
If I understand correctly, you have 1 router with 2 nics.  So you shape 
incoming traffic on nic1 by shaping outgoing traffic on nic2.  This is fine 
for your setup, but if you 3 nic's and you are running some services on the 
router, you will have a problem.

> > 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.

-- 

stef.coene@xxxxxxxxx
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net



[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux