Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Cow" <cow@gline.us>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB problem...
Date: Tue, 07 Sep 2004 21:18:24 +0000	[thread overview]
Message-ID: <002f01c49520$35916670$6e1464ab@palle> (raw)
In-Reply-To: <001301c4945c$53c79f70$6e1464ab@palle>

>by zytek
>Hello all, my first post here, maybe even I will help someone;)

>I assume that you want somethink like:
>data from server to LAN (PC1,PC2) unshaped (full 100mbit)
>data from Internet to LAN shaped

Correct.

>Then all you need to do is make classes with source 192.168.0.1 and
>destination 192.168.0.2(3) and 100mbit rate and then make classes with
>destination 192.168.0.2(3) with download rate. I believe that you
understand
>what I am thinkig of.

I do, but could you write an example please, so i have something to make
it from? :-)

>Or you can use iptables and mark traffic going from server to LAN, and
other
>mark for traffic in FORWARD chain. (iptables -t mangle -A FORWARD -j
MARK
>--set-mark SOME_MARK)
>When using iptables you will be able to shape upload speed, just mark
traffic
>in forward going from PC1/2 with output interface eth2 (-o eth2) - it
will be
>hosts upload.

Again, an example would be nice.. i have no idea on how to use MARK
command with iptables, even i know a great deal about iptables in
general.

>I won't write you full script, make it yourself, visit LARTC and
firstly try
>"htb.init" for simple class creation. Good fun!

Fair enough, i wouldn't exspect anyone to write a full script for me,
but i would exspect someone to make me an example for instance, how i
can shape PC1's download/upload rate to 256/128 KBit, so i atleast have
something to help me going.

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

  parent reply	other threads:[~2004-09-07 21:18 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-06 21:56 [LARTC] HTB problem Cow
2004-09-07 11:08 ` zytek
2004-09-07 20:28 ` Cow
2004-09-07 21:16 ` [LARTC] HTB Problem Cow
2004-09-07 21:18 ` Cow [this message]
2004-09-07 21:53 ` [LARTC] HTB problem Andreas Klauer
  -- strict thread matches above, loose matches on Subject: below --
2001-12-11  2:46 yangrunhua
2001-12-11  9:21 ` bert hubert
2001-12-11  9:34 ` yangrunhua
2001-12-11  9:35 ` yangrunhua
2001-12-11 11:10 ` bert hubert
2001-12-12  5:47 ` yangrunhua
2001-12-12 10:02 ` yangrunhua
2001-12-12 11:40 ` Martin Devera
2001-12-12 13:50 ` bert hubert
2001-12-12 23:48 ` yangrunhua
2001-12-13 10:07 ` bert hubert
2002-06-26  0:22 ` [LARTC] htb problem Omar Armas
2002-06-26  0:32 ` Tomasz Wrona
2002-12-09 18:19 ` [LARTC] HTB Problem lartc
2002-12-09 18:57 ` Stef Coene
2003-01-23 22:47 ` [LARTC] HTB problem Jay Wineinger
2003-01-24  2:15 ` mingching.tiew
2003-01-24  2:39 ` Jay Wineinger
2003-06-12 19:21 ` [LARTC] htb problem Ratel
2003-06-12 19:23 ` Esteban
2003-06-12 19:35 ` Stef Coene
2003-06-12 20:04 ` Morten Isaksen
2003-06-12 20:51 ` Stef Coene
2003-06-12 20:54 ` Stef Coene
2003-06-12 21:15 ` Stef Coene
2003-06-14 21:46 ` terahz
2003-06-15 18:14 ` Stef Coene
2003-06-25 11:14 ` Ratel
2003-07-24 14:26 ` Delcho
2003-07-28 17:49 ` Stef Coene
2003-09-30 13:44 ` [LARTC] HTB Problem Guilherme Benkenstein
2003-09-30 19:59 ` Stef Coene
2003-12-02 23:08 ` [LARTC] HTB problem Mihai Tanasescu
2003-12-04  5:16 ` Mihai Tanasescu
2003-12-04  7:40 ` Catalin BOIE

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='002f01c49520$35916670$6e1464ab@palle' \
    --to=cow@gline.us \
    --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