ljm42

Administrators
  • Content Count

    1905
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by ljm42

  1. You just want to remove this: vfio-pci.ids=8086:1c20 and set it up via Tools -> System Devices instead. See:
  2. You'll need to revert that. Think of this as a tunnel *between* the local and remote networks. It is a unique network of its own, not part of either the local or remote. If you want to use the LAN's network address, switch to "remote access to LAN"
  3. Is there a bug report that describes the problem in more detail? I was just able to change the "Warning disk temperature threshold" and "Critical disk temperature threshold" for my cache drive in rc2 without any problems. But maybe you are referring to something else?
  4. doh! have to let the monthly parity check finish before I can upgrade
  5. I see you are using the Device Manager to bind devices to VFIO-PCI, which is good. But I'm hoping someone with more VM experience can weigh in here
  6. A Google search for "unbound dns rebind protection" points to this: https://pfsense-docs.readthedocs.io/en/latest/dns/dns-rebinding-protections.html Maybe that can get you started? Another option would be to override the DDNS provided by unraid.net and hard-code your DNS server so that on your network, yourpersonalhash.unraid.net resolves to the correct IP. The downside is if you later change the IP but forget you setup this local DNS entry, it will be extremely hard to figure out why things aren't working. On the Settings -> Management Access page
  7. oh I just realized my "the answer to life, the universe, and everything" blurb isn't visible, odd
  8. Aha! Many thanks to you and @tmchow for reporting this issue with validation errors on hidden fields. I'm working on a fix for the next release.
  9. The Chrome error message shows that your client computer is unable to get an IP address for yourpersonalhash.unraid.net. The most likely cause is DNS Rebinding, although it could be some other local DNS problem. On your client computer, go to a command prompt and type ping rebindtest.unraid.net If rebinding is NOT an issue you will see that address resolves to 192.168.42.42 (the ping will still fail, but what we are checking here is whether it can resolve to an IP address) C:\>ping rebindtest.unraid.net Pinging rebindtest.unraid.net [192.168.42.42] with 32 byt
  10. Hopefully folks are able to see this message in the webgui when setting up VPN tunneled access? Things won't work right if you start a second tunnel while "VPN tunneled access" is active.
  11. Ah, I guess that was assumed in the guide, but not specifically stated. I modified the second paragraph to hopefully make it clear that the VM requires a physical USB flash drive.
  12. When asking the community for help, please upload your anonymized diagnostics ( from the Tools -> Diagnostics page )
  13. According to the screenshot, the certificate doesn't expire until Apr 2021, so renewing would not help. What happens when you press "Update DNS"? Does it show that the correct IP address "has been updated for unraid.net"? Sorry, IE is not supported by the Unraid webgui. Please use a current version of Chrome or Firefox. Pretty sure a current version of Edge would work too.
  14. No, passing your boot drive to a VM would not be good. I'm not clear which area of the interface you are looking at. Please provide screenshots showing the issue and upload your diagnostics (Tools -> Diagnostics). Thanks!
  15. Cool. I am not an expert with this, but note that your switch also has to be configured to support this type of bond. I found some info here: https://wiki.linuxfoundation.org/networking/bonding#switch_configuration If your switch does not support "balanced-rr" or isn't specifically configured for it, the "active-backup" bond is probably best.
  16. I updated the second post to address this question in a more generic way
  17. At some point in the past you added this to your syslinux file: vfio-pci.ids=8086:150e This is the old way of stubbing a device so that Unraid will not install a driver for it. In 6.9 we do that using the webgui. First go to Main -> Boot Device -> Flash and choose "Flash backup". This will give you a zip file of your settings "just in case" Then go to the Syslinux tab on that page and remove "vfio-pci.ids=8086:150e" from this line: append initrd=/bzroot vfio-pci.ids=8086:150e so it looks like this: append initrd=/bzroot
  18. You really shouldn't have two un-bonded nics plugged into the same network. Networking isn't meant to work that way, you could have any number of random, hard to track down problems in the future.
  19. Just to clarify - this pfsense screen is on VOID's network right? And where you blacked out out the source and destination IPs - the "Source" column is NODE's public WAN IP and the "Destination" column is VOID's public WAN IP? If my assumption above are correct then I'm afraid I'm stumped
  20. Oh bummer, I thought we got that working. The ping function on NODE just calls "ping 10.253.1.2". Traffic to that IP triggers WireGuard on NODE to try and open a tunnel to VOID. Once the tunnel is open then the ping command travels over it. So pfsense isn't blocking the ping, it is blocking the incoming WireGuard request from NODE. The fact that you can see the traffic being blocked means DDNS is correct at least. I would say there is an issue with the port forward on pfsense.
  21. WireGuard fails silently. This is great for security, but it makes troubleshooting very difficult. My best guess would be that your Local Endpoint does not resolve to your actual WAN IP, or else there is a problem with your port forward. But there could be other issues, I have tried to consolidate everything to the first two posts here: https://forums.unraid.net/topic/84226-wireguard-quickstart/
  22. Great catch! Anyone using the "Local tunnel firewall" option will run into this. If you start a tunnel using the webgui it will look like it started, but when you refresh the page it will actually be stopped. This can't be fixed by the plugin, it will be fixed in the 6.9.0-rc3 release of Unraid. In the meantime, anyone having this issue can solve it by adding this to their /boot/config/go script and rebooting: if ! iptables -S | grep -qom1 "WIREGUARD$"; then iptables -N WIREGUARD iptables -A FORWARD -j WIREGUARD fi if ! ip6tables -S | grep -qom1 "WIREGUARD$"; th
  23. I am looking for ways to improve the WireGuard interface so we can avoid configuration issues. I was prepared to add a check for ampersands in the peer name, but in my testing it doesn't seem to cause any problems. I am using the official WireGuard Android client (dated Dec 24, 2020). Would you mind testing this again? I don't want to prevent people from using ampersands unnecessarily
  24. Thanks for the details @dja So the issue was capital letters, numbers are fine but the validation routine will only accept lowercase letters. I am working on a fix for the next release that will automatically change capital letters to lowercase.
  25. great! I did a Google search for "rsync slows down over time". There are a lot of results Maybe some ideas here? https://www.reddit.com/r/linux/comments/s6moh/suddenly_rsync_transfers_at_about_25_of_normal/ https://itefix.net/content/transfers-slowing-down-over-time