From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Dichtel Subject: [RFC PATCH net-next v2 0/5] Allow to monitor protocol configuration Date: Wed, 24 Oct 2012 18:02:54 +0200 Message-ID: <1351094579-3911-1-git-send-email-nicolas.dichtel@6wind.com> References: <20121023.132940.1732325493436273627.davem@davemloft.net> Cc: netdev@vger.kernel.org To: davem@davemloft.net Return-path: Received: from 33.106-14-84.ripe.coltfrance.com ([84.14.106.33]:35365 "EHLO proxy.6wind.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757843Ab2JXPyi (ORCPT ); Wed, 24 Oct 2012 11:54:38 -0400 In-Reply-To: <20121023.132940.1732325493436273627.davem@davemloft.net> Sender: netdev-owner@vger.kernel.org List-ID: This patch serie aims to advertising via netlink any change in the network configuration of a protocol (network or transport). For example the announcement when ip forwarding parameter is toggled. It adds a new kind of messages, RTM_NEWNETCONF/RTM_GETNETCONF. The patch which adds the support of netconf messages in iproute2 will be sent when the feature will be included. If someone is interested to get it before, just tell me! v2: rename functions to be consistent specify type of the attribute to notify when calling inet[6]_netconf_notify_devconf(), goal is to notify only thinks that changed. add RTM_GETNETCONF support Comments are welcome. Regards, Nicolas