All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: Re: 802.1p, skb->priority, CoS for transit traffic not working?
Date: Sun, 5 Oct 2008 22:03:37 +0300	[thread overview]
Message-ID: <200810052203.37436.denys@visp.net.lb> (raw)
In-Reply-To: <48E8F1A3.3070900@trash.net>

On Sunday 05 October 2008, Patrick McHardy wrote:
> Denys Fedoryshchenko wrote:
> > 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.
> >
> > [...]
> > Is there a way to make work changing transit packets 802.1p values?
>
> Bridging traffic to a VLAN device should work, you can then
> define the priority for the device. I'm not aware of an easier
> method, but I believe act_pedit should also be able to do this.

Seems my silly mistake, i used wrong option in skbedit (first which i seen in 
example). 
Thanks to Intel guys, now it is possible also by this way:

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 priority 3

So it is possible now to do 802.1p marking on router(not bridge), by u32 
filter or whatever.

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 priority 3

Like this it works


And thanks again, i am really impressed by opensource initiatives of Intel, 
and quality/performance/cost of their network products.

      reply	other threads:[~2008-10-05 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-05 16:35 802.1p, skb->priority, CoS for transit traffic not working? Denys Fedoryshchenko
2008-10-05 16:56 ` Patrick McHardy
2008-10-05 19:03   ` Denys Fedoryshchenko [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=200810052203.37436.denys@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=kaber@trash.net \
    --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 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.