From: Stephen Hemminger <stephen@networkplumber.org>
To: Tom Herbert <therbert@google.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 0/5] iproute: Add FOU and GUE configuration in ip
Date: Sun, 2 Nov 2014 11:46:09 -0800 [thread overview]
Message-ID: <20141102114609.6ba7f9d1@urahara> (raw)
In-Reply-To: <1412351718-22921-1-git-send-email-therbert@google.com>
On Fri, 3 Oct 2014 08:55:13 -0700
Tom Herbert <therbert@google.com> wrote:
> This patch set adds support in iproute2 to configure FOU and GUE ports
> for receive, and using FOU or GUE with ip tunnels (IPIP, GRE, sit) on
> transmit.
>
> A new ip subcommand "fou" has been added to configure FOU/GUE ports.
> For example:
>
> ip fou add port 5555 gue
> ip fou add port 9999 ipproto 4
>
> The first command creates a GUE port, the second creates a direct FOU
> port for IPIP (receive payload is a assumed to be an IP packet).
>
> To configure an IP tunnel to use FOU or GUE encap parameters have
> been added. For example:
>
> ip link add name tun1 type ipip remote 192.168.1.1 local 192.168.1.2 \
> ttl 225 encap gue encap-sport auto encap-dport 7777 encap-csum
> ip link add name tun2 type gre remote 192.168.1.1 local 192.168.1.2 \
> ttl 225 encap fou encap-sport auto encap-dport 8888 encap-csum
>
> The first command configures an IPIP tunnel to use GUE on transmit. The
> peer might be configured to receive GUE packets with the
> "ip fou add port 7777 gue" command.
>
> The second configures a GRE tunnel to use FOU encapsulation. The
> peer might be configured to receive these packets with the
> "ip fou add port 8888 ipproto 47" command.
>
> Tom Herbert (5):
> iplink: Fix setting of -1 as ifindex
> ip fou: Support to configure foo-over-udp RX
> ip tunnel: Kernel uapi definitions for fou and gue
> ip link ipip: Add support to configure FOU and GUE
> ip link gre: Add support to configure FOU and GUE
>
> include/linux/fou.h | 41 ++++++++++++
> include/linux/if_tunnel.h | 17 +++++
> ip/Makefile | 3 +-
> ip/ip.c | 3 +-
> ip/ip_common.h | 1 +
> ip/ipfou.c | 158 ++++++++++++++++++++++++++++++++++++++++++++++
> ip/iplink.c | 2 +-
> ip/link_gre.c | 89 ++++++++++++++++++++++++++
> ip/link_iptnl.c | 89 ++++++++++++++++++++++++++
> 9 files changed, 400 insertions(+), 3 deletions(-)
> create mode 100644 include/linux/fou.h
> create mode 100644 ip/ipfou.c
Please resubmit this patch series.
1. It no longer applies cleanly
2. Address the comments about port number and -1 ifindex patch
3. Add man pages
prev parent reply other threads:[~2014-11-02 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 15:55 [PATCH iproute2 0/5] iproute: Add FOU and GUE configuration in ip Tom Herbert
2014-10-03 15:55 ` [PATCH iproute2 1/5] iplink: Fix setting of -1 as ifindex Tom Herbert
2014-10-07 0:42 ` Cong Wang
2014-10-03 15:55 ` [PATCH iproute2 2/5] ip fou: Support to configure foo-over-udp RX Tom Herbert
2014-11-02 19:36 ` Stephen Hemminger
2014-11-02 19:45 ` Stephen Hemminger
2014-11-02 20:53 ` Stephen Hemminger
2014-10-03 15:55 ` [PATCH iproute2 3/5] ip tunnel: Kernel uapi definitions for fou and gue Tom Herbert
2014-10-03 15:55 ` [PATCH 4/5] ip link ipip: Add support to configure FOU and GUE Tom Herbert
2014-10-21 16:48 ` Sabrina Dubroca
2014-10-03 15:55 ` [PATCH 5/5] ip link gre: " Tom Herbert
2014-11-02 19:46 ` 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=20141102114609.6ba7f9d1@urahara \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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.