Multiple hifiberryos systems running on same network conflict

Daansnijders62

January 30, 2022 12:16

None

I am a heavy duty HiFiBerry systems:

1) Pi 3b+ / hifiberryos / DAC+ DSP

2) Pi 3b+ / hifiberryos / DAC+ Pro

3) Pi 3b+ / hifiberryos / DAC+

I am using airplay / spotify connect /OpenHome.

I am experiencing very strange behaviour when using spotify. After a short while I cannot connect anymore to one of the systems in the spotify app on android phone, although they are still listed. When i move 2 systems (out of the 3) to moOde Audio with Librespot for spotify, it all works fine and stable. Only the DAC+DSP is now running on hifiberryos, the other 2 on moode audio.

anyone having the same experience?

HifiberryOS with vollibrespot seems to work fine with 1 player on the network, but causes issues with multiple players. Have it all working with a combi of hifiberryos and moode audio, but would like to move to hifiberryos for consistency and simplicity.

Thanks Daan

Date Votes

33 comments

0

HiFiBerry team January 31, 2022 06:13

Did you name the devices differently? If you still have them all running with the default "hifiberry" name, this will create problems.

Comment actions Permalink
0

Daansnijders62 January 31, 2022 08:21

Yes, all 3 instances have unique names.

Comment actions Permalink
0

Richardpub January 31, 2022 23:26

I have similar problems with 3 Raspberry Pi3B+ and Amp2

I started from scratch with HifiBerryOS on my 3 Pi with 3 different fixed IP and different names.
It worked for a few days and now I have 2 that are no longer visible on the network. The 3rd one works perfectly in pure WIFI.
I use these 3 IPs with the Spotify interface.
Otherwise the hiffiberry amp2 hat is really nice with decent speakers....

I have pretty close issues with 3 Raspberry Pi3B+ and Amp2. After a while, the raspberry goes to sleep after a few days or hours.... And I don't have active WIFI anymore and the reboots don't change anything.
Whether they are connected in wifi or in Ethernet doesn't change anything, and I have no more ping for 2 of the 3 raspberry pi3 associated with Amp2 cards.
I tried to see if rebooting the box, the switch, the WIFI or the raspberry would change something, but still no ping return on the corresponding IP. Yet sometimes I find them in my Spotify app after several days or weeks???

the problems continue with Hifiberry. the devices whether connected by wifi or ethernet disappear from the Spotify application and the search for fixed IPs does not give anything either.
maybe a problem with airport or with bluetooth ???
the problems continue with Hifiberry. the devices connected by wifi or ethernet disappear from the Spotify application and the search for fixed IP addresses does not give anything either.
maybe a problem with airport or with bluetooth ???

Last discovery, one of the Pi3 is invisible and connectable with airport on Iphone7, and yet it is not connectable by its IP, but not the other 2???
Thanks for your help...
*** Translated with www.DeepL.com/Translator (free version) ***

Comment actions Permalink
0

Daansnijders62 February 01, 2022 15:55

Thanks Richardpub, very similar experience indeed.
After a couple of hours of more testing, ended up again not being able to one of the players in Spotify cliënt app.
I switched back to moode audio on all three players. This works without issues. I am only using hifiberryos for my DAC+DSP to write setting to memory and then switch back to moode. Hope hifiberry can get this fixed for us in the near future / upcoming releases.

Comment actions Permalink
0

Richardpub February 02, 2022 23:24

My 2 rpi3 and amp2 are always unstable they work for a while then disappear one or the other without warning, then can come back for no visible reason. Maybe a conflict with airplay, blutooth or a cambridge streamer.
Currently one of them does not respond to the ping but it is visible in the airplay and if I cut the blutooth, it disappears from the airplay in spotify on Iphone

Comment actions Permalink
0

Richardpub February 03, 2022 18:11

To report an instability of Raspberry 3 with Amp2, it seems that Bluetooth is involved in the problems, and prevents and disrupts the wifi and Ethernet connection.

I have not really found the source, nor the solution to my worries.

And this time, it was the restarting of all the devices following a power outage that solved all the worries.
I let them run like this with the HifiberryOs and I don't think anything is really solved....!!!
If anyone has any idea how to really solve this problem

Comment actions Permalink
0

Daansnijders62 February 05, 2022 10:38

Hi Richard, thanks for the update.

I disabled bluetooth (not using that anyway) with:

sudo nano /boot/config.txt and added,

