From: Rich Brown <richb.hanover@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] mDNS
Date: Tue, 27 Feb 2024 13:52:28 -0500 [thread overview]
Message-ID: <1142E628-CF2B-4EDC-B4FD-46832B6D5840@gmail.com> (raw)
In-Reply-To: <mailman.5.1709053201.5517.bloat@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
> On Feb 27, 2024, at 12:00 PM, bloat-request@lists.bufferbloat.net wrote:
>
> On 2/26/2024 6:28 AM, Rich Brown via Bloat wrote:
>> - Avoid the WAN port's DHCP assigned subnet (what if the ISP uses
>> 192.168.1.0/24?)
>
> I recently got ATT fiber and its modem won't let me assign from
> 10.0.0.0/8! So I put a Raspberry Pi 4 in front of it.
Exactly! There are no rules about what subnet range an ISP's gear will assign to DHCP devices.
So (I believe) it becomes incumbent on OpenWrt to be smarter than the ISP's router (shouldn't be hard) and pick a separate subnet for its LAN & wireless interface. (Clearly, OpenWrt could default to 192.168.1.0/24, but if that's that range the ISP is using, it could switch to 192.168.2.0/24. I think that's all the flexibility that's required...)
And then advertise a mDNS name to make it easy for humans to connect. Who would notice?
- Newcomers wouldn't - they'd just connect and configure as described in the Wiki
- Grizzled OpenWrt old-timers wouldn't notice either, because they will have set their ISP device to use some other address range.
Any reason not to build this into OpenWrt? Thanks.
Rich
[-- Attachment #2: Type: text/html, Size: 4467 bytes --]
next parent reply other threads:[~2024-02-27 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1709053201.5517.bloat@lists.bufferbloat.net>
2024-02-27 18:52 ` Rich Brown [this message]
2024-02-27 20:51 ` Aaron Wood
2024-02-28 0:43 ` Kenneth Porter
2024-02-28 1:09 ` Mark Andrews
2024-02-28 2:31 ` Matt Taggart
2024-02-28 3:23 ` Kenneth Porter
[not found] <mailman.2341.1709082589.1074.bloat@lists.bufferbloat.net>
2024-02-28 2:04 ` Rich Brown
2024-02-28 11:40 ` Juliusz Chroboczek
2024-02-28 12:17 ` David Lang
2024-02-28 13:36 ` Rich Brown
2024-02-28 20:35 ` Juliusz Chroboczek
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1142E628-CF2B-4EDC-B4FD-46832B6D5840@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@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