Bonjour

Just checked mine out I'm seeing the same issue too.

It can't be Bonjour as safari on a Mac can be set to list Bonjour / mDNS devices as book marks, it shows   mu-so.local/1000/index.html as a bookmark, thats the main page for configuring the mu-so.

Also my iDevices can be set to stream audio to the mu-so, that's also done by Bonjour/mDNS.

Looks fine from my router too :-

[2.3.4-RELEASE][admin@pfsense]/root: avahi-browse -a | grep mu-so
+ igb0_vlan4 IPv4 mu-so _http._tcp local
+ igb0_vlan2 IPv4 mu-so _http._tcp local
+ igb0_vlan4 IPv4 3010B3F43F90@mu-so _raop._tcp local
+ igb0_vlan2 IPv4 3010B3F43F90@mu-so _raop._tcp local
+ igb0_vlan4 IPv4 mu-so _airplay._tcp local
+ igb0_vlan2 IPv4 mu-so _airplay._tcp local
+ igb0_vlan4 IPv4 mu-so _spotify-connect._tcp local
+ igb0_vlan2 IPv4 mu-so _spotify-connect._tcp local

Can you run your network diagnostics and verify if all your devices, especially the router (assigning the IP addresses) 'bonjour' to each other?

I can ping the mu-so from the iDevice & router. it's not a connectivity issue at the ip level.

Bonjour is multicast DNS as I said I can see the device via bonjour / mdns.

https://en.m.wikipedia.org/wiki/Multicast_DNS

Nogbad The Bad posted:

I can ping the mu-so from the iDevice & router. it's not a connectivity issue at the ip level.

Bonjour is multicast DNS as I said I can see the device via bonjour / mdns.

https://en.m.wikipedia.org/wiki/Multicast_DNS

 

And how exactly does that help the OP?

I have the same issue as the OP.

Check the first line of my first post and maybe the last line from the OP !

Nogbad The Bad posted:

I have the same issue as the OP.

Check the first line of my first post and maybe the last line from the OP !

I read that. But your answers clerly did not help the OP resolve his issue - you have just listed your problem and sent a reference to some theory, which obviosly did not help either. 

My question was to Jon Myles - is there any way you could run your network diagnostics with say Net Analyzer and post the result? 

It would also be helpful if you let us know which streamer are you updating and the basic setup of your netork? Can you get the following to work reliably on your network: stream, iRadio, NAS playback, Tidal etc?

Can he play music from his iDevice ( if he has one ) via AirPlay if he can its not a bonjour / mDNS issue as AirPlay uses bonjour to announce to the network, "I have these services you can use" via multicast. 

That test is insufficient without knowing the network topology - just because it's multicast doesn't mean that it actually reaches every endpoint on the network.

If he's trying to do the update via his iDevice it should be enough shouldn't it, otherwise he wouldn't see the mu-so as an AirPlay device.

I've emailed support and sent them a few network captures.

I've set up my iPad on ethernet ( yes it can be done but its a bit of a kludge ) and set up port mirroring, I can see Bonjour / mDNS packets being sent back to the iPad via Wireshark.

Jon can you ping the update server from your network ?

softwareupdate.naimaudio.com

Hi Guys,

I've had this reported by another customer too so I've logged his report and this forum thread with our software guys to look into - I don't think it's a Bonjour issue as Bonjour shouldn't be being used during the test for new firmware (I suspect that the error message itself is incorrect). Normally this has been down to the update server URL (softwareupdate.naimaudio.com) not being resolvable from the customers location but this doesn't seem to have been the case with the customer that I've been in contact with this morning.

Best

Phil

I wonder if the error message should read "No update available"

Nogbad The Bad posted:

I wonder if the error message should read "No update available"

No - There is a message of "No update available" which is normally reported if the device checks and finds that there is no update available ... this is being reported because for some reason the device isn't getting out to the update server.

Best

Phil

I had this this afternoon and restarted the router and UQ2 which sorted it.

Just seen this... looks like more  consumer router / consumer wifi issues. mDNS can use a multicast address (224.0.0.251) just like SSDP  (239.255.255.250) as used in UPnP. Multicast addresses are susceptible to errant IGMP snooping features on consumer routers, consumer wifi access points and other devices.. as always try and disable IGMP snooping - or put everything through a standalone basic non managed switch  and use a new separate wifi access point such an Apple Airport Express or better plugged into that switch. Switching the router switch off and on should also reset the issue  - for a while... 

I'm on holiday at the moment with my Qb and my Core. They are plugged into a BT hub4 in the rental cottage (with an unfortunate lack of a GS105 switch, but there are limits to what one  can bring on holiday without seeming geeky!).

Today I had an odd thing that my iPad could see the Core but not the Qb, although my iPhone could see both and the Qb could see the Core and play music from it with Upnp. Restarting the iPad and the app made no difference. I was quite frustrated and thought of suggesting to Naim a new feature, which would be a "Go on, look harder!" button for the rooms screen on the app!

Eventually I unplugged the network cable from the Qb, waited until the buffer was empty (so the music stopped) and then plugged it in again. 5 secs later the Qb was now visible from my iPad again.

This action presumably made the Qb ask for a lease again on being reconnected and whatever (possibly bonjour-related?) thing that had happened got sorted.  i haven't had to touch the Qb at home in six months, but two days here and it gets lost.

I reckon much of the pain on this part of the forum is down to poorly designed, incorrectly setup, or faulty routers. Restarting the router should be one of the first things people should try when they run into a connectivity problem, although unplugging and replugging a network cable can sometimes achieve similar results and is quicker.

best

David

I had a blank unresponsive app this afternoon and a "Bonjour message. I deleted and then downloaded and reinstalled the app to fix.

Jon Myles posted:

Sorry if this has been answered previously but I have searched to no avail. The message I get is: "Firmware update details not available as Bonjour discovery is not working. Please check your network."

There is no problem with the network. Nor with Bonjour. So where next?

Hi Jon,

If you have "Net Analyzer" (not the lite version) on your iOS device can you see if your unit shows up with a Bonjour flag when you do a network scan from your iOS device in Net Analyzer?

Thanks

Phil