From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH net-next] tun: implement carrier change Date: Thu, 29 Nov 2018 17:36:09 +0100 Message-ID: <20181129163609.GD1501@lunn.ch> References: <20181128181256.12526-1-nicolas.dichtel@6wind.com> <20181128214804.GB2770@lunn.ch> <3970d6d0-b6d9-c123-0055-6158191dd674@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: davem@davemloft.net, netdev@vger.kernel.org, Didier Pallard To: Nicolas Dichtel Return-path: Received: from vps0.lunn.ch ([185.16.172.187]:54608 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728136AbeK3DmJ (ORCPT ); Thu, 29 Nov 2018 22:42:09 -0500 Content-Disposition: inline In-Reply-To: <3970d6d0-b6d9-c123-0055-6158191dd674@6wind.com> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Nov 29, 2018 at 12:06:18PM +0100, Nicolas Dichtel wrote: > Le 28/11/2018 à 22:48, Andrew Lunn a écrit : > > On Wed, Nov 28, 2018 at 07:12:56PM +0100, Nicolas Dichtel wrote: > >> The userspace may need to control the carrier state. > > > > Hi Nicolas > Hi Andrew, > > > > > Could you explain your user case a bit more. > > > > Are you running a routing daemon on top of the interface, and want it > > to reroute when the carrier goes down? > Sort of, we have a daemon that monitors the app and may re-route the traffic to > a secondary app if needed. O.K, this sounds sensible. It is often useful to explain the use case for changes like this. People try to do crazy things sometimes. Thanks Andrew