All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ not properly functioning !?
Date: Fri, 01 Nov 2002 08:56:35 +0000	[thread overview]
Message-ID: <marc-lartc-103614106217987@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103609384708269@msgid-missing>

On Friday 01 November 2002 00:07, Robert Felber wrote:
> On Thu, Oct 31, 2002 at 11:50:28PM +0100, thomas bilke wrote:
> > Yes, the host is in my LAN. But I want to shape the incoming and outgoing
> > traffic corresponding to this host, or later to the whole LAN. Doesn't
> > exist any facility to shape the incoming traffic?
> >
> > Thomas
>
> Yes, the qdisc ingress is exactly developed for one purpose: shape
> incomming traffic.
Ingress will not shape the incoming traffic, but if you use filters+policers 
you can drop packets that exceed a certain rate.  That's not the same as you 
can do with cbq for the outgoin packets.

> You can both, the CBQ and ingress qdisc, use at the same time for
> a device (yes, also real eth devices).

You have something like this :

LAN --- eth1 --- linux box --- eth0 --- ISP

If you add a cbq qdisc on eth0, this will shape the packets going to your ISP.  
So in the filter statement you need the src address of the host in the LAN.  
But be aware that if you are natting on that box, you don't know the src 
address anymore (the src address is natted to the address of the linux-box).  
You can solve this issue with iptables + fw filter : mark the packets when 
they enter the box at eth1 and use that to filter mark on eth0.

For the incoming bandwidth, you can use the ingress qdisc and filters with 
policer.  If you add a ingress qdisc, you can add filters with policers.  
Each policer is a sort of tbf with a certain rate.  Packets that exceed that 
rate are dropped.  So you can control the incoming packets.

An other trick is using a imq device or shaping on eth1 if the linux box is 
only a router so all packets entering eth0 are leaving eth1.

Stef


-- 

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

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

      parent reply	other threads:[~2002-11-01  8:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 19:52 [LARTC] CBQ not properly functioning !? thomas bilke
2002-10-31 20:12 ` Stef Coene
2002-10-31 20:32 ` thomas bilke
2002-10-31 21:35 ` Stef Coene
2002-10-31 21:52 ` Robert Felber
2002-10-31 22:14 ` Stef Coene
2002-10-31 22:50 ` thomas bilke
2002-10-31 23:07 ` Robert Felber
2002-11-01  8:56 ` Stef Coene [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=marc-lartc-103614106217987@msgid-missing \
    --to=stef.coene@docum.org \
    --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.