[LARTC] egress bandwidth not limited / limitedextremely inaccurately

[Nikolay Kichukov]

Cheers Andy,
That clarifies;-)

Regards,
-nik

Andy Furniss wrote:
> Nikolay Kichukov wrote:
>> Hello Andy,
>> How do one create such a filter to catch arp/other link layer traffic? 
>> Can
>> you give us one such example?
> 
> A quick test on ingress
> 
> #tc qdisc add dev eth0 ingress
> 
> Classify all ip traffic
> 
> #tc filter add dev eth0 parent ffff: prio 1 protocol ip u32 match u32 0 
> 0 flowid :1
> 
> All arp
> 
> #tc filter add dev eth0 parent ffff: prio 2 protocol arp u32 match u32 0 
> 0 flowid :2
> 
> Anything else
> 
> #tc filter add dev eth0 parent ffff: prio 3 protocol all u32 match u32 0 
> 0 flowid :3
> 
> Look at the counters
> 
> #tc -s filter ls dev eth0 parent ffff:
> 
> Delete everything ingress on eth0
> 
> #tc qdisc del dev eth0 ingress
> 
> 
> You can use ethertype protocol numbers in place of arp/ip.
> Use the prio to make sure the catch alls are last in the filters you use 
> - prio 1 is the highest for filters.
> 
> Andy.
>