SOLVED SMB mDNS Service Discovery Broken / macOS Ventura Can No Longer See TrueNAS

[simdim]

SO my predicament:
Since I can not have 2 bridges on the same subnet and no VMs on on NIC1/Br0 I am not putting IP on Br0

NIC1 - 192.168.1.10/24 SMP/mDNS/WebGUI
Br0 - No IP
NIC2 - No IP
Br1 - 192.168.1.20/24 VM/APPS

But this setup brakes VM networking. The only reason I keep VMs on this rig is to run HomeBridge and Scripted that are not cooperating in APPs mode.
Reverted back to no BR0 .. will have to discover NAS as address and not name - I can survive :)

 

[Patrick M. Hausen]

Again: you cannot have addresses from the same subnet on two different network interfaces. This is a fundamental property of IP and routing.

See: https://www.truenas.com/community/resources/multiple-network-interfaces-on-a-single-subnet.45/

 

[simdim]

Sorry for all back and forth ...

Working solution

NIC1 - No IP
Br0 - 192.168.1.10/24 SMP/mDNS/WebGUI
NIC2 - No IP VM/APPS
Br1 - No IP

Just like what smart people had said - you want mDNS - have box IP on the bridge.

 

[Patrick M. Hausen]

This is wrong and going to bite you in the future. You cannot have two interfaces with addresses from the same subnet. Period. But you do you - I'm out.

 

[simdim]

This is wrong and going to bite you in the future. You cannot have two interfaces with addresses from the same subnet. Period. But you do you - I'm out.

Sorry hit post too fast - there is only one IP on the box (edited the post)

 

[Rob Granger]

I went years without having the issue, then 13 it started again. I can use a Bonjoure browswe and the _adisk._tcp will stop responding. Easy to verify with the "add new disk" option under TimeMachine. Results of pre-post of restarting are attached.
Lucky for me the Truenas that hosts my TM backups does not have any SMB shares other than the TM destinations so I can restart SMB.
The adis._tcp (0) is when SMB is not responding, as is "No Available Time Machine Destinations."

I reported the error years ago, is there a better work around?
Rob

 

[Rob Granger]

Found the issue. I had the same share on NFS and SMB. I did this so that I could browse backups from proxmox mounted to NFS on my mac. I disabled the share from SMB and the timemachine info started being browsable again.
dns-sd -L truenas _adisk._tcp Lookup truenas._adisk._tcp.local DATE: ---Tue 14 Nov 2023--- 17:01:14.304 ...STARTING... 17:11:08.942 truenas._adisk._tcp.local. can be reached at truenas.local.:9 (interface 6) sys=waMa=0,adVF=0x100 dk0=adVN=TM-BIGMAC,adVF=0x82,adVU=40d9fb4c-8d5d-4266-ab5e-8de7bba9f556 dk1=adVN=TM-MACJACK,adVF=0x82,adVU=88797048-06b8-402a-81a9-733175af1ff8 dk2=adVN=TM-MACMAC,adVF=0x82,adVU=5ff4521d-2b4e-4997-a694-cce2d88126e9 dk3=adVN=TM-RMP1,adVF=0x82,adVU=2e7f75bd-27d8-4c94-b566-c10a5a198031 dk4=adVN=TM-BIGGERMAC,adVF=0x82,adVU=ad75f3df-706c-47fa-b526-429cf877bf14 dk5=adVN=TM-RMP2,adVF=0x82,adVU=b3091b98-e215-48a4-9e8c-8e465c0db4c0 17:11:09.006 truenas._adisk._tcp.local. can be reached at truenas.local.:9 (interface 8) Flags: 1 sys=waMa=0,adVF=0x100 dk0=adVN=TM-BIGMAC,adVF=0x82,adVU=40d9fb4c-8d5d-4266-ab5e-8de7bba9f556 dk1=adVN=TM-MACJACK,adVF=0x82,adVU=88797048-06b8-402a-81a9-733175af1ff8 dk2=adVN=TM-MACMAC,adVF=0x82,adVU=5ff4521d-2b4e-4997-a694-cce2d88126e9 dk3=adVN=TM-RMP1,adVF=0x82,adVU=2e7f75bd-27d8-4c94-b566-c10a5a198031 dk4=adVN=TM-BIGGERMAC,adVF=0x82,adVU=ad75f3df-706c-47fa-b526-429cf877bf14 dk5=adVN=TM-RMP2,adVF=0x82,adVU=b3091b98-e215-48a4-9e8c-8e465c0db4c0 17:11:09.006 truenas._adisk._tcp.local. can be reached at truenas.local.:9 (interface 8) sys=waMa=0,adVF=0x100 dk0=adVN=TM-BIGMAC,adVF=0x82,adVU=40d9fb4c-8d5d-4266-ab5e-8de7bba9f556 dk1=adVN=TM-MACJACK,adVF=0x82,adVU=88797048-06b8-402a-81a9-733175af1ff8 dk2=adVN=TM-MACMAC,adVF=0x82,adVU=5ff4521d-2b4e-4997-a694-cce2d88126e9 dk3=adVN=TM-RMP1,adVF=0x82,adVU=2e7f75bd-27d8-4c94-b566-c10a5a198031 dk4=adVN=TM-BIGGERMAC,adVF=0x82,adVU=ad75f3df-706c-47fa-b526-429cf877bf14 dk5=adVN=TM-RMP2,adVF=0x82,adVU=b3091b98-e215-48a4-9e8c-8e465c0db4c0

 

