From: Pravin Shelar <pravin.ovn@gmail.com>
To: Pravin B Shelar <pbshelar@fb.com>, Harald Welte <laforge@gnumonks.org>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jonas Bonn <jonas@norrbonn.se>, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next v5] GTP: add support for flow based tunneling API
Date: Wed, 13 Jan 2021 07:25:43 -0800 [thread overview]
Message-ID: <CAOrHB_Bc_WTY3AA-o7sUQ-ycVg6sUvHDjukRufyXkT43e3nn-A@mail.gmail.com> (raw)
In-Reply-To: <20210110070021.26822-1-pbshelar@fb.com>
Hi Harald,
On Sat, Jan 9, 2021 at 11:02 PM Pravin B Shelar <pbshelar@fb.com> wrote:
>
> Following patch add support for flow based tunneling API
> to send and recv GTP tunnel packet over tunnel metadata API.
> This would allow this device integration with OVS or eBPF using
> flow based tunneling APIs.
>
> Signed-off-by: Pravin B Shelar <pbshelar@fb.com>
> ---
> v4-v5:
> - coding style changes
> v3-v4:
> - add check for non-zero dst port
> v2-v3:
> - Fixed coding style
> - changed IFLA_GTP_FD1 to optional param for LWT dev.
> v1-v2:
> - Fixed according to comments from Jonas Bonn
>
This is the latest revision.
I have started with OVS integration, there are unit tests that
validate the GTP support. This is datapath related test, that has the
setup commands:
https://github.com/pshelar/ovs/blob/6ec6a2a86adc56c7c9dcab7b3a7b70bb6dad35c9/tests/system-layer3-tunnels.at#L158
Once OVS patches are upstream I can post patches for ip-route command.
Patch for iproute to add support for LWT GTP devices.
https://github.com/pshelar/iproute2/commit/d6e99f8342672e6e9ce0b71e153296f8e2b41cfc
next prev parent reply other threads:[~2021-01-13 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 7:00 [PATCH net-next v5] GTP: add support for flow based tunneling API Pravin B Shelar
2021-01-13 15:25 ` Pravin Shelar [this message]
2021-01-17 0:46 ` Jakub Kicinski
2021-01-17 13:23 ` Jonas Bonn
2021-01-17 15:25 ` Harald Welte
2021-01-17 20:55 ` Pravin Shelar
2021-01-17 20:47 ` Pravin Shelar
2021-01-18 17:27 ` Jakub Kicinski
2021-01-18 18:27 ` Jonas Bonn
2021-01-18 18:56 ` Jakub Kicinski
2021-01-18 20:01 ` Harald Welte
2021-01-17 13:40 ` Jonas Bonn
2021-01-17 20:42 ` Pravin Shelar
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=CAOrHB_Bc_WTY3AA-o7sUQ-ycVg6sUvHDjukRufyXkT43e3nn-A@mail.gmail.com \
--to=pravin.ovn@gmail.com \
--cc=jonas@norrbonn.se \
--cc=kuba@kernel.org \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=pbshelar@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).