Mastodawn

Has anyone played around with the #Thread radio on M3+ MacBooks?

Seems like com.apple.threadradiod and com.apple.ThreadCommissionerService contain a full OpenThread stack!

I opened the Home app and threadradiod started right up, and created the following new interface!

utun9: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
    options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
    inet6 fe80::68a6:4bd7:cb50:b21d%utun9 prefixlen 64 scopeid 0x27
    inet6 fd11:35aa:6877:0:45ad:8e81:b682:dbc3 prefixlen 64
    inet6 fd11:35aa:6877::ff:fe00:2408 prefixlen 64 deprecated
    inet6 fd72:683:99a0:0:3997:be43:1c3c:b6b8 prefixlen 64
    nd6 options=201<PERFORMNUD,DAD>

Show thread

JJTech 4d ago

I used Wireshark on threadradiod's utun interface on my Mac, and when I toggle a Matter-over-Thread lamp using Home app I see #Matter packets sent on port 5540!

It seems like after a minute or two the Home app figures out there is a Thread Border Router and shuts down utun9 in favor of just using the router.

Show thread

JJTech

You can configure the #Thread interface using the private CoreThreadRadio.framework...

Unfortunately it requires the entitlement com.apple.private.ctr.thread