All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Brad Pousland <bpousland@izuma.net>
Cc: netfilter@vger.kernel.org
Subject: Re: setting meta priority to select link vlan qos 802.1q priority via egress map
Date: Wed, 11 May 2016 22:49:06 +0200	[thread overview]
Message-ID: <20160511204906.GA24369@salvia> (raw)
In-Reply-To: <CAGBdaZ=9bcechsjddxbcFZJGTv7UpkTSi22stnWBnyAsOvxHjw@mail.gmail.com>

On Wed, May 11, 2016 at 03:07:42PM -0500, Brad Pousland wrote:
> It appears to be a bug with the nftables userspace utility nft. I
> wrote a program to decode nftables rules and found the nft utility is
> trying to fill the BPF data register with the priority value in
> big-endian format.  If I hack it to use little-endian format for the
> meta value, the skb->priority is set appropriately.

Could you pass your hack so we can have a look?

Thanks!

  reply	other threads:[~2016-05-11 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 17:13 setting meta priority to select link vlan qos 802.1q priority via egress map Brad Pousland
2016-05-11 20:07 ` Brad Pousland
2016-05-11 20:49   ` Pablo Neira Ayuso [this message]
2016-05-11 21:56     ` Brad Pousland

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=20160511204906.GA24369@salvia \
    --to=pablo@netfilter.org \
    --cc=bpousland@izuma.net \
    --cc=netfilter@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.