From: "GoMi" <gomiuk@hotmail.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Lots amounts of classes to solve the DAP problem
Date: Thu, 24 Apr 2003 14:12:28 +0000 [thread overview]
Message-ID: <marc-lartc-105119362314335@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105103510025149@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there stef, since it does not work with the set up i sent you, i am thinking in changing the qdiscs to esfq. I will try that today and see what happens. Another question.. With the scripts i sent to the mailing list, there is an enormous amount of rules in the PREROUTING mangle section. Since each user has 1 class and those classes 2 marks to distinguish between interactive and noninteractive traffic. Thats more than 500 entries. I am not sure if thats a bit "too mutch" so i thought adding filters on eth0 and eth2 in the root qdisc and then based on the src address send it to the class, and there have tc filtres based on marks, that way i would have 250 filters on the root chain to a their class, and then 2 more filters in each class, having only 2 -J MARK entries in the mangle chain to mark pachets. The problem is i am doing SNAT and the EGRESS QDISC is applied after the SNAT so the tc filter based on src address do not work at all. Any idea how to solve that?
- -----Mensaje original-----
De: Stef Coene [mailto:stef.coene@docum.org]
Enviado el: miércoles, 23 de abril de 2003 22:29
Para: GoMi
CC: lartc@mailman.ds9a.nl
Asunto: Re: [LARTC] Lots amounts of classes to solve the DAP problem
On Wednesday 23 April 2003 14:45, GoMi wrote:
> I have finally worked a solution for egress traffic, but now i am a
> bit troubled with ingress with IMQ due to SNAT Here is my script, i
> have tried lots of combinations but with IMQ, the filters do not
> filter to the classes at all. I am pretty sure its because of the SNAT
> i am doing. Any one nows how to work around this problem?
So the filters for the eth2 device are working?
Mhh. You put all packets leaving eth3 in the imq1 device? Why not shaping on
the eth3 device???
I have some other remarks. You will get some warnings in your kernel log
about quantum too low. That's because you have 1kbit rate. You can solve
this by specifying a quantum if you add the htb class. The minimum quantum
is MTU bytes.
Also the pfifo. I'm not sure how and if this will work. It's possbile that
the default size of the pfifo is too small.
I snipped your almost perfect script to save some bandwidth :)
> ip link set ${IDEV} up
> ip link set ${DEV} txqueue 30
I'm not sure if this is going to change anything. As fas as I can remember,
you replaced the default queue with something else so the inital depth of
that queue doesn't mather anymore.
Stef
- --
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0
iQA/AwUBPqfwy37diNnrrZKsEQK8VgCeMeBT6yB4P7yRzXjPNxJOtelmLX8AnAmP
W2MMkuC/CU2KeqiK+dHx8MSG
=Hy+u
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-24 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 18:10 [LARTC] Lots amounts of classes to solve the DAP problem GoMi
2003-04-22 18:52 ` Stef Coene
2003-04-22 18:58 ` GoMi
2003-04-22 19:06 ` Stef Coene
2003-04-23 12:45 ` GoMi
2003-04-23 20:28 ` Stef Coene
2003-04-23 21:05 ` GoMi
2003-04-24 14:12 ` GoMi [this message]
2003-04-25 20:53 ` Stef Coene
2003-04-26 3:39 ` Rio Martin.
2003-04-26 4:50 ` Paul Evans
2003-04-26 8:01 ` Stef Coene
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-105119362314335@msgid-missing \
--to=gomiuk@hotmail.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 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.