From: Patrick McHardy <kaber@trash.net>
To: Bhanu CV <vbhanu.mailinglists@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: How does iptables classify change skb priority
Date: Tue, 01 Feb 2011 17:36:27 +0100 [thread overview]
Message-ID: <4D48368B.6050906@trash.net> (raw)
In-Reply-To: <AANLkTimK=LsDOGJGFSFNxH_zC-zDWv=Z3FpLZAPt1g0E@mail.gmail.com>
Am 01.02.2011 17:31, schrieb Bhanu CV:
> Hi,
>
> I am trying to change the skb priority of the packets going out to a
> particular destination. Then I use vlan set_egress_map to change the
> vlan priority of the packet. This works as I want it to, the confusing
> part is I do not know why it works!
>
> I use the following two commands:
>
> change the skb->priority (?) for the packets that I am interested in to 3:
> iptables -t mangle -A POSTROUTING -d 192.168.10.75 -j CLASSIFY --set-class 0:3
>
> change the vlan priority of the packet leaving over the vlan
> vconfig set_egress_map eth4.2 3 3
>
> This does send a packet on the wire with MAC layer priority of 3,
> which is what I want. What I am trying to understand is the action
> that iptables is taking. I do not have any class under the root qdisc
> on eth4. The root qdisc has handle 0:
>
> It would be great if someone could explain how iptables is classifying
> the packet in a way which changes the skb->priority of the packet.
It simply changes the skb->priority value, which used by the VLAN
driver to map to VLAN proprities. This is done by the VLAN driver
internally and unrelated to qdiscs.
next prev parent reply other threads:[~2011-02-01 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 16:31 How does iptables classify change skb priority Bhanu CV
2011-02-01 16:36 ` Patrick McHardy [this message]
2011-02-01 18:10 ` Bhanu CV
-- strict thread matches above, loose matches on Subject: below --
2011-01-28 18:34 Bhanu CV
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=4D48368B.6050906@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=vbhanu.mailinglists@gmail.com \
/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.