netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denys Fedoryshchenko <denys@visp.net.lb>
To: netdev@vger.kernel.org
Subject: 802.1p, skb->priority, CoS for transit traffic not working?
Date: Sun, 5 Oct 2008 19:35:56 +0300	[thread overview]
Message-ID: <200810051935.56616.denys@visp.net.lb> (raw)

I'm trying to set CoS tag, to manage priorities on my microwave link.
Possible such setup will be very useful also to set classify traffic passing 
QoS. A lot of hardware support this simple L2 QoS.

Hardware: RTL8139, since it doesn't have VLAN tags acceleration, i can use 
tcpdump to see priority flag.

Commands i did to setup test VLAN, 

vconfig add eth2 10
ifconfig eth2.10 3.3.3.3 netmask 255.255.255.0
vconfig set_egress_map eth2.10 1 1
vconfig set_egress_map eth2.10 2 2
vconfig set_egress_map eth2.10 3 3
vconfig set_egress_map eth2.10 4 4 

First, i made it works locally, with Patrick McHardy patch
http://marc.info/?l=lartc&m=101914368423554&w=2

Source PC: ping -P 2 3.3.3.1

Destination PC:
19:31:21.738317 00:0a:cd:14:6b:6f > 00:05:5d:2f:9b:ba, ethertype 802.1Q 
(0x8100), length 102: vlan 10, p 2, ethertype IPv4, (tos 0x0, ttl 64, id 0, 
offset 0, flags [DF], proto ICMP (1), length 84) 3.3.3.3 > 3.3.3.1: ICMP echo 
request, id 62505, seq 15, length 64
19:31:22.738376 00:0a:cd:14:6b:6f > 00:05:5d:2f:9b:ba, ethertype 802.1Q 
(0x8100), length 102: vlan 10, p 2, ethertype IPv4, (tos 0x0, ttl 64, id 0, 
offset 0, flags [DF], proto ICMP (1), length 84) 3.3.3.3 > 3.3.3.1: ICMP echo 
request, id 62505, seq 16, length 64
19:31:23.738398 00:0a:cd:14:6b:6f > 00:05:5d:2f:9b:ba, ethertype 802.1Q 
(0x8100), length 102: vlan 10, p 2, ethertype IPv4, (tos 0x0, ttl 64, id 0, 
offset 0, flags [DF], proto ICMP (1), length 84) 3.3.3.3 > 3.3.3.1: ICMP echo 
request, id 62505, seq 17, length 64

But next step is to manage traffic over iproute2. Sure it is not clear for me 
how it works, and for example i am feeling prio qdisc is not thing i need, at 
all.
I've tried , smth like this (not sure how it was, but on stats it was showing 
packets hit filter).

tc qdisc del dev eth2.10 root
tc qdisc add dev eth2.10 root handle 1: prio
/sbin/tc filter add dev eth2.10 parent 1:0 protocol all u32 match u32 0 0 
classid 1:3



And i try even new Intel patch, "action skbedit", it works on stats, but 
doesn't set anything. I try ingress(on incoming interface) and egress 
(outgoing).

tc qdisc del dev eth2.10 root
tc qdisc add dev eth2.10 root handle 1: prio
/sbin/tc filter add dev eth2.10 parent 1:0 protocol all u32 match u32 0 0 
action skbedit queue_mapping 2

and ingress
tc qdisc del dev eth0 ingress
tc qdisc add dev eth0 ingress
tc filter add dev eth0 parent ffff: protocol all u32 match u32 0 0 action 
skbedit queue_mapping 3

Is there a way to make work changing transit packets 802.1p values?


             reply	other threads:[~2008-10-05 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-05 16:35 Denys Fedoryshchenko [this message]
2008-10-05 16:56 ` 802.1p, skb->priority, CoS for transit traffic not working? Patrick McHardy
2008-10-05 19:03   ` Denys Fedoryshchenko

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=200810051935.56616.denys@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).