From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andy Furniss <adf.lists@gmail.com>
Date: Wed, 03 Jul 2013 22:49:50 +0000
Subject: Re: question about traffic control in for input (ingress) traffic
Message-Id: <51D4AA8E.9090905@gmail.com>
List-Id: <lartc.vger.kernel.org>
References: <CAGXs5wXUOenZZSHC3NVLS=AQELS8158e7rs9shbXph01=Qy8sA@mail.gmail.com>
In-Reply-To: <CAGXs5wXUOenZZSHC3NVLS=AQELS8158e7rs9shbXph01=Qy8sA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

Kevin Wilson wrote:
> Hello,
> I know that traffic control is usually used for output.
> I want to learn  traffic control kernel implementation for input
> (ingress) traffic
> I made several tries with the tc userspace tool to add
> traffic control entries, but I did not succeed.

You can only add filters/policers to ingress, if you want to shape you 
have to use the ifb device and redirect traffic to it with a filter.

eg.

modprobe ifb
tc qdisc add dev eth0 ingress
ip link set ifb0 up

tc filter add dev eth0 parent ffff: \
protocol ip prio 10 u32 match u32 0 0 flowid 1:0 \
action mirred egress redirect dev ifb0

Then you add normal qdiscs etc to ifb0 just like you would for output.