From: Rich Brown <richb.hanover@gmail.com>
To: David Lang <david@lang.hm>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] mDNS
Date: Wed, 28 Feb 2024 08:36:27 -0500 [thread overview]
Message-ID: <167EF7EA-0C28-4794-960F-F25AD56881DB@gmail.com> (raw)
In-Reply-To: <8s2q08r1-p4s0-2pns-3s2q-334s7np6947o@ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
I'm not advocating that we change the default OpenWrt address from 192.168.1.1 That's welded too deeply into our synapses (and documentation). But this proposal will benefit newcomers for the reasons described below.
> On Feb 28, 2024, at 7:17 AM, David Lang <david@lang.hm> wrote:
>
> remember, you don't need to randomly pick something, you just need to have a couple networks, figure out if one is in use by the WAN and if so pick the other.
Remember, too, that this proposal is designed to solve problems for first-time users. This lets them avoid reading an entire page of documentation that explains how to find their ISP's assigned subnet, and then set their new OpenWrt device LAN to use a different subnet.
This won't affect experienced OpenWrt users. On an initial flash/configuration, they'll know they can use 192.168.1.0/24 because they know their upstream device configuration. Or they can log in using the mDNS name and configure it themselves.
> I will say that 192.168.0 and 192.168.1 are very commonly used, so anything other than those a better default
>
> personally, I like 192.168.255 as people tend to forget that's a valid network.
So... Is there any reason not to incorporate this into the OpenWrt default build? Thanks again.
-- Rich
[-- Attachment #2: Type: text/html, Size: 4017 bytes --]
next prev parent reply other threads:[~2024-02-28 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2024-02-28 20:35 ` Juliusz Chroboczek
[not found] <mailman.5.1709053201.5517.bloat@lists.bufferbloat.net>
2024-02-27 18:52 ` Rich Brown
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
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=167EF7EA-0C28-4794-960F-F25AD56881DB@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
/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