Skip to contentSkip to conversation

egress bandwidth not limited /

LARTC Nikolay Kichukov 2 participants 3 messages Jan 18, 2007 – Jan 19, 2007

lore
Share & tools
lore
#0 lore raw

Hello Andy,
How do one create such a filter to catch arp/other link layer traffic? Can you give us one such example?

Thanks,
-nik

----- Original Message -----
From: "Andy Furniss" <[email protected]>
To: "Roman Skula" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, January 17, 2007 10:18 PM
Subject: Re: [LARTC] egress bandwidth not limited / limitedextremely inaccurately

Quoted 17 lines
Quoted 10 lines · Roman Skula

Andy Furniss napisa³(a):

Quoted 6 lines
Quoted 2 lines · Roman Skula

05:04.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5714 Gigabit Ethernet (rev a3)

You may need to turn off segmentation offload with ethtool -k

A huge, wet kiss for you, this turned my sky blue again. :)

Lol - I forgot to mention: be carefull about using htb default, your arp/other link layer end up there. If you don't specify a default htb will let them through unshaped, you can make a filter to catch the unclassified IP traffic and send it to the class you want.

Quoted 7 lines

Andy.

_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

#1 lore raw
Quoted 3 lines · Nikolay Kichukov

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
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

#2 lore raw
In reply to Nikolay Kichukov

Cheers Andy,
That clarifies;-)

Regards,
-nik

Quoted 31 lines · Andy Furniss
Quoted 4 lines · Nikolay Kichukov

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

Quoted 9 lines

#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
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc