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] HTB burstable for 2 interface , how ?
Date: Thu, 03 Jul 2003 09:50:21 +0000	[thread overview]
Message-ID: <marc-lartc-105722627304754@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105722285902235@msgid-missing>

On Thursday 03 July 2003 11:38, rio@martin.mu wrote:
> It wont work..
> eth0 only for public ip traffic. It wont handle private network traffic.
> Traffic to private network can be manage through eth1 & eth2
>
> I guess the answer is IMQ .. i'll try ..
> Documentation please, or perhaps docum.org already have documentation
> regarding IMQ ?
Not much.  I never had the time to try imq my self.  But it's easy.  
With imq you can create virtual devices and you can redirect any traffic to 
with iptables.  So you can redirect all incoming traffic to eth0 to the 
virutal device.  Shaping the traffic can be done by adding a htb qdisc to the 
imq device.  But in your case you will have a filter problem because you 
don't know the src address when a packet enter eth0.

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:[~2003-07-03  9:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03  8:56 [LARTC] HTB burstable for 2 interface , how ? rio
2003-07-03  9:12 ` Stef Coene
2003-07-03  9:12 ` ???????? ?????
2003-07-03  9:18 ` Martin Devera
2003-07-03  9:38 ` rio
2003-07-03  9:50 ` Stef Coene [this message]
2003-07-03 11:45 ` Joel
2003-07-04 16:39 ` Don Cohen
2003-07-07  3:54 ` Leonardo Balliache
2003-07-09  3:22 ` Leonardo Balliache

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