netdev - Re: [RFC net-next 1/2] net: allow user to set IPv6 nexthop for IPv4 route

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Mar 2015 09:23:57 -0400
From:	Sowmini Varadhan <sowmini05@...il.com>
To:	Andy Gospodarek <gospo@...ulusnetworks.com>
Cc:	netdev <netdev@...r.kernel.org>,
	Bjornar Ness <bjornar.ness@...il.com>,
	Eric Dumazet <eric.dumazet@...il.com>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: [RFC net-next 1/2] net: allow user to set IPv6 nexthop for IPv4 route

On Thu, Mar 26, 2015 at 5:05 PM, Andy Gospodarek
<gospo@...ulusnetworks.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.

--Sowmini
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html