Community Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by bonienl

  1. Sorry, I was off for a while. WireGuard isn't bound to an interface, instead it uses routing to determine how to set up the tunnel. Normally the end-point is reached by Unraid via the default gateway, which is reachable by interface eth0 (it holds the default route). If you want a WireGuard tunnel to run over a different interface, you need to make sure the routing on Unraid to reach the end-point of this tunnel points to the interface you want to use. It is already possible to define different tunnels and let them run via different interfaces, b
  2. In your setup above, the VLANs are assigned to a port, which means your Unraid has only presence in VLAN 1 and can access other devices directly which reside in VLAN 1 too (your left switch). For Unraid to access the devices in VLAN 3 it has to go via the router, and it does NOT need any VLAN configuration on the server itself In this scenario all devices both in VLAN 1 and VLAN 3 must use the router as their default gateway to make connectivity possible. The switches themselves do not require any configuration (in other words use unmanaged switches), your router keeps th
  3. This is normal after rebooting the server, time will get synchronized after a while (assuming you have NTP configured).
  4. WireGuard access is available independent of the array running or not. This gives it a distinct advantage over docker or vm based solutions.
  5. Perhaps it is controller specific related? I use an Adaptec HBA 1100 series controller and parity check speeds are as before.
  6. This is expected behavior when the GUI is displayed in non-tabbed mode. While in tabbed mode (see display settings) it will select the appropriate tab. This behavior hasn't changed since this feature was introduced, I can't remember exactly when but it is a long time ago.
  7. That fully depends on the device where you are installing WireGuard. When I use my iPad pro, it requires a fingerprint authentication first before installing the WireGuard tunnel.
  8. I've made the correction and moved the ruleset definition before the include. Note To make this work, the user has to delete the files /config/rsyslog.conf and /config/rsyslog.cfg from the USB device. Reboot the server and reconfigure the syslog service in the GUI again.
  9. It is correct that smart-one.cfg is not created when individual disk utilization levels are adjusted. Starting from 6.9 these levels are now stored in disk.cfg. Other variables, such as temperature levels, are still stored in smart-one.cfg. I made an update to the (background) monitoring script to prevent false positives. In my testing this all looks okay.
  10. With so many peers failing at the same time, I would first check the router. Is port forwarding still correct on the router. Perhaps your Unraid server got a different IP address which breaks forwarding. Perhaps your router is using UPnP and lost the forwarding entries?
  11. Gigabit ethernet connections don't use crossover cables.
  12. Everything is still working for me. As a test I also recreated the configs and uploaded to my peers, all fine and working. Version 2021.04.12 corrects language translation support, not directly related to WireGuard itself. Switch to advanced mode and use the PING button to test reachability to the peer (in my example I have both IPv4 and IPv6, but same principle with IPv4 only)
  13. Il faut avoir tous les fichiers au format Linux (LF). Les traductions manquent lorsque le format Windows (CRLF) est utilisé.
  14. I have the Supermicro X10SRA-F motherboard too, rock solid and zero issues. Make sure you use the latest BMC and BIOS versions.
  15. Tu peux tester sur n'importe quelle version 6.9 d'Unraid
  16. A possible solution is to run docker containers on a custom network (br0), this will give them a unique IP address and restrict access.
  17. You better open a new topic under General Support. Usually this is the result of some incompatibility of your system with regards to USB2/USB3 and/or UEFI/legacy. In addition, makes sure you run the latest BIOS version of your motherboard
  18. It is allowed to interrupt a running check and reboot, no harm done. If it is wise to do, is another question
  19. smart-one.cfg should be created as soon as you make a change for an individual disk. In the new format smart-one.cfg should have the disk identifier as the section header. E.g [KINGSTON_SA2000M81000G_50026B7683B40AB5] hotTemp="50" maxTemp="60" This is working fine for me on 6.9.2 (only outstanding issue is when the identifier has a 'dot' in the name)
  20. There are not many other ports open on Unraid, it is not a fully fledged server with many different services to run. On the management access page you can further tell what management services to open or close. Services like http/https, ssh and telnet are all protected by a login authentication.
  21. The WireGuard solution is intended to give only "trusted" users access, any "outsiders" can't make access because they don't have the WG keys to establish the session. Who is accessing your Unraid server over WireGuard? It sounds like you are setting up some "public" service. Any device on your LAN which runs on its own unique IP address (this may include docker containers and VMs) can be allowed or denied access over WG (configurable in the GUI).