dtoverlay=disable-bt

I have now 1 Rpi 3b+ with DAC+ Pro running without issues on hifiberryos for 48 hours.

Did you test this also?

thanks, daan

Comment actions Permalink
0

Richardpub February 06, 2022 10:25

I just disabled the bluetooth on the first raspberry P3B. I'll let it run for a while, to see if it will solve the problem.
I have a Cambridge CXN streamer next door that can also use blutooth, even if I only use it in Wifi. This could be one of the causes of the problem. When the installation becomes important it is not always easy to find the cause of the problems.

Comment actions Permalink
0

Daansnijders62 February 06, 2022 11:00

I just added #2 running on hifiberryos with bt disabled.

no luck, problems started again. so I switched back to moode audio all 3 rpi 3b+, since that works flawlessly.

Very eager to get you feedback Richards.

Also hope hifiberry (daniel) will respond and comes with a resolution.

cheers, Daan

Comment actions Permalink
0

Daansnijders62 February 09, 2022 15:15

after digging into this a bit more...this might very well be related to a known avahi issue (a service broadly used for mdns membership and services publication, resulting into multiple hostnames published for a single device...see link..

https://github.com/lathiat/avahi/issues/117

i saw this happening multiple times by running avahi-browse --all on one of hosts on my home network.

what worked for me whenever this occurs is a reboot of the router....immediately spotify / airplay / upnp discovery starts working and also ssh service...

Hope this will help others..

cheers Daan

Comment actions Permalink
0

Richardpub February 09, 2022 16:17

Restarting the router is your solution?? Obviously the budget is deeper. In my case, restarting everything together is the solution. but it's just temporary as a solution. it would be nice if Hifiberry solved the problem

Comment actions Permalink
0

Daansnijders62 February 09, 2022 16:20

thought you would be interested in findings like avahi bug...never mind...lets close this conversation.

Comment actions Permalink
0

HiFiBerry team February 09, 2022 16:23

We're happy to hear any ideas how to fix this. As we don't know the internals on Spotify, we can only wait for somebody that has a good idea what might be causing it and how to fix this. You could report your avahi-output when it works and when it stopped working.

Comment actions Permalink
0

Daansnijders62 February 09, 2022 17:03

Will try to reproduce this and publish the avahi output....may take some time ..stay tuned :-).

Comment actions Permalink
0

Richardpub February 09, 2022 17:34

I am interested in your solution, but the avahi bug seems to be a good way of research but I do not have enough skills to solve this part and a support by the Hifiberry team would be welcome because for the moment nothing seems to come from using spotify

Comment actions Permalink
0

Daansnijders62 February 09, 2022 18:37

HiFiBerry team

I have a very large log file to share...how do you want me to share this?

I cannot attach a document...

Good news is that I can consistently reproduce the issue.

mdns avahi gets confused by name changes of he host name.

avahi-browse --all shows this well (I have this all in the document).

rebooting the router seems to clear all mdns caches in the network.

Please advise how to share this document (or should i simply copy and paste it here)..

Cheers, daan

Comment actions Permalink
0

HiFiBerry team February 10, 2022 07:41

It's probably best to post it here. Can you explain what you mean by "name changes of the host name"? Do you have both WiFi and Ethernet active?

Comment actions Permalink
0
Daansnijders62 February 10, 2022 07:55
sure, will do....

I only have wifi active, not using ethernet. After a fresh install the name of the raspberry Pi 3b+ with hifiberry DAC card is 'hifiberry'. Since I have 3 of them, I need to make these names unique. So I need to change these names. That is what I am doing after boot up and connecting these players to the local network.

see below the results:

Hifiberryos host name conflict issue mdsn / avahi services during name change:
- Problem / Issue with hifiberryos using Airplay / Spotify & Openhome discovery on home network.
- After adding a new hifiberryos player, Spotify app cannot discover and connect to players.
- Same is happening to Airplay. OpenHome and also SSH server stops being accessible.
It seems to be caused by host naming conflicts from the mdse / avahi services after a host name change (during initial setup)

See steps and avahi-browse —all logs below resulting in host naming conflicts.

Step 1: Adding a new player to home network:
Raspberry Pi 3b+ with HifiBerry DAC+

Fresh install of hifiberryos image

config via hifiberryos hotspot.

change wifi to local SSID

rerun avahi-browse scan

Hifiberry added to mdsn

——

pi@Pimoroni:~ $ avahi-browse --all

