[bluez/bluez] 269438: mesh: Fix Command Disallowed on random address cha...

["Aurélien Rivet" <noreply@github.com>]

  Branch: refs/heads/1176997
  Home:   https://github.com/bluez/bluez
  Commit: 269438e7a5bac1adf2d63d7f28da994129064e58
      https://github.com/bluez/bluez/commit/269438e7a5bac1adf2d63d7f28da994129064e58
  Author: Aurélien Rivet <aurelienrivet@hotmail.fr>
  Date:   2026-09-30 (Wed, 30 Sep 2026)

  Changed paths:
    M mesh/mesh-io-generic.c

  Log Message:
  -----------
  mesh: Fix Command Disallowed on random address change in generic IO

send_cancel_done() issues LE Set Random Address at the end of every
burst of ADVs. The controller rejects that command with Command
Disallowed (0x0c) while scanning is enabled, per Core Spec, Vol 4,
Part E, Section 7.8.4, so the address never rotates as long as any
scan is registered, such as a provisioner discovering unprovisioned
devices.

Pause scanning around the address change and resume it afterwards,
mirroring the disable/re-enable sequence restart_scan() already uses.
When no scan is registered there is nothing to pause, so the address
change is issued directly.

Confirmed with btmon on a Raspberry Pi built-in controller: over a
60 s capture, 12 rotations about 5 s apart, each one LE Set Scan
Enable(disable) -> LE Set Random Address -> LE Set Scan
Enable(enable), every command completing with Success and every
rotation programming a distinct address. No Command Disallowed
anywhere in the capture, where the address change previously failed
on every attempt. Scanning is suspended for 1.2 ms to 2.6 ms per
rotation, which mesh retransmissions absorb.

Assisted-by: Claude:claude-sonnet-5
Assisted-by: Claude:claude-opus-5



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications