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 2015-11-25 09:21, Daniel Bilik wrote:
It happened again, yesterday, and I can now definitely confirm
that it's related to default route.
[...]
... because again it was pushing outgoing packets wrong way, via public
interface, where it's dropped by pf...
[...]
I've tried to just delete defau
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/04/15 20:34, Hans Petter Selasky wrote:
Hi Adrian,
On 10/31/15 16:01, Alexander V. Chernikov wrote:
31.10.2015, 16:46, "Adrian Chadd" :
On 31 October 2015 at 09:34, Alexander V. Chernikov
wrote:
31.10.2015, 05:32, "Adrian Chadd" :
Hiya,
Here's a panic from arptimer:
Hi Adr
Hi Adrian,
On 10/31/15 16:01, Alexander V. Chernikov wrote:
31.10.2015, 16:46, "Adrian Chadd" :
On 31 October 2015 at 09:34, Alexander V. Chernikov
wrote:
31.10.2015, 05:32, "Adrian Chadd" :
Hiya,
Here's a panic from arptimer:
Hi Adrian,
As far as I see, line 205 in if_ether.c
On 04.12.2015 07:21, Nikos Vassiliadis wrote:
> Hi,
>
> we use ETHERIP to connect two remote locations and we discovered
> something that looks like a bug. A packet of specific size
> cannot go through the tunnel.
>
> Correct behavior:
>> root@prometheus:~ # ping -s 1450 10.65.0.1
>> PING 10.65.0
Hi,
I am trying to configure bhyve with FreeBSD Guest and Centos Guest. I am
using FreeBSD 10.2 RELEASE or 11.0 CURRENT (November 19) as a host. The
host is setup with bce as bridging interface. The network in the host is
not working. (I did a similar setup with FreeBSD 10-STABLE and Centos
using
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
10 matches
Mail list logo