+ wlan0 IPv6 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv4 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv6 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv4 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv6 Apple TV HD _companion-link._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv4 Apple TV HD _companion-link._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv6 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv4 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv6 Apple TV HD _airplay._tcp local

+ wlan0 IPv6 Sonos _airplay._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv4 HiFiBerry _airplay._tcp local

+ wlan0 IPv4 Apple TV HD _airplay._tcp local

+ wlan0 IPv4 Sonos _airplay._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv6 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv6 Spotify Group Session [4EDra] _spotify-social-listening._tcp local

+ wlan0 IPv4 Spotify Group Session [4EDra] _spotify-social-listening._tcp local

+ wlan0 IPv6 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv6 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv6 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv6 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv6 0D6C1D2B8343@Zolder AirTunes Remote Audio local

+ wlan0 IPv6 9837B4D4B99B@Pimoroni AirTunes Remote Audio local

+ wlan0 IPv4 A688790DC9D6@HiFiBerry AirTunes Remote Audio local

+ wlan0 IPv4 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv4 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv4 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv4 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv4 0D6C1D2B8343@Zolder AirTunes Remote Audio local

+ wlan0 IPv4 9837B4D4B99B@Pimoroni AirTunes Remote Audio local

+ wlan0 IPv6 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv6 Zolder Microsoft Windows Network local

+ wlan0 IPv6 Pimoroni Microsoft Windows Network local

+ wlan0 IPv4 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv4 Zolder Microsoft Windows Network local

+ wlan0 IPv4 Pimoroni Microsoft Windows Network local

+ wlan0 IPv6 Studeerkamer _device-info._tcp local

+ wlan0 IPv6 Zolder _device-info._tcp local

+ wlan0 IPv6 Pimoroni _device-info._tcp local

+ wlan0 IPv4 Studeerkamer _device-info._tcp local

+ wlan0 IPv4 Zolder _device-info._tcp local

+ wlan0 IPv4 Pimoroni _device-info._tcp local

+ wlan0 IPv6 Studeerkamer Remote Disk Management local

+ wlan0 IPv6 Zolder Remote Disk Management local

+ wlan0 IPv6 Pimoroni Remote Disk Management local

+ wlan0 IPv4 Studeerkamer Remote Disk Management local

+ wlan0 IPv4 Zolder Remote Disk Management local

+ wlan0 IPv4 Pimoroni Remote Disk Management local

+ wlan0 IPv6 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv6 moOde audio player: Zolder Web Site local

+ wlan0 IPv6 moOde audio player: Pimoroni Web Site local

+ wlan0 IPv4 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv4 moOde audio player: Zolder Web Site local

+ wlan0 IPv4 moOde audio player: Pimoroni Web Site local

+ wlan0 IPv4 HiFiBerry _beocreate._tcp local

+ wlan0 IPv4 Music Player @ hifiberry Music Player Daemon local

+ wlan0 IPv4 hifiberry SFTP File Transfer local

+ wlan0 IPv4 hifiberry SSH Remote Terminal local

Step 2: host name change from hifiberry to keuken (kitchen in Dutch)

Hifiberry name changed to ‘keuken’ during initial setup

ran a rescan avahi-browse —all

Keuken is added to mdns registry, but hifiberry still present in registry for same host (IP address)!

pi@Pimoroni:~ $ avahi-browse --all

+ wlan0 IPv6 Music Player @ hifiberry Music Player Daemon local

+ wlan0 IPv4 Music Player @ hifiberry Music Player Daemon local

+ wlan0 IPv6 keuken SSH Remote Terminal local

+ wlan0 IPv4 keuken SSH Remote Terminal local

+ wlan0 IPv6 keuken SFTP File Transfer local

+ wlan0 IPv4 keuken SFTP File Transfer local

+ wlan0 IPv6 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv4 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv6 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv4 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv6 Apple TV HD _companion-link._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv4 Apple TV HD _companion-link._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv6 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv4 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv6 Keuken _airplay._tcp local

+ wlan0 IPv6 Apple TV HD _airplay._tcp local

+ wlan0 IPv6 Sonos _airplay._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv4 Keuken _airplay._tcp local

+ wlan0 IPv4 Apple TV HD _airplay._tcp local

+ wlan0 IPv4 Sonos _airplay._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv6 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv6 Spotify Group Session [4EDra] _spotify-social-listening._tcp local

