Title: Message
PLEASE DO NOT SEND ME ANY NEW E-MAIL with (LARTC) in the subject
body.
Regards!
[EMAIL PROTECTED]
Hi,
Thanks for your reply.
Does it mean that "fw" has implemented hashing
implicitly??
Suppose I've the following fitler rules:
tc filter add dev eth0 parent 1: protocol ip prio 3
handle 1 fw
tc filter add dev eth0 parent 1: protocol ip prio 3
handle 2 fw
tc filter add dev eth0 parent 1: protoc
Arindam Haldar wrote:
> hi Alex,
> thanx so much.. :) .. thanx to all
> my IMQ & htb3 test rules are working ok.. the best part--> imq handling
> both in & out traffic now.. :)
I also had this setup, and i also thought of it as a "cool thing" :)
but then Patrick told me, that it's not so cleve
Hello!
Sorry for ugly english.
I was sеtup rules to limit outgoing HTTP traffic :
$TC qdisc add dev $DEVA root handle 1: htb default 30
$TC class add dev $DEVA parent 1: classid 1:1 htb rate 100mbit ceil 100mbit burst 15k
#HTTP 49Mbit
$TC class add dev $DEVA parent 1:1 classid 1:10 htb rate 49mb
On Monday 12 August 2002 22:19, Claudio Aznar wrote:
> I have in the kernel configuration the option
> Network device support --->IMQ (intermediate queueing device) support
> But not the other options... To activate this option is sufficient ?
If you only want to enable the imq device, that
I have in the kernel configuration the option
Network device support --->IMQ (intermediate queueing device) support
But not the other options... To activate this option is sufficient ?
CA
On Mon, 12 Aug 2002 21:59:17 +0200
Stef Coene <[EMAIL PROTECTED]> wrote:
> On Monday 12 August 20
> I wonder if this is true. Shouldn't one rather use iptables -t mangle -A
> PREROUTING -i eth0 -j IMQ at the end (after the other rules) ? Otherwise
> everyting from eth0 will go right to target IMQ and the other rules are
> never executed, i.e. the desired packets are never marked and all the
>
On Monday 12 August 2002 21:48, Claudio Aznar wrote:
> Hello list,
> I'm try to compile the new versión of Kernel (2.4.18) for IMQ support, and
> I don't find this option:
> Networking options ---> IP: Netfilter Configuration --->IMQ target support
> Networking options ---> IPv6: Netfilt
>Messsage du 10/08/2002 00:10
>De : Wayne de Nobrega <[EMAIL PROTECTED]>
>A : <[EMAIL PROTECTED]>
>Copie à :
>Objet : [LARTC] Managing Inbound Traffic
>
> I have been playing around with traffic shaping using htb and imq but am
> battling to get any control over the inbound traffic. Managing the
Hello list,
I'm try to compile the new versión of Kernel (2.4.18) for IMQ support, and I
don't find this option:
Networking options ---> IP: Netfilter Configuration --->IMQ target support
Networking options ---> IPv6: Netfilter Configuration --->IMQ target
support
... is on SourceForge, http://tcng.sourceforge.net/#src
This is a maintenance release. Highlights:
- value << 0 was broken, oops
- build process is compatible with the final release of 2.4.19
- make tcsim-rpms is now much better at finding sources. In
particular, it will happily accept any
Arkadiusz Miskiewicz <[EMAIL PROTECTED]> writes:
> Hi,
>
> The problem is: I have PPPoE (ppp over eth) server and 100 clients.
> For each client new pppX interface is created.
>
> Now I want to limit max speed on each interface to different
> values. For example
> ppp0 - downstream 256kbit, ups
Hi
The downloadable mail archive is missing everything from 10/5 to 30/6:
http://mailman.ds9a.nl/pipermail/lartc/2002q2.txt.gz
Could someone fix this?
Thanks
Lars Munch
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinf
> 1.
> tc filter add dev eth1 protocol ip perent 1:0 \
> prio 5 u32 ht 800:: \
> match ip src 1.2.0.0/16 \
> hashkey mask 0x00ff at 12 \
> link 2:
>
> It seems that the hashkey make can only applied to ip
> header. How can I use the marked number in a packet
> (using iptables) as the hashkey??
Hi,
I've been working on hashing in tc for a month. Since
there are only a limited number of avaialbe example on
hashing, I'll be appreciate if someone can my
questions as follows:
1.
tc filter add dev eth1 protocol ip perent 1:0 \
prio 5 u32 ht 800:: \
match ip src 1.2.0.0/16 \
hashkey mask 0x0
15 matches
Mail list logo