bonienl

Yes, in combination with additional routing rules on your router (defines the return path)

Dockers with a custom network (unique IP address) have the router as gateway. It requires additional routing on the gateway itself to make containers reachable over VPN.

Solved in RC2

If your DNS server is another machine as your Unraid server, it needs a route back to your mobile over the VPN tunnel. In other words your mobile gets to your local DNS server over the VPN tunnel, but the DNS server doesn't know the way back.

yes, to be more precise the IP address of the tunnel endpoint at the client (peer) side.

The WireGuard function has no knowledge at all about DNS settings of the peer(s). Consequently these are left out of the peer configuration, but can be manually added on the peer (phone, laptop, etc) once the configuration is loaded. At the server side the DNS entries of the server itself are taken.

This is fixed

Fixed

Do you use IPv6? If not, change network settings to IPv4 only.

With the release of Unraid 6.8 comes support for WireGuard VPN connections. At the moment the GUI part is offered as a separate plugin, but will be integrated into Unraid in the future. This approach allows for quick updates and enhancements without dependency on Unraid version releases. People starting with WireGuard should read the quick-start guide written by @ljm42. See Please use his topic only to ask questions about using and setting up WireGuard. The GUI has online help as well, please have a look at this too. Use this topic to report any issues or bugs or proposed enhancements for the WireGuard functionality. This way things stay grouped together. Thanks

Stock Unraid does not download anything, regardless license.

On the Main page click on the disk icon of a device and it shows the associated log with the disk.

haha, not as undocumented as I thought 😄

but still undocumented 😉

The usage of the "stop" file is as undocumented as the usage of the folder "/extra" ...

Redo your parity schedule settings, so they get updated and corrected.

All the Dynamix plugins are "best effort" due to my busy schedule and other commitments. S3-sleep is difficult to test, because I don't have all the different hardware that exists out there. Recently, I did make a new test server with AMD though, just to see how things work.

Today, there is active development

I made a typo instead of "-a" (add) you should use "-u" (update)

Regular management of Unraid is done from the GUI, and CLI access is more of an exception. The same is true for manually editing config files. At this level we are talking "regular" linux commands and utilities. Documentation about these can be found online, and are not specific to Unraid. The GUI allows creation of shares, which become accessible for each remote system. When a share is given the security level "private", it will force remote systems to access such a share with a valid username and password. Associated with the username are the access rights, and for private share there are 3 options: no access, read only or read-write. All controlled from the GUI. Not sure what you mean with "they are visible to each other". Any system which has SMB enabled will become visible on the local network, regardless of Unraid. Unraid does not take part in any communication between remote systems themselves. When permissions are not set correctly (maybe due to copying from different sources/users/applications), you can run "New Permissions" -- see Tools -- to restore each share to the correct permissions.

Please explain what you try to accomplish. The specific user information is stored in a different files, and the smb extra file is primary used to set specific SMB settings, which are documented by Samba, see https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html Keep in mind that "Unraid users" is not the same as traditional "linux users". Within Unraid regular users have no access to the system itself, but are created to give access to shares. Within the GUI you can define the access rights of each user and specific share.

Creating users and assigning/maintaining associated rights is all done in the GUI. There is no need to do this by manually editing the smb config file.

You can run the CLI command (this updates the files in the specific folder) /usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker -b2 -a "/mnt/disk5/iTunes/Music/Wolfgang Haffner/Kind of Cool"

It shouldn't be possible to "break out" of a container and as far as I know this isn't possible. Otherwise it will be a security vulnerability of Docker itself.

Ok, but is there somewhere a "proof of concept" to confirm the claim?