+ wlan0 IPv4 Spotify Group Session [4EDra] _spotify-social-listening._tcp local

+ wlan0 IPv6 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv6 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv6 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv6 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv6 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv6 0D6C1D2B8343@Zolder AirTunes Remote Audio local

+ wlan0 IPv6 9837B4D4B99B@Pimoroni AirTunes Remote Audio local

+ wlan0 IPv4 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv4 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv4 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv4 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv4 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv4 0D6C1D2B8343@Zolder AirTunes Remote Audio local

+ wlan0 IPv4 9837B4D4B99B@Pimoroni AirTunes Remote Audio local

+ wlan0 IPv6 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv6 Zolder Microsoft Windows Network local

+ wlan0 IPv6 Pimoroni Microsoft Windows Network local

+ wlan0 IPv4 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv4 Zolder Microsoft Windows Network local

+ wlan0 IPv4 Pimoroni Microsoft Windows Network local

+ wlan0 IPv6 Studeerkamer _device-info._tcp local

+ wlan0 IPv6 Zolder _device-info._tcp local

+ wlan0 IPv6 Pimoroni _device-info._tcp local

+ wlan0 IPv4 Studeerkamer _device-info._tcp local

+ wlan0 IPv4 Zolder _device-info._tcp local

+ wlan0 IPv4 Pimoroni _device-info._tcp local

+ wlan0 IPv6 Studeerkamer Remote Disk Management local

+ wlan0 IPv6 Zolder Remote Disk Management local

+ wlan0 IPv6 Pimoroni Remote Disk Management local

+ wlan0 IPv4 Studeerkamer Remote Disk Management local

+ wlan0 IPv4 Zolder Remote Disk Management local

+ wlan0 IPv4 Pimoroni Remote Disk Management local

+ wlan0 IPv6 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv6 moOde audio player: Zolder Web Site local

+ wlan0 IPv6 moOde audio player: Pimoroni Web Site local

+ wlan0 IPv4 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv4 moOde audio player: Zolder Web Site local

+ wlan0 IPv4 moOde audio player: Pimoroni Web Site local

+ wlan0 IPv4 Keuken _beocreate._tcp local

Step 3: Reboot of host keuken

and after reboot of host keuken

rerun of avahi-browse —all

notice that there are still listings for hifiberry

wlan0 IPv6 Music Player @ hifiberry

wlan0 IPv4 Music Player @ hifiberry

and more..

ssh service is also not working anymore….resulting in broken pipe...

root@192.168.1.120's password:

client_loop: send disconnect: Broken pipe

results of scan ...

pi@Studeerkamer:~ $ avahi-browse --all

+ wlan0 IPv6 Music Player @ keuken Music Player Daemon local

+ wlan0 IPv6 Music Player @ hifiberry Music Player Daemon local

+ wlan0 IPv4 Music Player @ keuken Music Player Daemon local

+ wlan0 IPv4 Music Player @ hifiberry Music Player Daemon local

+ wlan0 IPv6 keuken SSH Remote Terminal local

+ wlan0 IPv4 keuken SSH Remote Terminal local

+ wlan0 IPv6 keuken SFTP File Transfer local

+ wlan0 IPv4 keuken SFTP File Transfer local

+ wlan0 IPv6 Studeerkamer _spotify-connect._tcp local

+ wlan0 IPv6 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv4 Keuken _spotify-connect._tcp local

+ wlan0 IPv4 Studeerkamer _spotify-connect._tcp local

+ wlan0 IPv4 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv6 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv6 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv6 Zolder Microsoft Windows Network local

+ wlan0 IPv6 Pimoroni Microsoft Windows Network local

+ wlan0 IPv4 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv4 Zolder Microsoft Windows Network local

+ wlan0 IPv4 Pimoroni Microsoft Windows Network local

+ wlan0 IPv6 Studeerkamer _device-info._tcp local

+ wlan0 IPv6 Zolder _device-info._tcp local

+ wlan0 IPv6 Pimoroni _device-info._tcp local

+ wlan0 IPv4 Studeerkamer _device-info._tcp local

+ wlan0 IPv4 Zolder _device-info._tcp local

+ wlan0 IPv4 Pimoroni _device-info._tcp local

+ wlan0 IPv6 Studeerkamer Remote Disk Management local

+ wlan0 IPv6 Zolder Remote Disk Management local

+ wlan0 IPv6 Pimoroni Remote Disk Management local

+ wlan0 IPv4 Studeerkamer Remote Disk Management local

