bonienl

Community Developer
 View Profile  See their activity

  • Posts

    10233

  • Joined

  • Last visited

  • Days Won

    65

 Content Type 

Report Comments posted by bonienl

    Unraid OS version 6.12.0-rc8 available

    in Prereleases

    Posted

    Name resolution on your PC is outside the scope of Unraid.

    You need to make sure correct name resolving to ipv4 and/or ipv6 is done in your network.

     

    I created a new name for my server, which resolves to an ipv6 address.

     

    image.png

     

      

    > ping flora6

Pinging flora6 [2a02:a448:32d5:101:xxxx:xxxx:xxxx:xxxx] with 32 bytes of data:
Reply from 2a02:a448:32d5:101:xxxx:xxxx:xxxx:xxxx: time<1ms
Reply from 2a02:a448:32d5:101:xxxx:xxxx:xxxx:xxxx: time<1ms
Reply from 2a02:a448:32d5:101:xxxx:xxxx:xxxx:xxxx: time<1ms
Reply from 2a02:a448:32d5:101:xxxx:xxxx:xxxx:xxxx: time<1ms

Ping statistics for 2a02:a448:32d5:101:xxxx:xxxx:xxxx:xxxx:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

     

    Note: netbios does not support ipv6.

     

    Upgrade from 6.12.0-rc5 to rc8 - Samba No Longer Works

    in Prereleases

    Posted

    24 minutes ago, shpitz461 said:

    Why did it work in rc5 but now no longer works? was there a syntax change?

     

    The latest Unraid versions limit the listening interfaces for samba. This is an automated process and should not be overridden.

    With those lines included you were telling samba only to listen to those two interfaces and not the main interface.

    The speed values are only used as indication, the true link speed of the interface is never changed.

     

    • Thanks 1

    Unraid OS version 6.12.0-rc7 available

    in Prereleases

    Posted

    33 minutes ago, baujahr said:

    Thanks for the update, please kindly look into this as I access the server remotely via a Tailscale tunnel.

     

    GUI and SSH are reachable over tailscale

    Are you using samba over tailscale?

     

    I did a quick test on Unraid 6.11.5 and here also samba is not working over a wireguard/tailscale tunnel, which is expected because these tunnels do not support broadcast.

     

     

    Unraid OS version 6.12.0-rc7 available

    in Prereleases

    Posted

    53 minutes ago, bonienl said:

    SMB try to restart the array and see if that make a difference (be sure to have the additional code in the 'go' file).

     

    I did some more reading on samba, it requires an interface with supports broadcast.

    WireGuard / Tailscale define their interface as a host address (/32) which does not support broadcast.

    Hence samba is not listening to such an interface eventhough it is given in the list of permitted interfaces.

     

    Unraid OS version 6.12.0-rc7 available

    in Prereleases

    Posted

    20 minutes ago, baujahr said:

    Thanks for including the option to add custom listening interfaces, I've added the tailscale0 network and access via the web works fine.

    However I am not able to access the server via SMB and SSH, is this still a limitation or am I forgetting something?

     

    All services follow the same conditions.

     

    SSH works fine for me. Make sure you use the tailscale tunnel 

    Jun 6 21:01:54 flora sshd[23009]: Connection from 100.86.214.68 port 59214 on 100.89.107.81 port 22 rdomain ""

     

    SMB try to restart the array and see if that make a difference (be sure to have the additional code in the 'go' file).

     

    Unraid OS version 6.12.0-rc7 available

    in Prereleases

    Posted

    HOW TO SETUP TAILSCALE OR ZEROTIER COMMUNICATION

     

    • Install the Tailscale or Zerotier docker container as usual and start the container
    • It is recommended to have this container autostart as the first container in the list

     

    image.png

     

    • Go to Settings -> Network Settings -> Interface Extra
    • This is a new section which allows the user to define which interfaces are used by the Unraid services. By default all regular interfaces with an IP address are included in the list of listening interfaces
    • The tunnels of the built-in WireGuard function of Unraid are automatically added or removed from the list when the Wireguard tunnels are activated or deactivated. The user may exclude these tunnels from the list of listening interfaces
    • To use the Tailscale or Zerotier interface, it is required to add the interface name or IP address of the communication to the list of included listening interfaces. It is imperative that Tailscale or Zerotier container is running before the interface is added to the list.

     

    image.png

     

    • A check is done if a valid name or IP address is entered and the new entry is added to the list of current listening interfaces. At this point, services are restarted to make them listen to the new interface as well

     

    image.png

     

    • When the new listening interface is active, it is possible to use it. For example it allows Tailscale to enter the GUI on its designated IP address

     

    image.png

     

    Included and Excluded listening interfaces need to be reactivated each time the server reboots or the array is restarted.

    To automate this process, you can add the following code in the "go" file (place it before starting the emhttpd daemon)

      

    # reload services after starting docker with 20 seconds grace period to allow starting up containers
event=/usr/local/emhttp/webGui/event/docker_started
mkdir -p $event
cat <<- 'EOF' >$event/reload_services
#!/bin/bash
echo 'sleep 20;/usr/local/emhttp/webGui/scripts/reload_services' | at -M now 2>/dev/null
EOF
chmod +x $event/reload_services

     

    With this code in place and autostart of containers is enabled, it will ensure the listening interfaces are automatically updated after a system reboot or array restart.

     

    • Like 2