On Sun, 25 Jun 2023, Matthias Petermann wrote:
2) increased the ARP cache timeout net.inet.arp.nd_reachable=120
on both, Dom0 and DomU -> this seemed to have an effect at first,
but the problem still exists (its not a measured fact but a feeling,
that it happens now a bit less oft
Hello. Here are the network configuration settings I've been using for
a number of years,
all the way through -current.
net.inet.tcp.recvbuf_auto=1
net.inet.tcp.sendbuf_auto=1
net.inet.tcp.sendbuf_max=16777216
net.inet.tcp.recvbuf_max=16777216
-thanks
-Brian
Hello,
On 25.06.23 03:48, RVP wrote:
On Sat, 24 Jun 2023, Brian Buhrow wrote:
In any case, The fact that you're getting regular delays on your pings
suggests
there is a delay between the time when the arp cache times out and
when it gets refreshed.
This would be determined by `net.inet.ar
Updating src tree:
P src/bin/sh/eval.c
P src/doc/CHANGES.prev
P src/external/bsd/ipf/dist/ip_fil.c
P src/lib/libbluetooth/bt_dev.c
P src/lib/libcrypt/crypt.c
P src/lib/libcurses/refresh.c
P src/lib/libperfuse/ops.c
P src/sys/arch/amd64/amd64/locore.S
P src/sys/arch/amiga/dev/if_esreg.h
P src/sys/
On Sat, 24 Jun 2023, Brian Buhrow wrote:
In any case, The fact that you're getting regular delays on your pings suggests
there is a delay between the time when the arp cache times out and when it gets
refreshed.
This would be determined by `net.inet.arp.nd_delay' I think (on
-HEAD).
As a c
Brian Buhrow writes:
> Hello. The ARP cache timeout used to be 1200 seconds or 20 minutes,
> hard coded. Now, it
> looks like it's either 1200 seconds or 300 seconds, I'm not sure after a
> quick romp through the
> kernel source. In any case, The fact that you're getting regular delays
Hello. The ARP cache timeout used to be 1200 seconds or 20 minutes,
hard coded. Now, it
looks like it's either 1200 seconds or 300 seconds, I'm not sure after a quick
romp through the
kernel source. In any case, The fact that you're getting regular delays on
your pings suggests
there
In article ,
Paul Goyette wrote:
>On Tue, 20 Jun 2023, Paul Goyette wrote:
>
>> On Tue, 20 Jun 2023, Paul Goyette wrote:
>>
>>> With sources updated on 2023-06-20 at 17:26:58 UTC and building into
>>> a completely empty $DESTDIR I am getting
>>>
>>>
>>> == 2 missing files in DESTDIR =
On Fri, Jun 23, 2023 at 11:37:23PM +, RVP wrote:
> On Fri, 23 Jun 2023, Brian Buhrow wrote:
>
> > hello. My understanding is that the arp caching mechanism works
> > regardless of whether
> > you use static MAC addresses or dynamically generated ones.
> > [...]
> > If you then run brconf
On Sat, 24 Jun 2023, Matthias Petermann wrote:
On my Dom0, it looks like there is a timeout for the MAC adresses. The lines
below are random but subsequent samples of the "arp -an" command on the Dom0
(192.168.2.50) within a timespan of ~5 minutes. What catched my eye so far:
- there seem to
10 matches
Mail list logo
