Mac mini M6: AirPlay to HomePod fails over built-in Ethernet (works over Wi-Fi/USB) – PTP clock never syncs

Question

Level 1

18 points

Mac mini M6: AirPlay to HomePod fails over built-in Ethernet (works over Wi-Fi/USB) – PTP clock never syncs

Setup

- Mac mini (M6, 2026), macOS 27.2, built-in 2.5GbE port (Realtek RTL8125, driver com.apple.driver.AppleEthernetRL, "AVB Support: Yes")

- HomePod mini stereo pair, HomePod Software 27.2

Problem

When the Mac uses its built-in Ethernet port, AirPlay audio to the HomePods fails: the HomePods light up, no sound plays, and after ~6 seconds the output falls back to the Mac speakers.

What works

- Same Mac over Wi-Fi: works

- Same Mac with a USB 2.5GbE adapter (Realtek RTL8156, "AVB Support: No"): works

- A MacBook on the same cable and switch port: works

- Everything else over the built-in port (internet, file sharing, Screen Sharing) works fine. Only AirPlay fails.

What I found (logs + packet capture)

- AirPlay control and audio data reach the HomePods fine. Only the PTP timing fails.

- AirPlayXPCHelper logs 50 rejected SetRateAndAnchorTime attempts per HomePod with error -71974 (kAPSNetworkClockError_InternalError), then tears down the session.

- The kernel TimeSync plugin tries to enable AVB on en0 and gets "activateAVB returned 0xe00002c7" (unsupported), but still runs the PTP port in hardware mode (en0[hw]).

- PTP counters on en0: everything sent by the Mac is transmitted, but ALL received PTP messages = 0, Delay_Resp sent = 0.

- A packet capture on en0 shows the HomePods sending ~8 Delay_Req per second to the Mac. They arrive at the interface but are never processed or answered, so the HomePods can never sync to the Mac's clock.

- Disabling AVB/EAV mode in System Settings > Network > Ethernet > Details > Hardware and rebooting makes no difference.

Reported to Apple as FBxxxxxxxx (with sysdiagnose, logs and packet capture).

Can anyone with a Mac mini M6 / M5 Pro (or Mac Studio M5) check?

1. Run in Terminal: system_profiler SPEthernetDataType

and look for "Driver: com.apple.driver.AppleEthernetRL" and "AVB Support: Yes"

2. Turn Wi-Fi off, use only the built-in Ethernet, and try AirPlay audio to a HomePod.

If it fails for you too, please file your own report in Feedback Assistant and mention FBxxxxxxxx. Duplicate reports help Apple prioritize the fix.

Workaround for now: a USB Ethernet adapter without AVB support, or Wi-Fi.

Mac mini (M6, 2026)

Posted on Nov 8, 2026 2:16 PM

Answer 1

Top-ranking reply

Churria Author

Level 1

18 points

Nov 9, 2026 10:37 AM in response to Churria

Update – correction and a fully wired workaround

Further testing narrowed the bug down much more precisely.

What I tested (Mac mini M6, built-in Ethernet en0, macOS 27.2):

| IPv6 on built-in Ethernet | Wi-Fi | AirPlay to HomePods |

|---------------------------|-------|---------------------|

| On | On | Fails |

| On | Off | Fails |

| Off | On | Works (over Wi-Fi) |

| Off | Off | Works (over Ethernet, IPv4) |

So the built-in port itself is fine for AirPlay. What fails is the clock sync (PTP) over IPv6 on the built-in port. When IPv6 is disabled on that port, AirPlay falls back to IPv4 on the same cable and works normally.

Workaround (everything stays wired), DISABLE IPv6:

1. Find your Ethernet service name:

networksetup -listallnetworkservices

2. Disable IPv6 on it:

sudo networksetup -setv6off "Ethernet"

(or System Settings > Network > Ethernet > Details > TCP/IP > Configure IPv6: Off)

3. Turn Wi-Fi off, or leave it on without joining a network if you use AirDrop/Handoff/Universal Control.

4. Try AirPlay to your HomePods again.

The setting survives reboots. To check it:

networksetup -getinfo "Ethernet" | grep -i ipv6 -> "IPv6: Off"

Side effects are minimal on a home network: AirDrop, Handoff, iCloud, file and screen sharing keep working over IPv4. The only thing you lose is IPv6 internet on that port, if your ISP provides it.

To revert once Apple fixes it:

sudo networksetup -setv6automatic "Ethernet"

If you have a Mac mini M6 / M5 Pro or a Mac Studio M5 and see the same problem, please try this, post your results here, and file a report in Feedback Assistant mentioning FBxxxxxxxx. I've sent Apple these findings as well. (***)

[Edited by Moderator]