+ wlan0 IPv4 Zolder Remote Disk Management local

+ wlan0 IPv4 Pimoroni Remote Disk Management local

+ wlan0 IPv6 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv6 moOde audio player: Zolder Web Site local

+ wlan0 IPv6 moOde audio player: Pimoroni Web Site local

+ wlan0 IPv4 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv4 moOde audio player: Zolder Web Site local

+ wlan0 IPv4 moOde audio player: Pimoroni Web Site local

+ wlan0 IPv6 Spotify Group Session [4EDra] _spotify-social-listening._tcp local

+ wlan0 IPv4 Spotify Group Session [4EDra] _spotify-social-listening._tcp local

+ wlan0 IPv6 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv4 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv6 Keuken _airplay._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv6 Sonos _airplay._tcp local

+ wlan0 IPv6 Apple TV HD _airplay._tcp local

+ wlan0 IPv4 Keuken _airplay._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv4 Sonos _airplay._tcp local

+ wlan0 IPv4 Apple TV HD _airplay._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv6 Apple TV HD _companion-link._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv4 Apple TV HD _companion-link._tcp local

+ wlan0 IPv6 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv4 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv6 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv6 9837B4D4B99B@Pimoroni AirTunes Remote Audio local

+ wlan0 IPv6 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv6 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv6 0D6C1D2B8343@Zolder AirTunes Remote Audio local

+ wlan0 IPv6 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv6 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv4 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv4 9837B4D4B99B@Pimoroni AirTunes Remote Audio local

+ wlan0 IPv4 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv4 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv4 0D6C1D2B8343@Zolder AirTunes Remote Audio local

+ wlan0 IPv4 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv4 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv4 Keuken _beocreate._tcp local

+ wlan0 IPv4 Spotify Group Session [1q1zr] _spotify-social-listening._tcp local

+ wlan0 IPv6 Spotify Group Session [1q1zr] _spotify-social-listening._tcp local

- wlan0 IPv4 Spotify Group Session [4EDra] _spotify-social-listening._tcp local

- wlan0 IPv6 Spotify Group Session [4EDra] _spotify-social-listening._tcp local

Step 4: Rebooting router and access point as a remedy…

rerun of avahi-browse —all

All hifiberry listings are gone….only keuken present as host.

ssh server is also approachable ..

dsnijders@Daans-Air ~ % ssh root@192.168.1.120

root@192.168.1.120's password: xxxxxxxxx

#

pi@Studeerkamer:~ $ avahi-browse --all

+ wlan0 IPv6 Music Player @ keuken Music Player Daemon local

+ wlan0 IPv4 Music Player @ keuken Music Player Daemon local

+ wlan0 IPv6 keuken SSH Remote Terminal local

+ wlan0 IPv4 keuken SSH Remote Terminal local

+ wlan0 IPv6 keuken SFTP File Transfer local

+ wlan0 IPv4 keuken SFTP File Transfer local

+ wlan0 IPv6 Keuken _airplay._tcp local

+ wlan0 IPv4 Keuken _airplay._tcp local

+ wlan0 IPv6 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv4 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv6 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv4 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv6 Studeerkamer _device-info._tcp local

+ wlan0 IPv4 Studeerkamer _device-info._tcp local

+ wlan0 IPv6 Studeerkamer Remote Disk Management local

+ wlan0 IPv4 Studeerkamer Remote Disk Management local

+ wlan0 IPv6 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv6 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv4 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv4 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv4 Keuken _beocreate._tcp local

+ wlan0 IPv4 Apple TV HD _airplay._tcp local

+ wlan0 IPv4 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv6 Apple TV HD _airplay._tcp local

+ wlan0 IPv6 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv4 Sonos _airplay._tcp local

+ wlan0 IPv4 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv6 Sonos _airplay._tcp local

+ wlan0 IPv6 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv6 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv4 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv6 Studeerkamer _spotify-connect._tcp local

+ wlan0 IPv4 Studeerkamer _spotify-connect._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv4 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv4 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv6 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv6 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv6 Keuken _spotify-connect._tcp local

+ wlan0 IPv4 Keuken _spotify-connect._tcp local

+ wlan0 IPv4 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv4 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv4 Apple TV HD _companion-link._tcp local

+ wlan0 IPv4 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv6 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv6 Apple TV HD _companion-link._tcp local

+ wlan0 IPv6 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

