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:16:22 -0700 [thread overview]
Message-ID: <CAEBrVk5u2qFdSha8ANgM_C5rbAzYSsOYhHP1XMmKxLY4=SnONw@mail.gmail.com> (raw)
In-Reply-To: <s05qp069-r500-83o0-15n1-7po19o6sr33n@ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]
>
> 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
[-- Attachment #2: Medical-Devices-with-Wi-Fi-03-15-2025_10_41_AM.png --]
[-- Type: image/png, Size: 341666 bytes --]
next prev parent reply other threads:[~2025-03-15 18:16 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 [this message]
2025-03-15 18:49 ` Daniel Ezell
2025-03-16 17:50 ` Robert McMahon
2025-03-15 18:50 ` 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='CAEBrVk5u2qFdSha8ANgM_C5rbAzYSsOYhHP1XMmKxLY4=SnONw@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