Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


ljm42 last won the day on September 2 2019

ljm42 had the most liked content!

Community Reputation

206 Very Good


About ljm42


  • Gender
  • Personal Text
    the answer to life, the universe, and everything

Recent Profile Visitors

4880 profile views
  1. The issue is DNS. When you use a browser to visit https://yourhash.unraid.net, your computer does a DNS lookup to translate the hostname into an IP address, something like But if your Internet is down and the DNS lookup fails, the browser won't be able to get the IP address for that hostname. I don't use pihole myself, but I imagine it has a way that you can hard-code an IP address for a given hostname so that it will respond correctly even if your Internet is down. Google should be able to help with that. Another option would be to modify the hosts file on your computer (not Unraid, the computer with the browser on it) so it will resolve yourhash.unraid.net to the correct local IP address. Google can help with that too. Just keep in mind if your Unraid's IP address ever changes you'll need to go back and update whatever you hard-coded.
  2. The reason for "adding a tick" to a device is to ensure Unraid doesn't install any drivers for it, thus leaving the device available to be passed through to a VM. I'd guess that Unraid doesn't load audio drivers right now so it isn't strictly necessary to bind the audio device to vfio-pci. But I'd probably add the tick anyhow, in case something changes in the future.
  3. We need more details. I'm not really clear how you are getting an invalid cert error, unless you are going to https://<ip address> What happens if you go to: http://<ip address> NOTE: it must be http, not https. There is no certificate for the ip address.
  4. The dashboard is simply formatting the output of the "wg show" command provided by WireGuard. wg does not provide a counter of "how long" a device was connected, probably because it is designed to let connections seamlessly drop and reconnect. It does show the amount of data that was transferred though. I guess WireGuard feels the length of time somebody was connected is less important than the amount of data they transferred.
  5. I'm looking into this. To clarify, what browser on what device are you using when you do this? From my testing, it appears to be a browser issue. When I use press the Apply button using Chrome on Android, the tunnel stops but does not start back up. If I use Chrome on Windows it works fine. In either case, it does not matter whether I am connected via WireGuard or direct via wifi. Can you confirm that you see the same?
  6. Realtek came up in another thread today too: In general, you're better off avoiding Realtek in Unraid. The may work OK in Windows, but their Linux drivers are hit and miss. They will work in one version and then have problems after an upgrade.
  7. "Active" simply means the tunnel is enabled on the Unraid side, has nothing to do with whether someone is currently connected to it. The "handshake" column shows that "Peer 1" last connected to tunnel WG0 7 minutes and 23 seconds ago. If you no longer want the tunnel to be available for connections, go to Settings -> VPN Manager and change the "Active" slider for tunnel WG0 to "Inactive". If you want to "forget" the fact that "Peer 1" connected 7 minutes and 23 seconds ago but still keep the tunnel up, change the slider from Active to Inactivate and then back to Active. That will clear the connection list.
  8. "Unassigned Devices" is both a generic term that means "disk not assigned to the Unraid array" and the name of a plugin which adds capabilities to disks not assigned to the array.
  9. Here is a guide that describes the new System Devices page and how you can use it to bind devices to vfio-pci:
  10. At times you will want to "hide" devices from Unraid so that they can be passed through to a VM. Unraid Prior to 6.7 In the past (pre Unraid 6.7) we would stub the device by adding a Vendor:Device code to the vfio-pci.ids parameter in Syslinux, something like this: append vfio-pci.ids=8086:1533 This worked, but had several downsides: If you have multiple devices with the same Vendor:Device code, all of them would be stubbed (hidden) from Unraid It is a fairly technical process to find the right Vendor:Device code and modify the syslinux file. Make a mistake and your system won't boot! As an alternative, you could add the <Domain:Bus:Device.Function> string to the xen-pciback.hide parameter in Syslinux: append xen-pciback.hide=0000:03:00.0 This had downsides too: Still a technical / risky process If you add/remove hardware after modifying syslinux, the pci address could change and the wrong device could end up being stubbed. This would cause problems if a critical disk controller or NIC were suddenly hidden from Unraid This broke in Unraid 6.7. More details Unraid 6.7 Starting with Unraid 6.7 we could bind devices to the vfio-pci driver based on the <Domain:Bus:Device.Function> string (aka pci address). You needed to manually modify the config/vfio-pci.cfg file and specify the <Domain:Bus:Device.Function> string, like this: BIND=03:00.0 This worked, but still had several downsides: It was a fairly technical process to find the right string to place in the file. But at least if anything went wrong you could simply delete the config file off the flash drive and reboot. We still had the problem where if you add/remove hardware after modifying the file, the pci addresses could change and the wrong device could end up being bound to vfio-pci Unraid 6.9 For Unraid 6.9, Skittals has incorporated the excellent "VFIO-PCI Config" plugin directly into the Unraid webgui. So now from the Tools -> System Devices page you can easily see all of your hardware and which IOMMU groups they are in. Rather than editing the config file by hand, simply add a checkbox next to the devices that you want to bind to vfio-pci (aka hide from Unraid). If a device is being used by Unraid (such as a USB controller, disk controller, etc) then the web interface will prevent you from selecting it. Additionally, we have a new version of the underlying vfio-pci script which can prevent the wrong devices from being bound when hardware is added or removed. When you click to bind a device on the System Devices page, it will write both the <Domain:Bus:Device.Function> and the <Vendor:Device> code to the config file, like this: BIND=0000:03:00.0|8086:1533 In this example, the updated script will bind the device at pci address 0000:03:00.0, but only if the <Vendor:Device> code is 8086:1533. If a different <Vendor:Device> code is found at that address, it will not bind. This means we will never inadvertently bind a device that is important to Unraid! (However, since the desired device is not available to be bound, the VM expecting that device may not function correctly.) Devices bound in this way can be passed through to your VMs by going to the VM tab, editing the template, and then selecting the appropriate device from one of the hardware dropdowns. Can't find it? Check under "Other PCI Devices". If the System Devices page shows that multiple devices are in the same IOMMU group, it will automatically bind all the devices in that group to vfio-pci. You should then pass all devices in that IOMMU group to the same VM. Note: If you make hardware changes after setting this up, it would be a good idea to disable autostart on your VMs first. Then shutdown, add/remove hardware as needed, and boot back into Unraid. Visit the Tools -> System Devices page and ensure the correct devices are still being bound to vfio-pci. Adjust as needed and reboot, then start your VMs. Troubleshooting Tips If you had the VFIO-PCI Config plugin installed, you should remove it as that functionality is now built-in to Unraid 6.9 The System Devices page writes the device details to config/vfio-pci.cfg file on the flash drive. If you ever want to "start fresh" simply delete this file and reboot. (New in beta24) If there was a vfio-pci.cfg file to process during boot, System Devices will include a "View VFIO-PCI Log" button that details each of the devices that were (un)successfully bound during boot, along with any available error messages. Be sure to upload your diagnostics ( Tools -> Diagnostics ) when requesting help as both the config file and the log are included in it Hopefully this is helpful Feel free to let me know in the comments if anything is unclear or wrong.
  11. the static route is definitely required
  12. Change the slider from Basic to Advanced, then on the "Local server users NAT" line there is a comment telling you what static route needs to be setup in your router. There are more details in the "Complex Networks" portion of the first post of this thread. This can help whether you have "Use NAT" set to yes or no, particularly if the "devices" are you are trying to reach are hosted on Unraid.
  13. Sorry, I can't think of anything. The static route you added on the router should have allowed the tunnel to work with NAT disabled.