Step 5: Adding a second hifiberryos player to local network with HiFiBerry DAC+ Pro on hifiberryos

configured thru hotspot.

connected to wifi SSID

name change from hifiberry to Zolder

Rescan avahi-browse —all

same results

pi@Studeerkamer:~ $ avahi-browse --all

+ wlan0 IPv6 Spotify Group Session [3wXG5] _spotify-social-listening._tcp local

+ wlan0 IPv4 Spotify Group Session [3wXG5] _spotify-social-listening._tcp local

+ wlan0 IPv6 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv4 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv6 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv4 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv6 Apple TV HD _companion-link._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv4 Apple TV HD _companion-link._tcp local

+ wlan0 IPv6 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv4 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv6 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv6 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv6 Music Player @ zolder Music Player Daemon local

+ wlan0 IPv6 Music Player @ hifiberry Music Player Daemon local

+ wlan0 IPv6 Music Player @ keuken Music Player Daemon local

+ wlan0 IPv4 Music Player @ zolder Music Player Daemon local

+ wlan0 IPv4 Music Player @ hifiberry Music Player Daemon local

+ wlan0 IPv4 Music Player @ keuken Music Player Daemon local

+ wlan0 IPv6 zolder SSH Remote Terminal local

+ wlan0 IPv6 keuken SSH Remote Terminal local

+ wlan0 IPv4 zolder SSH Remote Terminal local

+ wlan0 IPv4 keuken SSH Remote Terminal local

+ wlan0 IPv6 zolder SFTP File Transfer local

+ wlan0 IPv6 keuken SFTP File Transfer local

+ wlan0 IPv4 zolder SFTP File Transfer local

+ wlan0 IPv4 keuken SFTP File Transfer local

+ wlan0 IPv6 Zolder _airplay._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv6 Sonos _airplay._tcp local

+ wlan0 IPv6 Apple TV HD _airplay._tcp local

+ wlan0 IPv6 Keuken _airplay._tcp local

+ wlan0 IPv4 Zolder _airplay._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv4 Sonos _airplay._tcp local

+ wlan0 IPv4 Apple TV HD _airplay._tcp local

+ wlan0 IPv4 Keuken _airplay._tcp local

+ wlan0 IPv6 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv4 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv6 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv4 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv6 Studeerkamer _device-info._tcp local

+ wlan0 IPv4 Studeerkamer _device-info._tcp local

+ wlan0 IPv6 Studeerkamer Remote Disk Management local

+ wlan0 IPv4 Studeerkamer Remote Disk Management local

+ wlan0 IPv6 8E3E7D0A182F@Zolder AirTunes Remote Audio local

+ wlan0 IPv6 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv6 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv6 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv6 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv6 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv4 8E3E7D0A182F@Zolder AirTunes Remote Audio local

+ wlan0 IPv4 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv4 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv4 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv4 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv4 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv4 Zolder _beocreate._tcp local

+ wlan0 IPv4 Keuken _beocreate._tcp local

Step 6: Again a reboot of router and access point seems to be the remedy.

reboot router and access point

rescan avahi-browse —-all

see results

pi@Studeerkamer:~ $ avahi-browse --all

+ wlan0 IPv6 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv4 moOde audio player: Studeerkamer Web Site local

+ wlan0 IPv6 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv4 Studeerkamer Microsoft Windows Network local

+ wlan0 IPv6 Studeerkamer _device-info._tcp local

+ wlan0 IPv4 Studeerkamer _device-info._tcp local

+ wlan0 IPv6 Studeerkamer Remote Disk Management local

+ wlan0 IPv4 Studeerkamer Remote Disk Management local

+ wlan0 IPv6 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv4 8E3E7D0A182F@Zolder AirTunes Remote Audio local

+ wlan0 IPv4 A3D786F5E879@Studeerkamer AirTunes Remote Audio local

+ wlan0 IPv4 Zolder _beocreate._tcp local

+ wlan0 IPv4 Zolder _airplay._tcp local

+ wlan0 IPv4 zolder SFTP File Transfer local

+ wlan0 IPv4 zolder SSH Remote Terminal local

+ wlan0 IPv4 Music Player @ zolder Music Player Daemon local

+ wlan0 IPv6 8E3E7D0A182F@Zolder AirTunes Remote Audio local

+ wlan0 IPv6 Music Player @ zolder Music Player Daemon local

+ wlan0 IPv6 zolder SSH Remote Terminal local

