As I click (tap) on the blue labelled “NDdac555” device in the above display, there is no response with this LITE version of Net Analyzer.
Suspect I may need to purchase the “Pro” version of the app.
agh probably not worth buying it just for this.
But if your streamer is supporting ipv6 which the app has confirmed, but you have no v6 addresses in the streamer network config screen - it does suggest your router is not working correctly - or has an interoperability issue with your streamer, or your ISP does not yet support v6.
If the router is not playing ball - then I suspect all your streamer has is a link local v6 address - these start FE80::0 /10 and allows other devices to talk ipv6 to it but ONLY within your home network.
S
well there you go then - you are all good and running ipv6 and ipv4. What I can’t see necessarily is whether your ISP support v6, because addresses starting FD are unique router assigned local / intranet addresses… so might be how your router is setup… your router might have an external internet ipv6 address if setup that way and that would start with 2
1 Like
Thankyou Simon, for your followups in this thread, appreciate your efforts.
Regards from “one of the colonies”.
2 Likes
I just checked and Tidal Connect is most definitely working even though Plusnet does not support ipv6 and I have disabled ipv6 in my router
Interesting… out of interest what does does your streamer network config screen show… I looked for the official Connect integration SDKs and they are only through NDA. So with your info it’s perhaps the unofficial repo on GitHub that is ipv6 only.
Such interesting thread. I am delighted. I don’t understand even 5%. I think in French it would be similar for me 
@Mike_S , I have a home work to do for you. Summarise the thread in 10 sentences.
1 Like
That’s a strange name for your streamer to be given, I would expect it normally to have the name ND5XS2-xxxxxx. Perhaps a sign that something odd is going on here?
Hi Chris, the device’s “hostname” is by default assigned a value of ND5XS2-xxxxxx where xxxxxx is the device serial number. This field is user customisable, it could set to “front-lounge” or “my-best-dog”, blank characters not permitted.
I decided mine to be representative for what it is ND5xs2/nDAC/PS555DR hence NDdac555.
This user customising is part of standard TCP/IP capabilities.
Understood - although the Naim streamers I have renamed were still identified by their original name when viewed in the Net Analyzer app.
I’m a muppet. While it is true that Plusnet don’t support ipv6 and I have turned it off for the WAN interface in my router settings, the LAN interface still has ipv6 enabled so devices on my LAN are getting an ipv6 address. That said, the streamer isn’t showing an IP address but a LAN scan is showing an ipv6 address for it!
Yes that is your link local (FE80) address that all ipv6 enabled hosts will generate for themselves. However your streamer is showing no routable ipv6 address or a link local address of the router/gateway, therefore it does appear that Tidal Connect is indeed working on only ipv4 contrary to the info I found on the web.
I don’t really want to upend my home network to demonstrate it one way or other with my streamer.
At the end of the day it is working for me apparently on ipv4 only so it just goes to show that you can’t believe everything you read on the Internet! Who knew?! 
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.