On 05/16, Andrew K Adams wrote:
> I've looked at traffic with tcpdump, but there is so much in both
> scenarios that I can't really say that one service, or a
> packet-of-death is triggering the degraded state. But thinking in
> aggregate, if there was a way to monitor the average packets/sec the
On Mon, 16 May 2022, Andrew K Adams wrote:
I've looked at traffic with tcpdump, but there is so much in both
scenarios that I can't really say that one service, or a
packet-of-death is triggering the degraded state. But thinking in
aggregate, if there was a way to monitor the average
I've looked at traffic with tcpdump, but there is so much in both
scenarios that I can't really say that one service, or a
packet-of-death is triggering the degraded state. But thinking in
aggregate, if there was a way to monitor the average packets/sec the
gateway is forwarding, in both
On Sun, May 15, 2022 at 7:52 AM Andrew K Adams wrote:
>
> Hi, I’ve noticed a problem with my NetBSD server that I really could
> use some help with. The server is acting as my home router (gateway)
> in ‘pass-through’ mode with Comcast Xfinity as the service provider.
> The only
Hi, I’ve noticed a problem with my NetBSD server that I really could
use some help with. The server is acting as my home router (gateway)
in ‘pass-through’ mode with Comcast Xfinity as the service provider.
The only functions/services enabled on the server are: ip-forwarding,
dhcp-client, and
