From: Nikolay Kichukov <hijacker@oldum.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] egress bandwidth not limited /
Date: Fri, 19 Jan 2007 08:37:15 +0000 [thread overview]
Message-ID: <45B0833B.5090504@oldum.net> (raw)
In-Reply-To: <002a01c73ad8$50e43af0$0200a8c0@ccja>
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.
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-01-19 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 7:13 [LARTC] egress bandwidth not limited / Nikolay Kichukov
2007-01-18 23:26 ` Andy Furniss
2007-01-19 8:37 ` Nikolay Kichukov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45B0833B.5090504@oldum.net \
--to=hijacker@oldum.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.