From: Stephen Hemminger <stephen@networkplumber.org>
To: Amir Vadai <amir@vadai.me>
Cc: netdev@vger.kernel.org, Or Gerlitz <ogerlitz@mellanox.com>,
Jamal Hadi Salim <jhs@mojatatu.com>
Subject: Re: [PATCH iproute2 net 0/8] tc/act_pedit: Support offset relative to conventional header
Date: Mon, 1 May 2017 09:26:25 -0700 [thread overview]
Message-ID: <20170501092625.30274bee@xeon-e3> (raw)
In-Reply-To: <20170423125356.1298-1-amir@vadai.me>
On Sun, 23 Apr 2017 15:53:48 +0300
Amir Vadai <amir@vadai.me> wrote:
> Hi Stephen,
>
> This patchset extends pedit to support modifying a field in an offset relative
> to the conventional network headers (kenrel support was added [1] in 4.11 rc1).
> Without the extended pedit, user could specify fields in TCP and ICMP headers,
> but the kernel code was using an offset relative to the begining of the IP
> header. This will break if IP header length is greater than the minimal value
> of 20, or if L3 is not IPv4.
>
> It also introduces support in manipulating ETH, TCP, UDP and IP.ttl fields and
> a new command to increase/decrease the value of a field (current use case is IP.ttl).
>
> Since there might be deployments already using pedit, special consideration was
> taken, not to break those scripts - only by specifying the special keyword
> 'ex', the extended capabilities are available, thus there should be no impact
> on existing scripts.
> Also, the new code can live together with rules added by the old code. It
> supports both the old netlink and the new one.
>
> This patchset is against the master and not net-next as the functionality was
> added in 4.11
>
> Thanks,
> Amir
>
> [1] - 71d0ed7079df ("net/act_pedit: Support using offset relative to the
> conventional network headers")
>
> Amir Vadai (7):
> tc/pedit: Fix a typo in pedit usage message
> tc/pedit: Extend pedit to specify offset relative to mac/transport
> headers
> tc/pedit: Introduce 'add' operation
> tc/pedit: p_ip: introduce editing ttl header
> tc/pedit: Support fields bigger than 32 bits
> tc/pedit: p_eth: ETH header editor
> tc/pedit: p_tcp: introduce pedit tcp support
>
> Or Gerlitz (1):
> tc/pedit: p_udp: introduce pedit udp support
>
> man/man8/tc-pedit.8 | 126 +++++++++++++++++++++--
> tc/Makefile | 1 +
> tc/m_pedit.c | 290 ++++++++++++++++++++++++++++++++++++++++++++++------
> tc/m_pedit.h | 44 ++++++--
> tc/p_eth.c | 72 +++++++++++++
> tc/p_icmp.c | 3 +-
> tc/p_ip.c | 21 +++-
> tc/p_tcp.c | 40 +++++++-
> tc/p_udp.c | 30 +++++-
> 9 files changed, 572 insertions(+), 55 deletions(-)
> create mode 100644 tc/p_eth.c
>
Applied. Then I cleaned up long lines
next prev parent reply other threads:[~2017-05-01 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 12:53 [PATCH iproute2 net 0/8] tc/act_pedit: Support offset relative to conventional header Amir Vadai
2017-04-23 12:53 ` [PATCH iproute2 net 1/8] tc/pedit: Fix a typo in pedit usage message Amir Vadai
2017-04-23 12:53 ` [PATCH iproute2 net 2/8] tc/pedit: Extend pedit to specify offset relative to mac/transport headers Amir Vadai
2017-05-01 16:21 ` Stephen Hemminger
2017-04-23 12:53 ` [PATCH iproute2 net 3/8] tc/pedit: Introduce 'add' operation Amir Vadai
2017-04-23 17:44 ` Jamal Hadi Salim
2017-04-24 7:52 ` Amir Vadai
2017-04-24 11:04 ` Or Gerlitz
2017-04-23 12:53 ` [PATCH iproute2 net 4/8] tc/pedit: p_ip: introduce editing ttl header Amir Vadai
2017-04-23 12:53 ` [PATCH iproute2 net 5/8] tc/pedit: Support fields bigger than 32 bits Amir Vadai
2017-04-23 12:53 ` [PATCH iproute2 net 6/8] tc/pedit: p_eth: ETH header editor Amir Vadai
2017-04-23 12:53 ` [PATCH iproute2 net 7/8] tc/pedit: p_tcp: introduce pedit tcp support Amir Vadai
2017-04-23 12:53 ` [PATCH iproute2 net 8/8] tc/pedit: p_udp: introduce pedit udp support Amir Vadai
2017-05-01 16:26 ` Stephen Hemminger [this message]
2017-05-03 6:27 ` [PATCH iproute2 net 0/8] tc/act_pedit: Support offset relative to conventional header Amir Vadai
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=20170501092625.30274bee@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=amir@vadai.me \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.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.