Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "yangrunhua" <yangrunhua@njupt.edu.cn>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] HTB problem
Date: Wed, 12 Dec 2001 23:48:56 +0000	[thread overview]
Message-ID: <marc-lartc-100820085703788@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100803866815679@msgid-missing>

Thanks to everyone, my problem has been solved.
Here is my description:
for BIG ISP, if you have broadband for every client and use NAT_SRC to
let them out, and you want to divide bandwidth among all clients. My
solution is iproute2 + netfilter.
I've modified netfilter framework's src to hash every client (not like
originally,line by line) and also do some accounting based on flow, and
add a table(which hacks after NAT_SRC, not like mangle. Mangle hacks
before NAT_SRC), then mark the packets with it's classid related with
it's intra-network ipaddr, so the dev attached with filter fw with no
option will classify directly into the class with that classid, finally
control it's bandwidth(I use HTB).
Every step is O(1) in complexity. Excellent!
Thanks for all. Thanks for all the people here and from netfilter
mail-list.
Iproute2+ netfilter seems pretty good! I've got good performance!
I'm a new here, so very nice to hear from you, you are so kind.

-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]
On Behalf Of bert hubert
Sent: 2001Äê12ÔÂ12ÈÕ 21:51
To: Martin Devera
Cc: yangrunhua; lartc@mailman.ds9a.nl
Subject: Re: [LARTC] HTB problem

On Wed, Dec 12, 2001 at 12:40:57PM +0100, Martin Devera wrote:

> try replace 0x0001000a by 0x00010010. IIRC in 1:10
> the "10" is in hex.

True. Even the 1 is hex!

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
Trilab                                 The Technology People
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet

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


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

  parent reply	other threads:[~2001-12-12 23:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11  2:46 [LARTC] HTB problem 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2004-09-06 21:56 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 ` [LARTC] HTB problem Cow
2004-09-07 21:53 ` Andreas Klauer

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-100820085703788@msgid-missing \
    --to=yangrunhua@njupt.edu.cn \
    --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