February 16, 20233 yr The SysLog shows Feb 15 11:25:03 Tower avahi-daemon[326]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Feb 15 11:25:03 Tower avahi-daemon[326]: *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** I can see that there are two (at least) mDNS groups 192.168.1.. (that I would expect) and 192.168.122.. that I have no knowledge of I do seem to be getting random network disconnections (user share disconnections) - which might be related to network resets??? I'm running a number of Dockers and one VM (Hoobs) I set the VM on 192.168.1.82 I've downloaded (anonymised) diagnostic files - should upload all or selective ones? browsing ifconfig I can see virbr0: inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 I can see IPv4 192.168.122.0/24 virbr01 in the network routing table I'd like some advice please? I guess I could delete ..122.. from the routing table - but would this be wise? are there any other areas I should investigate or diagnostics I should run
March 21, 20233 yr Same issue here.. Random disconnects from the network. Rebooting is the only thing that brings the server back online. Not sure if this is the cause or not. It's about the only thing I am seeing in syslog. Then it may last for 6-12 hours then disconnect again. Edited March 21, 20233 yr by Dro
March 21, 20233 yr Author I deleted the "duplicate mDNS" - there might have been a marginal, but not material improvement. I ended up purchasing an app "auto mounter" from the App store - it works... (I understand there are alternatives)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.