Homepod private address

Follow

Stephen Ball

• March 06, 2022 10:32
• Edited

Since using the firewalla I occasionally get an "unknown" device appears on my network which Firewalla said has MAC randomisation on...

I had double-checked both Macs, iPhones, iPads and my Apple Watch to make sure it was disabled

This evening it appeared again and I was able to ping it so I ran the "discovery" app on my Mac to see if it had any Bonjour services running, I find it being one of my Homepods

 

However, firewalla is showing that Homepod is connected as 192.168.115.103 but it clearly isn't as I can't ping it

Any idea what is going on here and how I can stop this happening, Homepods don't have mac randomisation that I am aware of so there is no way to turn it off :|

1

• 

  Firewalla

  • March 06, 2022 01:44

  anything x6:... is a private MAC; do you have extenders running? (I am not aware that homepod can randomize MAC ...)

  0

  Comment actions Permalink
• 

  Stephen Ball

  • March 06, 2022 10:34

  No, I don't have extenders running... that said I was clearly half asleep when debugging this last night as the screenshot of discovery clearly says Apple TV not HomePod. 🤦‍♂️ Although the Apple TV doesn't have randomized MAC either. Will have to play around again next time it happens.

  0

  Comment actions Permalink
• 

  Stephen Ball

  • March 08, 2022 21:57

  So here it is again, Firewalla with a new device with MAC randomisation on, no IPv4 address but an IPv6 address

  Discovery shows ieee1588, meshcop, raop, homekit, airplay, sleep-proxy, srpl-tls and companion-link services all on that  IPv6 address

   

  

  The places it mentions an IPv4 address matches up with the Bedroom Apple TV

  

   

  0

  Comment actions Permalink
• 

  Garrett Cox

  • March 22, 2022 22:22

  I'd check the blocked routes to confirm it looks like homepod traffic, preferably with VPN off... especially since the VPN isn't getting used anyways (internet disabled). I've seen this with Apple Watches also. 

  0

  Comment actions Permalink
• 

  Jan Bird

  • March 12, 2023 07:57

  Have you figured it out? Having the same problem with my HomePods+AppleTV... Thanks!

  0

  Comment actions Permalink
• 

  Firewalla

  • March 12, 2023 16:38

  Do you have the latest firmware from apple? I vaguely (may be I was just dreaming), apple latest release fixed a few things, and may include this. 

  0

  Comment actions Permalink
• 

  Jan Bird

  • March 12, 2023 16:54

  Yes. They fixed a lot of HomeKit stuff in 16.4… but this behaviour remains unchanged.

  0

  Comment actions Permalink
• 

  Firewalla

  • March 13, 2023 16:06

  It is going to be hard for us to do exceptions via the device name. The reason is, many parents uses the device quarantine feature to block kids ... and if they name their box HomePod, then it will become a work around for naughty stuff.

  0

  Comment actions Permalink
• 

  Jan Bird

  • March 13, 2023 16:36

  I understand, idea was for the feature to be optional, so it would be up to them to consider risks/benefits. More, it’s common to keep HomePod hostname as homepod, but it can freely be renamed in Home app. I’m open to other ideas, this was just a suggestion. Yesterday, I simply restarted AppleTV and boom - new private IP in quarantine (Homepod)… again :)

  0

  Comment actions Permalink

Please sign in to leave a comment.