From: David Lang <david@lang.hm>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Rich Brown <richb.hanover@gmail.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] mDNS
Date: Wed, 28 Feb 2024 04:17:23 -0800 (PST) [thread overview]
Message-ID: <8s2q08r1-p4s0-2pns-3s2q-334s7np6947o@ynat.uz> (raw)
In-Reply-To: <874jdsizp5.wl-jch@irif.fr>
On Wed, 28 Feb 2024, Juliusz Chroboczek via Bloat wrote:
>> But my point is that the OpenWrt router has no way to predict what
>> address/subnet will be assigned to its WAN port.
>
> In principle, the ISP should assign either a global address, or an address in
> the range 100.64.0.0/10 (RFC 6598). This range was deliberately chosen to
> not collide with RFC 1918 space, so that the NAT box can choose any RFC 1918
> prefix on its downstream interfaces.
>
> In practice, however, ISPs don't necessarily obey the RFCs, and people do
> chain NAT boxes, so none of the above is guaranteed.
chaining NAT boxes is very common, too many ISPs don't give you anything other
than a NAT address from their router
>> Consequently, at boot-time, OpenWrt should simply choose some different
>> subnet for its LAN subnet(s), and then advertise an mDNS name.
>
> I'm not sure how that could happen at boot time, it would need to happen
> whenever a DHCPv4 lease changes. This implies that the router might need
> to renumber if the ISP changes its allocation, and there are no
> renumbering procedures for IPv4 (I'm not sure if anyone implements RFC 3203).
it's unusual for the network block to change on a renewal, and in that rare case
you could reboot the router.
> It would also make addressing non-deterministic, which would make
> debugging slightly more difficult. But then, we already have
> non-deterministic addressing in IPv6, so I guess that's something we can
> live with.
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.
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.
David Lang
> -- Juliusz
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2024-02-28 12:17 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 [this message]
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=8s2q08r1-p4s0-2pns-3s2q-334s7np6947o@ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=jch@irif.fr \
--cc=richb.hanover@gmail.com \
/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