General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] mDNS
Date: Wed, 28 Feb 2024 12:40:54 +0100	[thread overview]
Message-ID: <874jdsizp5.wl-jch@irif.fr> (raw)
In-Reply-To: <30F7E4EF-906B-41CD-9EDE-179106E8BFCF@gmail.com>

> 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.

> 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 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.

-- Juliusz

  reply	other threads:[~2024-02-28 11:40 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 [this message]
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=874jdsizp5.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=bloat@lists.bufferbloat.net \
    --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