All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini05@gmail.com>
To: "Bjørnar Ness" <bjornar.ness@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: IPv6 nexthop for IPv4
Date: Thu, 26 Mar 2015 10:53:56 -0400	[thread overview]
Message-ID: <CACP96tQAYZEq=cFyDNBkgzUbJ_VPJB540ZxgaRqpciujCYOjsA@mail.gmail.com> (raw)
In-Reply-To: <CAJO99TmhNARZL4L2KzMHLdqhXFh8LYb+mussWvaiCN4KQpim=Q@mail.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.


> Basically because you either added the route manually, or it was provided
> by fe80::225:90ff:fed3:bfb4 itself via some routing protocol (MP-BGP)
>
> This will be the same as any other route. How do you know it forwards traffic..

because you would be running a routing protocol that manages reachability
of the gw and the route. RIP, OSPF, BGP etc all have a lot of mechanisms
to monitor liveness of the route and of the nexthop, which has to be of
the same address family as the route itself.

>
> In large routed setups, address management in general and lack of IPv4 addresses
> can become a big hassle. Beeing able to get a ipv6 neighbor for a ipv4
> route would
> make this process a lot simpler.

Yes, that's the motivation behind all the tunneling/transition mechanisms
in the various ipv6 working groups.

--Sowmini

  reply	other threads:[~2015-03-26 14:53 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 [this message]
2015-03-26 15:10       ` Bjørnar Ness
2015-03-26 15:43         ` John W. Linville
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='CACP96tQAYZEq=cFyDNBkgzUbJ_VPJB540ZxgaRqpciujCYOjsA@mail.gmail.com' \
    --to=sowmini05@gmail.com \
    --cc=bjornar.ness@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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.