From: Andy Gospodarek <gospo@cumulusnetworks.com>
To: Sowmini Varadhan <sowmini05@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
Bjornar Ness <bjornar.ness@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [RFC net-next 1/2] net: allow user to set IPv6 nexthop for IPv4 route
Date: Fri, 27 Mar 2015 10:35:23 -0400 [thread overview]
Message-ID: <20150327143522.GH1051@gospo> (raw)
In-Reply-To: <CACP96tQjVxSgh3m7ext5P+iyY2tPXy3O6R+UQ4wv44MRjFQvZQ@mail.gmail.com>
On Fri, Mar 27, 2015 at 09:23:57AM -0400, Sowmini Varadhan wrote:
> On Thu, Mar 26, 2015 at 5:05 PM, Andy Gospodarek
> <gospo@cumulusnetworks.com> wrote:
> > This adds kernel infrastructure to allow userspace (read: routing protocols) to
> > support adding IPv6 next-hops to IPv4 routes. This is essentially added to
> > support a feature of MP-BGP outlined in RFC-5549.
> >
> > Thise does not encompass all that is needed to support RFC-5549, but this
> > demonstrates the netlink infrastructure needed to correctly enable the kernel
> > infrastructure that would support this RFC. For more informtion the full RFC
> > is here: http://www.ietf.org/rfc/rfc5549.txt.
>
> Is there some impact to redirect behavior? RFC 5549 does not seem to
> discuss it at all, but the firsthop would be processing (and
> potentially sending)
> an icmp redirect to the host. I dont think there is a good way to construct
> this, either with icmpv4 or icmpv6, and maybe some checks are needed to
> not even try, when the IP mix-match is encountered.
>
You are correct that there is not a great way to construct this since
the frames at strictly IPv4 frames. I'll have to dig into this a bit
more to see if there is something worth doing for this case.
next prev parent reply other threads:[~2015-03-27 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 21:05 [RFC net-next/iproute2 0/2] net: infrastructure to support RFC-5549 Andy Gospodarek
2015-03-26 21:05 ` [RFC net-next 1/2] net: allow user to set IPv6 nexthop for IPv4 route Andy Gospodarek
2015-03-26 21:42 ` Sowmini Varadhan
2015-03-26 23:12 ` Julian Anastasov
2015-03-27 0:27 ` Andy Gospodarek
2015-03-27 11:53 ` Robert Shearman
2015-03-27 14:10 ` Andy Gospodarek
[not found] ` <CAJO99TkSaJjmvTjWOpnMLwNaf7A-q9_DvkppT+M77rSV0Syh0w@mail.gmail.com>
2015-04-08 2:52 ` Andy Gospodarek
2015-03-27 13:23 ` Sowmini Varadhan
2015-03-27 14:35 ` Andy Gospodarek [this message]
2015-03-27 14:37 ` Sowmini Varadhan
2015-03-26 21:05 ` [RFC iproute2 2/2] iproute2: " 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=20150327143522.GH1051@gospo \
--to=gospo@cumulusnetworks.com \
--cc=bjornar.ness@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=linville@tuxdriver.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