On Wed, 24 Mar 2004, MihaiV wrote:
> Citez din lartc.org cap 9.6
> "
>
> root 1:
> |
> _1:1_
> / | \
> / | \
> / | \
> 10: 11: 12:
> / \ / \
> 10:1 10:2 12:1 12:2
>
> When enqueueing a packet, at each branch the filter chain is consulted
> for a relevant instruction. A typical setup might be to have a filter in
> 1:1 that directs a packet to 12: and a filter on 12: that sends the
> packet to 12:2.
> "
> iar un pic mai jos:
>
> "Also, with HTB, you should attach all filters to the root!"
>
> Nu e contradictie acolo ? Sus zice ca pot pune filtre si pe 1:1 si pe
> 12: , iar jos zice ca pot pune doar pe root.
Ei initial se refera la cazul general, dar in particular HTB3 nu
verifica filtrele decat cele din root, asta-i tot (dar CBQ de exemplu nu
face asa).
Deci nu e contradictie, ci HTB e exceptie de la regula.
> Si inca o intrebare: care e diferenta intre
>
> tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \
> ip dport 22 0xffff flowid 10:1
> si
> tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \
> ip dport 22 0xffff classid 10:1
>
> adica la unele filtre am classid x:y , iar la altele am flowid x:y
Conform iproute2/tc/f_u32.c pare sa fie sinonime:
} else if (matches(*argv, "classid") == 0 ||
strcmp(*argv, "flowid") == 0) {
unsigned handle;
NEXT_ARG();
if (get_tc_classid(&handle, *argv)) {
fprintf(stderr, "Illegal \"classid\"\n");
return -1;
}
addattr_l(n, 4096, TCA_U32_CLASSID, &handle, 4);
sel.sel.flags |= TC_U32_TERMINAL;
} else if (matches(*argv, "divisor") == 0) {
> --
> Mihai Voica
--
Mihai RUSU Email: [EMAIL PROTECTED]
GPG : http://dizzy.roedu.net/dizzy-gpg.txt WWW: http://dizzy.roedu.net
"Linux is obsolete" -- AST
---
Detalii despre listele noastre de mail: http://www.lug.ro/