+ wlan0 IPv6 zolder SFTP File Transfer local

+ wlan0 IPv6 Zolder _airplay._tcp local

+ wlan0 IPv6 Sonos _airplay._tcp local

+ wlan0 IPv6 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv6 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv6 Music Player @ keuken Music Player Daemon local

+ wlan0 IPv6 keuken SSH Remote Terminal local

+ wlan0 IPv6 keuken SFTP File Transfer local

+ wlan0 IPv6 Keuken _airplay._tcp local

+ wlan0 IPv4 Sonos _airplay._tcp local

+ wlan0 IPv4 48A6B83B26BF@Sonos AirTunes Remote Audio local

+ wlan0 IPv4 A688790DC9D6@Keuken AirTunes Remote Audio local

+ wlan0 IPv4 Music Player @ keuken Music Player Daemon local

+ wlan0 IPv4 keuken SSH Remote Terminal local

+ wlan0 IPv4 keuken SFTP File Transfer local

+ wlan0 IPv4 Keuken _airplay._tcp local

+ wlan0 IPv4 Keuken _beocreate._tcp local

+ wlan0 IPv4 Apple TV HD _airplay._tcp local

+ wlan0 IPv4 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv6 Apple TV HD _airplay._tcp local

+ wlan0 IPv6 44C65D76ED53@Apple TV HD AirTunes Remote Audio local

+ wlan0 IPv6 Studeerkamer _spotify-connect._tcp local

+ wlan0 IPv4 Studeerkamer _spotify-connect._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv4 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv6 Daan___s MacBook Air _airplay._tcp local

+ wlan0 IPv6 1C9180C28945@Daan___s MacBook Air AirTunes Remote Audio local

+ wlan0 IPv6 Keuken _spotify-connect._tcp local

+ wlan0 IPv6 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv4 Keuken _spotify-connect._tcp local

+ wlan0 IPv4 Zolder _spotify-connect._tcp local

+ wlan0 IPv4 Sonos-48A6B887C47E@Sonos _sonos._tcp local

+ wlan0 IPv4 Sonos-48A6B887C44E@Sonos _sonos._tcp local

+ wlan0 IPv4 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv4 Apple TV HD _companion-link._tcp local

+ wlan0 IPv4 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv6 70-35-60-63.1 Apple TV HD _sleep-proxy._udp local

+ wlan0 IPv6 Apple TV HD _companion-link._tcp local

+ wlan0 IPv6 025DADF0-C2EB-5806-A768-BE6C54F763F3 _homekit._tcp local

+ wlan0 IPv6 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv6 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv4 sonos48A6B83B26BF _spotify-connect._tcp local

+ wlan0 IPv4 Sonos-48A6B83B26BF@Sonos _sonos._tcp local

+ wlan0 IPv6 Zolder _spotify-connect._tcp local

+ wlan0 IPv4 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv6 Daan___s MacBook Air _companion-link._tcp local

+ wlan0 IPv6 Sonos-48A6B887C44E@Sonos _sonos._tcp local

Conclusions / Observations:

Looks like host name change are not processed well.

Looks like MPD might cause the problem!? not sure...

I did the same test procedure with a moode audio host, including a host name change after initial setup. Moode audio does NOT show this behaviour, although moods also uses the same mdns / avahi service. This proves (to me al least) that it is NOT a router issue..since the moode hosts run on same home network..

Hope this helps the HifiBerry support team a bit, did my best te re-produce this behaviour consistently…and it does...
Comment actions Permalink
0

HiFiBerry team February 10, 2022 08:00

Ok, just for me to understand: You're talking about a name change during operation. However, what happens when you reboot after the name change?

Comment actions Permalink
0

Daansnijders62 February 10, 2022 08:18

That is in the log file .... the original name 'hifiberry' still shows up in mdns registry. And causes the problem...

Only after a reboot of router it will be gone. Please read and go thru the steps and you will see what is happening.

Comment actions Permalink
0

HiFiBerry team February 10, 2022 08:23

Hmm, I can't reproduce this here. Not sure where this is still configured in your installation.

Please search for this as follows:

grep -r HiFiBerry /etc

Comment actions Permalink
0

Daansnijders62 February 10, 2022 08:28

# grep -r HiFiBerry /etc

/etc/mpd.conf.default: name "HiFiBerry"

/etc/hifiberry_raat.conf: "vendor": "HiFiBerry",

/etc/upmpdcli.conf:ohmanufacturername = HiFiBerry

