netdev - Re: [PATCH net-next 0/3 v4] changes to make ipv4 routing table aware of next-hop link status

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20150617202526.GK588@gospo.home.greyhouse.net>
Date:	Wed, 17 Jun 2015 16:25:27 -0400
From:	Andy Gospodarek <gospo@...ulusnetworks.com>
To:	Nicolas Dichtel <nicolas.dichtel@...nd.com>
Cc:	netdev@...r.kernel.org, davem@...emloft.net,
	ddutt@...ulusnetworks.com, sfeldma@...il.com,
	alexander.duyck@...il.com, hannes@...essinduktion.org,
	stephen@...workplumber.org
Subject: Re: [PATCH net-next 0/3 v4] changes to make ipv4 routing table aware
 of next-hop link status

On Wed, Jun 17, 2015 at 09:52:11PM +0200, Nicolas Dichtel wrote:
> Le 17/06/2015 21:10, Andy Gospodarek a écrit :
> >On Wed, Jun 17, 2015 at 06:05:32PM +0200, Nicolas Dichtel wrote:
> >>Le 15/06/2015 18:33, Andy Gospodarek a écrit :
> >>>This series adds the ability to have the Linux kernel track whether or
> >>>not a particular route should be used based on the link-status of the
> >>>interface associated with the next-hop.
> >>>
> >>>Before this patch any link-failure on an interface that was serving as a
> >>>gateway for some systems could result in those systems being isolated
> >>>from the rest of the network as the stack would continue to attempt to
> >>>send frames out of an interface that is actually linked-down.  When the
> >>>kernel is responsible for all forwarding, it should also be responsible
> >>>for taking action when the traffic can no longer be forwarded -- there
> >>>is no real need to outsource link-monitoring to userspace anymore.
> >>>
> >>>This feature is only enabled with the new per-interface or ipv4 global
> >>>sysctls called 'ignore_routes_with_linkdown'.
> >>>
> >>>net.ipv4.conf.all.ignore_routes_with_linkdown = 0
> >>>net.ipv4.conf.default.ignore_routes_with_linkdown = 0
> >>>net.ipv4.conf.lo.ignore_routes_with_linkdown = 0
> >>>...
> >>Sorry for my late reply, but is it possible to advertise this sysctl via the
> >>netconf infra (grep NETCONFA_)?
> >I would be happy to do that.  Do you see it as a requirement for this
> >set to be accepted?
> No, but it would be great to do it before net-next closes.
Will do.

> 
> >
> >I've got to add ipv6 support, so netconf support could also easily be
> >added in the kernel and iproute2.
> Ok.
--
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