From owner-freebsd-net@freebsd.org Fri Dec 4 23:43:10 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E257A40D03 for ; Fri, 4 Dec 2015 23:43:10 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 65C8419C1 for ; Fri, 4 Dec 2015 23:43:10 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1a500I-0009xY-6a; Fri, 04 Dec 2015 23:43:06 +0000 Date: Fri, 4 Dec 2015 23:43:06 +0000 From: Gary Palmer To: Jason Van Patten Cc: freebsd-net@freebsd.org Subject: Re: Bridge Interfaces and ARPs Message-ID: <20151204234306.GA18341@in-addr.com> References: <56604982.9010003@lateapex.net> <20151204070606.GA16904@babolo.ru> <5661F728.5090108@lateapex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5661F728.5090108@lateapex.net> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2015 23:43:10 -0000 On Fri, Dec 04, 2015 at 03:27:20PM -0500, Jason Van Patten wrote: > On 12/4/15 2:06 AM, Aleksandr A Babaylov wrote: > > > > sysctl net.link.ether.inet.proxyall=1 > > This looks like it's working; thanks a bunch! Whoda'thunk you could use > something like proxy arp to un-break a broken network? It appears as > though the above sysctl keeps resetting itself to 0 with *any* network > interface changes. And from what I can see, that's as by design? Is > there any way to get it to stay 1? The problem is that sysctl does its > think during boot-up, before the interfaces and routing are all set in > /etc/rc.conf. So I have to come back in and manually set it to 1. I > suppose I can write an RC script to do that for me, but it's still > suboptimal. > > Any guidance or suggestions on that one? > > Thanks again! Try: sysrc arpproxy_all=YES You can remove the sysctl setting as that's what that option does. Regards, Gary