Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Robert McMahon <rjmcmahon@rjmcmahon.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] FCC - delete, delete, delete
Date: Sat, 15 Mar 2025 11:50:46 -0700	[thread overview]
Message-ID: <CAEBrVk4DnaQOqBi5BD2sTAYn7OGgmas8Ezkj-0Wj8js86rvtCg@mail.gmail.com> (raw)
In-Reply-To: <CAEBrVk5u2qFdSha8ANgM_C5rbAzYSsOYhHP1XMmKxLY4=SnONw@mail.gmail.com>

A correction, some additions and a short allegory

o) I'm using 4 APs for 1800 sq ft, but it's two story stacked like two
blocks, so the radius per the RF spray pattern design can (and does)
take advantage of that
o) I placed high quality UPS where needed
o) I didn't mention IoT like irrigation control, PV monitoring,
weather systems, etc. Those are managed by a RPi4 with a UPS board and
battery. Scripts and c - code is written by me.
o) I didn't mention my in home lab/work network where each test device
has it's own GPS signal to get pulse per second from those atomic
clocks. That really helps a lot in my iperf 2 work
o) Having an in home lab gives me back an 30 minute commute (or 1 hr
for both directions) which is a lot and adds up. Unfortunately, my CEO
thinks we're children and need to follow an attendance policy so now I
have to waste time driving to do emails and get an attendance credit.
I started working at age 13 at a Baskin Robbins and within a month the
immigrant owner asked me to run the crews so he and his wife could go
home and rest w/o worrying about their primary means of  income. It's
very sad to be treated like a child, even when a child. SV is run by
children's mindsets now.

Bob

On Sat, Mar 15, 2025 at 11:16 AM Robert McMahon <rjmcmahon@rjmcmahon.com> wrote:
>
> >
> > In case it's not clear. I am NOT happy with how device manufacturers ship old
> > code and never update it.
> >
>
> I was unhappy about my home network and my paying job is to provide
> components for such.
>
> My home network wasn't resilient enough to carry entertainment,
> productivity (including distance learning) and medical traffic.
>
> The fixes so far have been:
>
> o) Don't use an all in one AP anywhere, just use it for wireless bridging
> o) Use a fronthaul architecture (2.5G - will go to 100G when Fi-Wi is ready)
> o) Use a dedicated firewall & dhcp server with AQM such as fq_codel (I
> use a protectcli vault)
> o) Connect the APs (4 for me in 100 sq ft) configured in bridge mode
> and optimize spacetime, allow for proper RF overlap - not too much,
> not too little, but just right like the story says.
> o) Use AP's that support the 6G band
> o) Use keep connect devices to detect AP failures and power cycle them
> (hammer approach)
> o) Use separate ethernet switches where 802.3 switching is needed
> (don't use the AP integrated switches, they go down per the crappy
> gateway sw you're likely talking about)
> o) Implement DHCP guard to protect against rogue DHCP servers
>
> Then for monitoring
> o) Install rpi 5bs with INTC BE200 and pcie Wi-Fi adapters in the
> rooms that need monitoring
> o) Install kismet and integrate with kismet to monitor
> o) Turn on firewall & WAN port monitoring services
>
> Only access to devices is ssh with encryption keys, and configure ssh
> passwordless access.
>
> Now, my family can be entertained, do their work and learning, and use
> their medical instruments with high in-home reliability.
>
> It's a thankless job we Dads must do. The home frustration level goes
> way down and the complaints of "Dad, the internet isn't working again"
> have gone away - except for when the OSP goes down. The OSP provider
> tends to send information to me when that happens so my family can
> work around it.
>
> Bob

      parent reply	other threads:[~2025-03-15 18:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 17:39 Dave Taht
2025-03-13  0:00 ` Richard Roy
2025-03-13 16:33   ` Robert McMahon
2025-03-13 17:00     ` Frantisek Borsik
2025-03-13 18:36       ` Robert McMahon
2025-03-13 23:59         ` David Lang
2025-03-14  1:12           ` Robert McMahon
2025-03-14  1:38         ` David Bray, PhD
2025-03-14  2:17           ` Robert McMahon
2025-03-14  2:20             ` Robert McMahon
2025-03-14  2:24             ` David Bray, PhD
2025-03-14  8:16               ` Tara Stella
2025-03-14 18:53                 ` Robert McMahon
2025-03-14 19:05                   ` Richard Roy
2025-03-14 21:09                     ` David Lang
2025-03-14 21:20                       ` Dick Roy
2025-03-14 21:48                         ` David Lang
2025-03-15 18:16                           ` Robert McMahon
2025-03-15 18:49                             ` Daniel Ezell
2025-03-16 17:50                               ` Robert McMahon
2025-03-15 18:50                             ` Robert McMahon [this message]

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=CAEBrVk4DnaQOqBi5BD2sTAYn7OGgmas8Ezkj-0Wj8js86rvtCg@mail.gmail.com \
    --to=rjmcmahon@rjmcmahon.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