From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Westphal Subject: Re: [PATCH nf-next 0/3] netfilter: built-in NAT support for DCCP, SCTP, UDPlite Date: Thu, 20 Oct 2016 12:28:08 +0200 Message-ID: <20161020102808.GB26517@breakpoint.cc> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Pablo Neira Ayuso , Patrick McHardy , Jozsef Kadlecsik , "David S. Miller" , Arturo Borrero Gonzalez , Florian Westphal , netfilter-devel@vger.kernel.org, coreteam@netfilter.org To: Davide Caratti Return-path: Received: from Chamillionaire.breakpoint.cc ([146.0.238.67]:60696 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754041AbcJTK3Y (ORCPT ); Thu, 20 Oct 2016 06:29:24 -0400 Content-Disposition: inline In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: Davide Caratti wrote: > The above L4 protocols usually need an explicit modprobe command (e.g > "modprobe nf_nat_proto_sctp") to provide full functionality of REDIRECT > targets and SNAT/DNAT targets where port number translation is explicitly > configured. > In order to remove such limitation, this series converts > CONFIG_NF_NAT_PROTO_{DCCP,SCTP,UDPLITE} from tristate to boolean: in case > NAT support for these protocols is enabled in the kernel configuration, it > will be built into nf_nat.ko. Sorry for not thinking of this sooner, but it would be nice to record size increase of nat module in the commit message (and perhaps size of 'old' proto_foo nat module that is removed).