netdev - Re: ingress policying for realtime protocol

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 20 May 2015 17:30:40 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Cong Wang <cwang@...pensource.com>
Cc:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>, netdev <netdev@...r.kernel.org>,
	Jamal Hadi Salim <jhs@...atatu.com>
Subject: Re: ingress policying for realtime protocol

On Wed, 2015-05-20 at 16:46 -0700, Cong Wang wrote:

> There is very little to do on ingress side since there is no queue at all,
> not to mention priority, you could try ifb to see if it fits your need.

Note that if the need is to police traffic, ifb is not really needed :

TC="tc"
DEV="dev eth0"
IP=10.246.11.51/32
$TC qdisc del $DEV ingress 2>/dev/null
$TC qdisc add $DEV ingress
$TC filter add $DEV parent ffff: protocol ip u32 match ip src $IP \
	police rate 1Mbit burst 10Mbit mtu 66000 action drop/continue

$TC -s filter ls $DEV parent ffff: protocol ip


--
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