General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: David Lang <david@lang.hm>
Cc: Rich Brown <richb.hanover@gmail.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] mDNS
Date: Wed, 28 Feb 2024 21:35:03 +0100	[thread overview]
Message-ID: <87frxcqqdk.wl-jch@irif.fr> (raw)
In-Reply-To: <8s2q08r1-p4s0-2pns-3s2q-334s7np6947o@ynat.uz>

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

At any rate, boot time is too early, since you don't know your
ISP-assigned address at that point.  You really need to delay until DHCPv4
gets a lease.

> and in that rare case you could reboot the router.

You don't need to reboot the router, it can renumber just fine.  You need
to reboot all the client devices (unless they implement DHCPv4 force renew
with nonce authentication, aka RFC 3203).

I'm not saying it's a bad idea, just pointing out some of the edge-cases
that you will need to consider in order to get a robust implementation.

-- Juliusz

  parent reply	other threads:[~2024-02-28 20:35 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
2024-02-28 20:35       ` Juliusz Chroboczek [this message]
     [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=87frxcqqdk.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=bloat@lists.bufferbloat.net \
    --cc=david@lang.hm \
    --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