Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: "Karl Auerbach" <karl@cavebear.com>,
	"Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] upgrading old routers to modern, secure FOSS
Date: Mon, 23 Oct 2023 16:39:24 -0700 (PDT)	[thread overview]
Message-ID: <6756521n-p6n4-30q8-qr13-85p1s4n3on9s@ynat.uz> (raw)
In-Reply-To: <50c07326-781d-40de-8e2c-92d84bd84cf1@cavebear.com>

[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]

On Mon, 23 Oct 2023, Karl Auerbach via Nnagain wrote:

> It would be nice if we built our network devices so that they each had a 
> little introspective daemon that frequently asked "am I healthy, am I 
> still connected, are packets still moving through me?"  (For consumer 
> devices an answer of "no" could trigger a full device reboot or reset.)

I agree with a lot of what you say, but I want to throw in a word of caution 
here. I have seen systems go from 'slow but functioning' to 'completely down and 
requires a complete datacenter shutdown to recover' because of automated 
response systems that decided to restart something when it didn't respond fast 
enough, triggering a cascade of failures that prevented any service from being 
able to start into a healthy state.

I've also implemented monitoring on APs to restart them if they don't have a 
path to the Internet, resulting in continual reboots when there is a transitory 
issue (now changed to only check their next hop and only shut down wifi to avoid 
becoming a black hole for that SSID

to err is human, to really mess things up requires a computer, and automation 
removes the oversight from the computer allowing it to do more damage faster.

David Lang

  reply	other threads:[~2023-10-23 23:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 17:04 Dave Taht
2023-10-23 17:43 ` le berger des photons
2023-10-23 17:46   ` Frantisek Borsik
2023-10-23 18:11     ` Dave Taht
2023-10-23 18:38       ` Frantisek Borsik
2023-10-24  5:34       ` Ignacio Ocampo
2023-10-24  5:39         ` Ignacio Ocampo
2023-10-24 12:10           ` Frantisek Borsik
2023-10-24  0:36   ` Dave Taht
2023-10-23 17:58 ` Dave Taht
2023-10-23 18:20   ` David Lang
2023-10-23 18:39   ` Sebastian Moeller
2023-10-23 18:53   ` Jack Haverty
2023-10-23 19:01     ` David Lang
2023-10-23 19:37     ` Karl Auerbach
2023-10-23 21:54       ` rjmcmahon
2023-10-23 23:22         ` Karl Auerbach
2023-10-23 23:39           ` David Lang [this message]
2023-10-24  0:13             ` Karl Auerbach
2023-10-24  5:16           ` Robert McMahon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6756521n-p6n4-30q8-qr13-85p1s4n3on9s@ynat.uz \
    --to=david@lang.hm \
    --cc=karl@cavebear.com \
    --cc=nnagain@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox