From: Stephen Hemminger <stephen@networkplumber.org>
To: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Cc: netdev@vger.kernel.org, Jamal Hadi Salim <jhs@mojatatu.com>,
Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH v2 iproute2 net-next] tc: m_vlan: Add vlan modify action
Date: Sun, 9 Oct 2016 19:12:06 -0700 [thread overview]
Message-ID: <20161009191206.401b10ad@xeon-e3> (raw)
In-Reply-To: <1474567265-3397-1-git-send-email-shmulik.ladkani@gmail.com>
On Thu, 22 Sep 2016 21:01:05 +0300
Shmulik Ladkani <shmulik.ladkani@gmail.com> wrote:
> The 'vlan modify' action allows to replace an existing 802.1q tag
> according to user provided settings.
> It accepts same arguments as the 'vlan push' action.
>
> For example, this replaces vid 6 with vid 5:
>
> # tc filter add dev veth0 parent ffff: pref 1 protocol 802.1q \
> basic match 'meta(vlan mask 0xfff eq 6)' \
> action vlan modify id 5 continue
>
> Signed-off-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Applied to net-next (for 4.9)
prev parent reply other threads:[~2016-10-10 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 18:01 [PATCH v2 iproute2 net-next] tc: m_vlan: Add vlan modify action Shmulik Ladkani
2016-10-10 2:12 ` Stephen Hemminger [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=20161009191206.401b10ad@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=shmulik.ladkani@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.