Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andre Correa <andre.correa@pobox.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB
Date: Thu, 15 Jan 2004 12:12:11 +0000	[thread overview]
Message-ID: <4006839A.9060505@pobox.com> (raw)
In-Reply-To: <marc-lartc-101661742904753@msgid-missing>


Cristea, you are too vague in your question. I can tell you that you can 
shape MAN and WAN traffic separately using diferent classes and filters.

100Mbits for a single machine looks like too much traffic. Maybe you 
should divide load between more machines and have redundancy in your setup.

If this is not what you meant, please let us know...

Andre



Cristea Virgil Ionut wrote:
> Hi, I have the following questions:
> 
> I only have one htb computer (2 nics) to shape the international traffic 
> as well as the metropolitan traffic (i have a list of metropolitan ip's 
> to use). Can this be achived using iptables with packet marking (on that 
> htb computer the 2 nics are bridged)?
> If it can will there be delays introduced by the shaping operation (the 
> metropolitan link is a 100M fiber - full almost all the time)???
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 
> 

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

  parent reply	other threads:[~2004-01-15 12:12 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20  9:43 [LARTC] htb George Tsuladze
2002-03-20 12:20 ` Soulfly
2002-05-04 11:42 ` Stef Coene
2002-09-24 14:12 ` [LARTC] HTB Rimas
2002-09-24 14:12 ` Rimas
2002-09-24 14:17 ` Marc-Christian Petersen
2002-09-24 14:23 ` Esteban Maringolo
2002-09-24 14:30 ` Rimas
2002-09-24 14:55 ` Rimas
2002-09-24 15:00 ` Marc-Christian Petersen
2002-09-24 15:14 ` Rimas
2002-09-24 15:14 ` Rimas
2002-09-24 15:51 ` Esteban Maringolo
2002-09-24 16:16 ` Stef Coene
2002-09-25  4:27 ` mdew
2002-09-25  7:59 ` Stef Coene
2002-09-26 14:36 ` raptor
2002-11-08 13:45 ` Chandrashekhar Rane
2002-12-27 20:14 ` Reginald R. Richardson
2002-12-27 21:59 ` Stef Coene
2003-05-13 18:00 ` [LARTC] htb Evgeni Gechev
2003-05-13 18:34 ` Stef Coene
2003-05-13 19:03 ` Evgeni Gechev
2003-05-13 19:40 ` Stef Coene
2003-05-13 19:47 ` Evgeni Gechev
2003-05-13 19:53 ` Stef Coene
2003-05-13 20:47 ` Evgeni Gechev
2003-05-14 10:01 ` Stef Coene
2004-01-15  7:21 ` [LARTC] HTB Cristea Virgil Ionut
2004-01-15 12:12 ` Andre Correa [this message]
2004-04-09 23:09 ` Arturas Lapiene
2004-10-14 18:23 ` sistemas
2004-10-14 20:03 ` Jason Boxman
2004-10-17 11:44 ` [LARTC] htb James Lista
2004-10-17 12:08 ` James Lista
2004-10-17 12:19 ` Andreas Klauer
2004-10-17 12:41 ` James Lista
2004-10-17 12:53 ` ja
2004-10-17 13:02 ` James Lista
2004-10-17 13:20 ` Andreas Klauer
2004-10-17 13:22 ` Andreas Klauer
2004-11-10 14:48 ` [LARTC] HTB "Marcus Schäfer"
2007-06-10 16:27 ` Marco Aurelio
2007-06-11  8:09 ` m.innocenti
  -- strict thread matches above, loose matches on Subject: below --
2002-05-04  8:53 [LARTC] htb Anjaneya Pal
2002-05-04  8:56 ` Martin Devera

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=4006839A.9060505@pobox.com \
    --to=andre.correa@pobox.com \
    --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