On 12/4/15 6:43 PM, Gary Palmer wrote:
On Fri, Dec 04, 2015 at 03:27:20PM -0500, Jason Van Patten wrote:
Any guidance or suggestions on that one?
Try:
sysrc arpproxy_all=YES
You can remove the sysctl setting as that's what that option does.
According to /etc/rc.d/routing, it looks like th
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?
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*
On 12/4/15 2:06 AM, Aleksandr A Babaylov wrote:
May be it is proxy arp from Verison.
Fair assumption. They may be doing that to prevent one Verizon customer
from talking directly to another without routing through them first,
even though each customer is on the same broadcast domain.
sys
On Thu, Dec 03, 2015 at 08:54:10AM -0500, Jason Van Patten wrote:
> Hey gang -
>
> I posted this to the FreeBSD user forums but figured I'd send a message
> off to the list to see if anyone has any input, guidance, or ideas.
> Emailing diagrams around isn't good form (IMHO) but having a diagram
On 12/3/2015 5:24 PM, Jason Van Patten wrote:
Hey gang -
I posted this to the FreeBSD user forums but figured I'd send a message off to the list to see if anyone has any input, guidance, or ideas. Emailing diagrams around isn't good form (IMHO) but having
a diagram handy will help with the disc
