❓ [SAMBA NAS] not work via Zerotier

[LeONTheProfess]

Addon

SambaNAS

Your request

Hello, Installed the Samba NAS addon. I connect to the disk via the local network without problems, but for some reason the disk is not accessible via ZeroTier. May I connect via ZeroTier? What should I configure? Thanks!

Addon Config

workgroup: WORKGROUP
username: lom
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 169.254.0.0/16
  - fe80::/10
  - fc00::/7
  - 10.243.0.0/16
automount: true
moredisks:
  - id:ata-H_W_RAID1_IVVMS8ES2MKUJSPY3Y70-part1
available_disks_log: true
medialibrary:
  enable: true
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
compatibility_mode: false
wsdd2: false
mqtt_use_legacy_entities: false
autodiscovery: {}
other_users: []
acl: []
interfaces: []
password: "pwd"
log_level: warning

Addon logs

s6-rc: info: service base-addon-banner: starting

-----------------------------------------------------------
 Add-on: Samba NAS
 Expose Home Assistant disc with SMB/CIFS
-----------------------------------------------------------
 Add-on version: 10.0.2-nas4
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.1  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.10.5
 Home Assistant Supervisor: 2023.10.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to WARNING
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-automount: starting
---------------------------------------------------
Supported fs:   ext3    ext2    ext4    squashfs    vfat    msdos   f2fs    fuseblk ntfs3   exfat   btrfs   xfs
Supported fusefs: 
---------------------------------------------------
---------------------------------------------------
---------------------------------------------------
---------------------------------------------------
---------------------------------------------------
[13:52:54] WARNING: Your raid1 is ntfs. This is an EXPERIMENTAL support
s6-rc: info: service init-automount successfully started
s6-rc: info: service init-smartd: starting
s6-rc: info: service init-samba: starting
s6-rc: info: service hd-idle: starting
s6-rc: info: service hd-idle successfully started
smartctl 7.3 2022-02-28 r5338 [aarch64-linux-6.1.21-v8] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
SMART Attribute Autosave Enabled.
SMART Automatic Timers not supported

SMART Automatic Offline Testing Enabled every four hours.

s6-rc: info: service init-smartd successfully started
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
Added user lom.
---------------------------------------------------
---------------------------------------------------
s6-rc: info: service init-samba successfully started
s6-rc: info: service init-mqtt: starting
s6-rc: info: service wsdd: starting
s6-rc: info: service smbd: starting
s6-rc: info: service nmbd: starting
s6-rc: info: service avahi: starting
s6-rc: info: service smbd successfully started
s6-rc: info: service nmbd successfully started
s6-rc: info: service wsdd successfully started
s6-rc: info: service cifs-supervisor-mount: starting
s6-rc: info: service avahi successfully started
Waiting for daemon ...
s6-rc: info: service init-mqtt successfully started
Wait Samba Server to going up..(max 30s)
2023-10-29 13:53:03,553:wsdd INFO(pid 337): using pre-defined UUID cb6a33a0-b841-531d-a34e-09ecec492eb1
2023-10-29 13:53:03,561:wsdd INFO(pid 337): joined multicast group 239.255.255.250 on 192.168.100.48%wlan0
2023-10-29 13:53:03,567:wsdd INFO(pid 337): scheduling Hello message via wlan0 to 239.255.255.250%wlan0
2023-10-29 13:53:03,641:wsdd INFO(pid 337): joined multicast group [ff02::c] on fe80::7543:1a93:a99a:6533%wlan0
2023-10-29 13:53:03,645:wsdd INFO(pid 337): scheduling Hello message via wlan0 to ff02::c%wlan0
2023-10-29 13:53:03,682:wsdd INFO(pid 337): 192.168.100.74 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
2023-10-29 13:53:03,709:wsdd INFO(pid 337): fe80::9923:5865:a6c4:da4 - - "POST /cb6a33a0-b841-531d-a34e-09ecec492eb1 HTTP/1.1" 200 -
nmbd version 4.18.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd version 4.18.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
INFO: Profiling support unavailable in this build.
s6-rc: info: service cifs-supervisor-mount successfully started
s6-rc: info: service mqtt-disk-handler: starting
s6-rc: info: service mqtt-disk-handler successfully started
s6-rc: info: service mqtt-handler: starting
s6-rc: info: service mqtt-handler successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
*****

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.100.48

*****
*****

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 172.30.32.1

*****
2023-10-29 13:54:56,310:wsdd INFO(pid 337): [fe80::9923:5865:a6c4:da4]:56850(wlan0) - - "Resolve urn:uuid:2f9d3f7f-2aef-4906-b7cc-b43e0db28617 UDP" - -
2023-10-29 14:04:56,302:wsdd INFO(pid 337): [fe80::9923:5865:a6c4:da4]:64518(wlan0) - - "Resolve urn:uuid:d6fb4cf9-6c68-4074-b08e-bbfd9ba56937 UDP" - -
2023-10-29 14:14:56,310:wsdd INFO(pid 337): [fe80::9923:5865:a6c4:da4]:57770(wlan0) - - "Resolve urn:uuid:47d2a1ce-0002-4720-907e-c09ea570b12b UDP" - -

[dianlight]

I don't have a zerotier configuration to test but I suppose you need to add the interface in the addon configuration. From your log I see that your primary interface is wlan0 so add both ( wlan0 and zt0?)in manual configuration. I suppose zt0 is the name for zerotier in your configuration adjust if not.

L

[Johnynekk]

@LeONTheProfess Hi, do you figure it out? I have same problem. Thank you.

[dianlight]

In the beta channel the version (12.2.0-nas2.beta69) has a new option bind_all_interfaces that allow pseudo-eth device like TailScale to work. Please try with Zerotier

L