[tylermilner]

I'm having the same issue here where mDNS eventually craps out causing Time Machine to stop seeing my backup disk and my Macs going without being backed up until I notice. Most recently, this happened after less than 3 days of uptime on the NAS. I'm using a pretty basic setup on TrueNAS-SCALE-23.10.1 with just a couple of SMB shares for Time Machine backups for 2 MacBooks. I am not running any VMs, containers, or extra services, so no "bridging" or any other complex setup like some of the other posters here.

When the issue happens, I am still able to browse and connect to the shares via the "Network" tab in Finder, although the name shows as "truenas-3" instead of just "truenas". However, I am not able to connect to the web interface in my browser at

https://truenas.local

like I normally am and instead must connect by typing out the IP address

https://192.168.1.xx

. In an effort to get things working again, I tried turning off SMB and then turning it back on, but that didn't help anything.

So far, the only fix I've found is to reboot the NAS when I notice that Time Machine backups aren't working. However, based on an idea in this post, I found another workaround to get things working again without a reboot. I went to Network --> Global Configuration --> Settings and then unchecked "mDNS" under "Service Announcement" and clicked "Save". I got an error about being unable to disable mDNS because it's required for Time Machine. I then re-checked the "mDNS" box and then clicked "Save" again which seems to have restarted mDNS and fixed things. Immediately, I was able to see the entry for my NAS show as "truenas" instead of "truenas-3" in my Mac's Finder window and I was also able to connect to the web interface again without issue at

https://truenas.local

instead of typing the IP address. In my Mac's Time Machine app, clicking "Back Up Now" was also able to find the back up disk and resume backing up no problem.

TL;DR: This mDNS problem still seems to be a general issue with TrueNAS-SCALE-23.10.1 and not necessarily related to VM network configuration. Disabling and re-enabling mDNS under Network --> Global Configuration --> Settings seems to get things working again, but it would be nice not to have to babysit TrueNAS to make sure my Time Machine backups are working.

 

[Rob Granger]

Add a cron task to restart the service every 5 minutes, it is what I did. It won't affect running jobs.

/usr/sbin/service avahi-daemon restart

 

[Rob Granger]

I setup a cron job and run /usr/sbin/service avahi-daemon restart every five minutes, not a fix but seems to help.