netdev - Meaning of "handle" when using tc filter ... flow hash

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sun, 20 Nov 2011 09:00:41 +0000
From:	Andrew Beverley <andy@...ybev.com>
To:	netdev@...r.kernel.org
Subject: Meaning of "handle" when using tc filter ... flow hash

Hi,

I've been using the "flow hash keys" feature of tc to evenly distribute
bandwidth across client IP addresses.

In order to get it to work, I have to specify a "handle" value:

$TC filter add dev eth0 parent 4101: protocol ip \
	handle 10 flow hash keys dst divisor 1024

         ^^^^

However, the handle doesn't seem to do anything. No matter what value I
specify, the rule works. If I leave it out, I get an "RTNETLINK answers:
Invalid argument" error.

I would normally expect the handle parameter to specify a netfilter mark
value. In this case though, it doesn't seem to make any difference. Is
there a reason that it needs to be specified?

Thanks,

Andy

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html