From: Rich Brown <richb.hanover@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] mDNS
Date: Tue, 27 Feb 2024 21:04:32 -0500 [thread overview]
Message-ID: <30F7E4EF-906B-41CD-9EDE-179106E8BFCF@gmail.com> (raw)
In-Reply-To: <mailman.2341.1709082589.1074.bloat@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
> Avoid the WAN port's DHCP assigned subnet (what if the ISP uses
> 192.168.1.0/24?)
>
> ...
>
> Exactly! There are no rules about what subnet range an ISP's gear will assign to DHCP devices.
@Mark Andrews and @Kenneth Porter... I apologize for any confusion caused by my slightly ambiguous language. In both cases, I was referring to the DHCP address/subnet assigned to the OpenWrt router's WAN port, by the ISP's gear. This will be an RFC1918 address by default.
But my point is that the OpenWrt router has no way to predict what address/subnet will be assigned to its WAN port. Consequently, at boot-time, OpenWrt should simply choose some different subnet for its LAN subnet(s), and then advertise an mDNS name.
Does this make sense? Thanks.
Rich
[-- Attachment #2: Type: text/html, Size: 2003 bytes --]
next parent reply other threads:[~2024-02-28 2:04 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 [this message]
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
[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=30F7E4EF-906B-41CD-9EDE-179106E8BFCF@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