From: "John W. Linville" <linville@tuxdriver.com>
To: "Bjørnar Ness" <bjornar.ness@gmail.com>
Cc: Sowmini Varadhan <sowmini05@gmail.com>,
netdev <netdev@vger.kernel.org>,
Andy Gospodarek <gospo@cumulusnetworks.com>
Subject: Re: IPv6 nexthop for IPv4
Date: Thu, 26 Mar 2015 11:43:36 -0400 [thread overview]
Message-ID: <20150326154336.GA2528@tuxdriver.com> (raw)
In-Reply-To: <CAJO99Tm+ex7aELCrNnubWz1hGjELMp0LCMKSqtyr+Vci1hrmuw@mail.gmail.com>
On Thu, Mar 26, 2015 at 04:10:21PM +0100, Bjørnar Ness wrote:
> 2015-03-26 15:53 GMT+01:00 Sowmini Varadhan <sowmini05@gmail.com>:
> > On Thu, Mar 26, 2015 at 10:39 AM, Bjørnar Ness <bjornar.ness@gmail.com> wrote:
> >
> >>>> ip route add 10.0.0.0/16 via fe80::225:90ff:fed3:bfb4/64 dev sfp0
> >>>
> >>> Trying to understand what the desired behavior is, for the route
> >>> above: if I send a packet from 10.0.0.1 to 10.0.0.2, you want the dst-mac
> >>> to be the mac address of e80::225:90ff:fed3:bfb4???
> >>
> >> Absolutely, correct.
> >
> > What if the current node does not want to support ipv6? This sounds
> > pretty "creative", if this can work, you might as well make the nexthop to
> > be the L2 address of the gw.
>
> If it does not support IPv6 I guess the route command will fail! This
> is a bad argument
> against this. Dont see the point of limiting nexthop to L2
This topic was discussed at the recent Netconf event in Ottawa.
This is a viable means of interconnecting two IPv4 "island" subnets
across an IPv6 "ocean" backplane.
Andy Gospodarek gave a short discussion on the topic, and IIRC it
was warmly received. I'll Cc him on this message -- I think he had a
(fairly simple) patch more or less ready.
Hth!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2015-03-26 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 13:16 IPv6 nexthop for IPv4 Bjørnar Ness
2015-03-26 14:29 ` Sowmini Varadhan
2015-03-26 14:39 ` Bjørnar Ness
2015-03-26 14:53 ` Sowmini Varadhan
2015-03-26 15:10 ` Bjørnar Ness
2015-03-26 15:43 ` John W. Linville [this message]
2015-03-26 16:27 ` Andy Gospodarek
2015-03-26 16:37 ` Eric Dumazet
2015-03-26 17:17 ` Andy Gospodarek
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=20150326154336.GA2528@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bjornar.ness@gmail.com \
--cc=gospo@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=sowmini05@gmail.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).