forty2
Members
-
Joined
-
Last visited
-
Yes, the field is currently validating that it has to be an IP address. The issue for me is that I have my home network set up such that the local domain names are things like "hostname.home.domain.other.stuff". If I just add the IP address to the DNS field, I can use those fully-qualified names, but I'd like to be able to use just "hostname". Typically that's done by setting the DNS search domains, which Wireguard does actually support, but for some reason they've implemented it as an add-on to the DNS option instead of as its own option 😞 The end result is that the validation (which makes sense if the option is only for DNS servers) is preventing me from setting a related-but-separate option for search domains.
-
It would be nice if there were a way to specify DNS search domains in the Wireguard peer config. In the config file, it's specified as extra comma-separated values in the same `DNS=` field as peer DNS servers. I'd hoped I could just add my search domain in that field, but apparently there's some form validation going on that won't allow me to type a domain name into that field.
-
Apologies if this is a duplicate; I did some searching but didn't turn up anything. However, a lot of these terms are hard to search for 🙂 My Firefox browser updated to version 100 this morning, and now the left-side nav menu using the "azure" setting for "Dynamix color theme" is shifted too far to the left. It doesn't break any functionality, but it does look bad. I tried downgrading to Firefox 98 (couldn't find an installer for 99) and everything goes back to looking correct. It's happening because the "#nav-block" div has a "mozilla" class applied that sets a left margin of -17px. According to /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php, this is a "Firefox specific workaround" but it appears to be no longer necessary as of Firefox 100. I don't know what the issue was that it was fixing, so I'm not sure why version 100 fixes it. I'm on unRAID 6.9.2; I haven't tried any of the prereleases (I generally prefer to wait for the actual release). I've marked this as an Annoyance because it doesn't actually break any functionality, but it really looks terrible so I'm hoping it gets fixed 🙂
-
Great, thank you! What I'm trying to get working right now is joystick/gamepad input support. If it is possible to do that with a plugin, that would obviously be preferable. I have a fair amount of experience building custom kernels and modules on other platforms, but I've never done it on Unraid before the last couple of days, and I also have no plugin dev experience. So right now I'm just trying to muddle my way through and see what I can get working 🙂
-
Are kernels built with the kernel helper docker compatible with the "regular" nvidia plugin? In other words, if I want to build a kernel with support for some unrelated feature and I want my Nvidia card to keep working, do I have to set BUILD_NVIDIA to true, or can I set it to false and keep using the plugin? Also, I too am interested in getting sound drivers working on Unraid, so I'll send a quick PM about that.