bonienl

When you use the profile "Remote access to server", then all traffic will follow the normal route as before. Make sure the peer (your sister) uses the correct configuration which is generated with this profile.

Select "Remote access to server" as profile. At the peer side, it is possible to access (only) the Unraid server by its wireguard address 10.253.0.1

A wireguard tunnel terminates on your Unraid server, you can not deny peer access to your server, unless you use a different device (router) to terminate the WG tunnel. The WG configuration has a limited firewall function to allow or deny access to other devices in your network. A simple solution would be to define your local network, e.g. 192.168.1.0/24 and deny access.

My take on this. Wifi support in Linux is limited, the main reason is drivers are not free. It will be hit and miss with your hardware. Unraid is based on slackware, which has virtually no wifi implementation. The network stack of Unraid is heavily modified to support a lot more networking than slackware offers. Wifi support requires additional development, which isn't a light job (not to mention hardware purchases to do so). Wifi is a support nightmare. Speaking from own experience I can tell that most connection problems are caused by wifi. It is questionable whether the additional support burden is worth it. The easy solution I have done, is the installation of an AP set as client. APs come in all sorts of shapes and sizes. It is a matter of finding the right one for the job. An advantage with a separate AP is its placement. Instead of a server somewhere tucked away in a corner, the AP can be placed anywhere in the room for best reception.

Times are set in the code and can’t be changed in the GUI. You can make a feature request though.

Are you perhaps using a spin down time of 2 hours? See Settings -> Disk Settings -> Default spin down delay

The official website is not really conclusive about this. It doesn't say what counts exactly as storage device. When you go to Tools -> Registration, it will tell how many attached storage devices Unraid counts for.

For Unraid 6.9.0-beta23 I have added a truncation of the version identifier to prevent too long strings.

To keep folders cached by Linux, it requires periodic updates, read: full scans of those folders every so many seconds. When you have cached folders with many levels and/or files, it will make your system more busy and of course consumes your RAM memory.

This is corrected in Unraid 6.9.0-beta23

Start your system in safe mode and undo the ACS override setting.

WireGuard is a stateless protocol, it doesn't maintain a connected or disconnected state, and hence can't keep time. The "best" it can do is to show how long ago the last exchange took place (handshake).

Please update to today's version.

Yes, several plugins have the same bug. I have made an update for all affected plugins. Please update.

You found a bug, I need to correct that.

The date format is selected under Settings -> Display Settings -> Date format

Host access is not needed for Pi-hole. It is recommended to set regular DNS servers for Unraid itself, because Pi-hole will interfere with the operation of Unraid. When host access is enabled and shim networks are used, your pfSense box will see the same IP address twice and gets confused.

Very unlikely. The MAC address of your Unraid systeem is tight to the NIC and doesn't change. Seems more a configuration issue on pfsense, it receives a different MAC address associated with the IP address as configured.

The WireGuard implementation itself is always loaded as part of the system kernel. The plugin is for the GUI front-end and configuration part only. Removing the plugin will not remove any already existing WireGuard configurations. In a future version of Unraid, this plugin will be integrated. The reason we started with the plugin was to make the development of WireGuard support independent of the Unraid releases, but we are getting to a point where integration can be done (not yet in Unraid 6.9 though). WireGuard configuration should have no effect on local connections, i.e. connecting from your LAN network. The WireGuard configuration files are stored on the flash device in the folder /config/wireguard. Deleting this folder and rebooting the system is like starting without WireGuard.

Re-apply both the global and per disk settings, and check if that makes a difference.

Have you tried different settings of "Device activity monitoring"? Status check is a hardware check, but may not work with all disk types. Counters check is a software check, and can be used as alternative

Not really, my eye felt on the IPv6 question by pure accident.

IPv6 support is only available for custom (macvlan) networks. This is configured under the Docker settings. Host and bridge networks have IPv4 only.

As long as you keep the WG tunnel in active state on the Unraid server, it is not really disconnected. This is also the reason why the time is incremented, because it will tell exactly when the last exchange has occurred.