Date: Fri, 4 Dec 2015 23:43:06 +0000 From: Gary Palmer <gpalmer@freebsd.org> To: Jason Van Patten <jvp@lateapex.net> Cc: freebsd-net@freebsd.org Subject: Re: Bridge Interfaces and ARPs Message-ID: <20151204234306.GA18341@in-addr.com> In-Reply-To: <5661F728.5090108@lateapex.net> References: <56604982.9010003@lateapex.net> <20151204070606.GA16904@babolo.ru> <5661F728.5090108@lateapex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151204234306.GA18341>