netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timo Teras <timo.teras@iki.fi>
To: xeb@mail.ru
Cc: netdev@vger.kernel.org
Subject: Re: [net-next,v3] GRE over IPv6
Date: Mon, 30 Jul 2012 14:38:06 +0300	[thread overview]
Message-ID: <20120730143806.41f759fd@vostro> (raw)
In-Reply-To: <1368610.TAsHNfv2Eb@comp1>

On Sat, 28 Jul 2012 22:12:42 -0000 xeb@mail.ru wrote:

> GRE over IPv6 implementation.
> 
> Signed-off-by: Dmitry Kozlov <xeb@mail.ru>
> 
> ---
> Changes:
> Initialize nt->dev before calling ip6gre_tnl_link_config in
> ip6gre_newlink.
> Add missing ip6gre.c
> 
>  include/linux/if_arp.h     |    1 +
>  include/linux/if_tunnel.h  |    3 +
>  include/linux/ip6_tunnel.h |   18 +
>  include/net/ip6_tunnel.h   |   40 +-
>  include/net/ipv6.h         |    1 +
>  net/ipv6/Kconfig           |   16 +
>  net/ipv6/Makefile          |    1 +
>  net/ipv6/ip6_gre.c         | 1817
> ++++++++++++++++++++++++++++++++++++++++++++
> net/ipv6/ip6_tunnel.c      |   86 ++- 9 files changed, 1958
> insertions(+), 25 deletions(-)

Would it be possible and/or feasible to instead modify ip_gre to support
also ipv6 as outer protocol? 

It already has ipv6 stuff in it for the inner protocol support. And it
would avoid duplicating most of the code.

And I would especially love that approach, since I could then on
per-target basis say if it should be contacted with IPv4 or IPv6. As in:
 
  ip addr add 10.0.0.1/24 dev gre1
  ip neigh add 10.0.0.2 lladdr 192.168.x.x dev gre1 nud permanent
  ip neigh add 10.0.0.3 lladdr fe80::xxxx:xxxx:xxxx:xxxx/64 dev gre1 nud permanent

- Timo

  reply	other threads:[~2012-07-30 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-29  8:12 [PATCH net-next v3] GRE over IPv6 Dmitry Kozlov
2012-07-30 11:38 ` Timo Teras [this message]
2012-07-30 11:52   ` [net-next,v3] " Kozlov Dmitry
2012-07-30 12:26     ` Timo Teras

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=20120730143806.41f759fd@vostro \
    --to=timo.teras@iki.fi \
    --cc=netdev@vger.kernel.org \
    --cc=xeb@mail.ru \
    /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).