/etc/upmpdcli.conf:ohmodelname = HiFiBerryOS device

/etc/issue:Welcome to HiFiBerryOS

/etc/mpd.conf: name "HiFiBerry"

/etc/tempap-hostapd.conf:ssid=HiFiBerry Setup efb3248c

/etc/tempap-hostapd.conf:ssid=HiFiBerry Setup efb3248c

/etc/tempap-hostapd.conf:ssid=HiFiBerry Setup efb3248c

/etc/tempap-hostapd.conf:ssid=HiFiBerry Setup efb3248c

/etc/tempap-hostapd.conf:ssid=HiFiBerry Setup efb3248c

/etc/tempap-hostapd.conf:ssid=HiFiBerry Setup efb3248c

/etc/tempap-hostapd.conf:ssid=HiFiBerry Setup efb3248c

/etc/tempap-hostapd.conf:ssid=HiFiBerry Setup efb3248c

/etc/tempap-hostapd.conf:ssid=HiFiBerry Setup efb3248c

/etc/systemd/system/multi-user.target.wants/hifiberry.target:Description=HiFiBerry target

/etc/systemd/system/multi-user.target.wants/hifiberry-detect.service:Description=HiFiBerry detect

/etc/systemd/system/multi-user.target.wants/hifiberry-detect.service:ExecStartPre=/opt/hifiberry/bin/bootmsg "Detecting HiFiBerry sound card"

/etc/systemd/system/multi-user.target.wants/pc-startup.service:Description=HiFiBerry startup

/etc/systemd/system/multi-user.target.wants/pc-startup-finish.service:Description=HiFiBerry startup

/etc/systemd/system/multi-user.target.wants/sigmatcp.service:Description=SigmaTCP Server for HiFiBerry DSP

/etc/systemd/system/multi-user.target.wants/hifiberry-finish.service:Description=HiFiBerry final

/etc/beocreate/product-information.json:{"modelID":"hifiberry","modelName":"HiFiBerry","productImage":false,"bonjourEnabled":true,"systemNameApprovedByUser":true}

Comment actions Permalink
0

HiFiBerry team February 10, 2022 08:53

Ok. Nothing here.

Do I understand you correctly:
- You rename all systems to a unique name
- You rebooted all systems
- You rebooted your router

After doing all this, the incorrect HiFiBerry name comes back in MDNS?

Comment actions Permalink
0

Daansnijders62 February 10, 2022 09:03

allmost:

only after rebooting router and access point, the incorrect hifiberry name does NOT coming back anymore...

so that is my remedy for now....after adding a new player or renaming one of them I reboot router and access point...

so I have a work around, but still is the wrong behaviour.

Moode audio does not show this behaviour, after a name change, the old mdns name is done. so somehow they publish a 'mdns goodbye message for the old name' ...

does this help?

Comment actions Permalink
0

HiFiBerry team February 10, 2022 09:09

Yes, but not sure how we can fix it.At least the workaround is clear now:
- After a name change reboot the system AND restart the router if it still cached the old name

Comment actions Permalink
0

Daansnijders62 February 10, 2022 09:13

could very well be a avahi-daemon bug...maybe check if you are using the latest version...there are a lot of bug reports / issues related to this in the avahi community...good luck and please keep us posted.

ps: love hifiberry boards and os, and happy to help out where i can.

Comment actions Permalink

Daansnijders62 March 17, 2022 10:39

question: is this fixed now with the mdns fix in the 20220222 release?

Running Moode Audio now, but happy to test if this is the fix for the problems i encountered.

Please let me know...

20220222:
	- Add compatibility checks
	- Update kernel to 5.10.95
	- Update to buildroot 2021.11
	- Updated shairport-sync
	- audiocontrol2 websocket API by @schnabel
	- Bugfix: Set host name on MDNS when it changes
	- Bugfix: Shiaport-sync/nqptp

0

HiFiBerry team March 18, 2022 09:47

Yes, this has been included in the latest release.

Comment actions Permalink
0

Daansnijders62 March 18, 2022 17:22

Works like a charm. Thanks for the fix!

Comment actions Permalink
0

Richardpub March 18, 2022 17:42

for Pi3 B+, I only find this version hifiberryos-20211105-pi3.img
Are the 20220222 fixes only valid for Pi4??

Edited by Richardpub March 18, 2022 17:43

Comment actions Permalink

Please sign in to leave a comment.