From owner-freebsd-net@FreeBSD.ORG Sat Nov 1 01:28:29 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 36C69C7; Sat, 1 Nov 2014 01:28:29 +0000 (UTC) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EAD00275; Sat, 1 Nov 2014 01:28:28 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id v63so3124019oia.9 for ; Fri, 31 Oct 2014 18:28:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=d47zLIZrH06oXHgyEodvKkAFAAFr7Q0KN9R8xb08vAg=; b=ynU8wbfanR04lpBx8Og1HZVAnVegF+1rspxtPWotqZO9F4+wjzWE+8P0mItAZdslfX uTfsr5bEssBv4WmpH6fi2XdaHtnX+jBZuZFUaMgOCPi2y+mMiLdOFchP+lQoApCoT27s 8T6QGC2mOmOR5mQv3rmXeZNWfMP3ab4hHtkT2Vq/cGv3Lx0Mbai4hh5n3RHCauGkRZ3U SMqug+ugEDUdUBtriCwUrXOmTXrT6MA0N94VYmjt4f6jYeX/NNjXu4sbG4V0XQvGo85E cIMKe4E/S4R2HKisXSqAo01WEeVALr/QvawPkPHlf0FFOfR+jiqQN77qKTijksjKpwjl 9J1A== MIME-Version: 1.0 X-Received: by 10.182.18.104 with SMTP id v8mr22769616obd.3.1414805308246; Fri, 31 Oct 2014 18:28:28 -0700 (PDT) Received: by 10.202.104.39 with HTTP; Fri, 31 Oct 2014 18:28:28 -0700 (PDT) Received: by 10.202.104.39 with HTTP; Fri, 31 Oct 2014 18:28:28 -0700 (PDT) In-Reply-To: <20141031191212.GO8852@funkthat.com> References: <20141031191212.GO8852@funkthat.com> Date: Fri, 31 Oct 2014 18:28:28 -0700 Message-ID: Subject: Re: any reason not to enable IPDIVERT for ipfw module? From: Freddie Cash To: FreeBSD Arch , freebsd-net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2014 01:28:29 -0000 On Oct 31, 2014 12:12 PM, "John-Mark Gurney" wrote: > > Can any one think of a good reason not to enable IPDIVERT sockets in > the ipfw module? > > And possibly enabling default to accept? That way you don't have to > go to the console when you load the ipfw module because you forgot to > auto add the accept all rule? :) You can change the default rule to accept via loader.conf and it will be set when the module is loaded. net.inet.IP.fw.default_to_accept or something Luke that. > something like: > ==== //depot/projects/opencrypto/sys/modules/ipfw/Makefile#3 - /home/jmg/freebsd.p4/opencrypto/sys/modules/ipfw/Makefile ==== > --- /tmp/tmp.15774.16 2014-10-31 12:11:56.000000000 -0700 > +++ /home/jmg/freebsd.p4/opencrypto/sys/modules/ipfw/Makefile 2014-10-31 12:11:54.000000000 -0700 > @@ -16,7 +16,10 @@ > #CFLAGS+= -DIPFIREWALL_VERBOSE_LIMIT=100 > # > #If you want it to pass all packets by default > -#CFLAGS+= -DIPFIREWALL_DEFAULT_TO_ACCEPT > +CFLAGS+= -DIPFIREWALL_DEFAULT_TO_ACCEPT > +# > +#If you want divert sockets > +CFLAGS+= -DIPDIVERT > # > > .include > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"