From: Jiri Benc <jbenc@redhat.com>
To: netdev@vger.kernel.org
Cc: Pravin B Shelar <pshelar@nicira.com>, Thomas Graf <tgraf@suug.ch>,
Simon Horman <simon.horman@netronome.com>
Subject: [PATCH net 0/3] ipgre: fix lwtunnel support
Date: Fri, 22 Apr 2016 19:44:05 +0200 [thread overview]
Message-ID: <cover.1461346798.git.jbenc@redhat.com> (raw)
lwtunnels currently work only with gretap. This patchset fixes the bugs in
ipgre metadata mode implementation.
As an example, in this setup:
ip a a 192.168.1.1/24 dev eth0
ip l a gre1 type gre external
ip l s gre1 up
ip a a 192.168.99.1/24 dev gre1
ip r a 192.168.99.2/32 encap ip dst 192.168.1.2 ttl 10 dev gre1
ping 192.168.99.2
the traffic does not go through before this patchset and does as expected
with it applied.
Jiri Benc (3):
gre: do not assign header_ops in collect metadata mode
gre: build header correctly for collect metadata tunnels
gre: receive also TEB packets for lwtunnels
include/net/ip_tunnels.h | 1 +
net/ipv4/ip_gre.c | 48 +++++++++++++++++++++++++++++++++---------------
2 files changed, 34 insertions(+), 15 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-04-22 17:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 17:44 Jiri Benc [this message]
2016-04-22 17:44 ` [PATCH net 1/3] gre: do not assign header_ops in collect metadata mode Jiri Benc
2016-04-22 21:04 ` pravin shelar
2016-04-22 21:20 ` Jiri Benc
2016-04-23 1:41 ` Thomas Graf
2016-04-24 9:31 ` Jiri Benc
2016-04-22 17:44 ` [PATCH net 2/3] gre: build header correctly for collect metadata tunnels Jiri Benc
2016-04-22 21:05 ` pravin shelar
2016-04-23 0:03 ` Simon Horman
2016-04-22 17:44 ` [PATCH net 3/3] gre: receive also TEB packets for lwtunnels Jiri Benc
2016-04-22 21:07 ` pravin shelar
2016-04-22 21:27 ` Jiri Benc
2016-04-23 3:40 ` pravin shelar
2016-04-24 9:54 ` Jiri Benc
2016-04-23 1:49 ` Thomas Graf
2016-04-23 5:09 ` Simon Horman
2016-04-24 9:38 ` Jiri Benc
2016-04-28 6:49 ` Simon Horman
2016-04-28 8:23 ` Jiri Benc
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=cover.1461346798.git.jbenc@redhat.com \
--to=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=simon.horman@netronome.com \
--cc=tgraf@suug.ch \
/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).