Taige

Has anyone noticed that no matter what you set the password to in the template, it ends up being the default password? The docker statement shows it on the screen after editing any setting, and it's just setting it to the default value, no matter that I have a different password configured...

Not sure where it came from (KVM or ???), but I found that I could delete it using "route -p delete 0.0.0.0" and that took care of it. I've rebooted and validated that it didn't return.

Hi, I have added a VLAN for a DMZ, vlan 11. This is a network that UnRaid isn't on (from an IP perspective). The VM can reach the gateway, but can't get out. When I look at the route table, I see two persistent static default routes - One is what I have configured in Windows, but the gateway for the 2nd one is the IP of the VM itself, and even though they both show the metric as "default", it seems that the one with it's own interface as the next hop is taking priority. If I look at the firewall, I'm not seeing traffic destined for the internet coming to the firewall. If I delete the default route, it works, but it returns when I reboot. Is this something being added by KVM? If so, how do I resolve this? Thanks

I think when Fedora was working was before I had added a VLAN to the br interface. I reinstalled Fedora and it was behaving the same as Win11. I have a somewhat unusual config. I ended up placing these on a different VLAN (which is bridged to the default VLAN - don't ask, I'm not sure I could adequately explain it), and they both came up and are working as expected.

Oh, and as another Datapoint, I had a Fedora VM up and running on the same subnet, and it worked fine.

I've recently come back to UnRaid. I'm trying to move from ESXi for my VMs. I have installed a new Windows 11 VM, but I'm having issues with it on the Bridged network. I've tried the virtio, virtnet, and Intel network drivers. Oddly, they all will get a DHCP address assigned to them, but I can't ping the default gateway. I can ping the IP address of the UnRaid host. If I change the network source from br0 to virbr0, it works fine, but it's on a different subnet (I'm guessing, NAT'ed behind my Unraid box). I am planning to put a VM in a DMZ, and for that, I'll definitely want it to be directly on that network for port forwarding from the Internet. If I look at the ARP table on the VM, the only thing I have on my local subnet is the broadcast address and my UnRaid host. I'm on the latest UnRAID, 6.12.10. I'm using a Unifi switch and a Firewalla as my gateway. And idea what's wrong here?

I have a VM that I'm trying to configure to use a single NIC with a native VLAN, and multiple tagged VLANs. I've configured the VLANs in UnRaid (2, 10, 11, 15, and 30) and configured the VM to use the native VLAN (with no tag) as well as the various tagged sub-interfaces. When I bring this VM up, I can only successfully communicate via the native VLAN. My VM is tagging the rest of the packets, but they do not appear to be routed to the proper VLAN. Is this possible via UnRaid? To match the partner VM (running under QNAP), it needs to be configured to work with the native VLAN and sub-interfaces on the one virtual adapter. I've already looked into the possibility of passing the NIC straight through to the VM, but that's does not appear to be an option because it's a dual NIC server, and they both have the same PCI id.

@StevenD - Thank you very much. Installed perfectly on my RC7 VM, and ESXi sees it just fine.

I think StevenD hasn't gotten the free time yet. I actually just recently moved my UnRAID from a physical to a VM, and I'm running without OpenVM Tools. So far, it seems to be working well without them. Any down sides to doing so? (Other than VMware host can't shut it down gracefully, etc.) I was running UnRAID on a quad core Xeon (with HT) with 28 GB of ram, moved it to a dual core i3 (I think, also with HT) with only 12 GB of RAM, but found that it didn't perform as well. (Specifically, the docker Channels DVR was slow to skip ahead in video, and sometimes just slow in general - it didn't seem to work nearly as well as it did before). In the meantime, I converted my Xeon machine to ESXi. I ended up moving the controller and drives back to the Xeon, but now run it under ESXi with 4 vCPUs (out of 8 ESXi sees) and 8 GB of RAM. It seems to be running as well as it did before on the physical Xeon hardware.

FYI, I updated to rc2 today, and it went fine. It's up and running fine, so I don't know if there's a difference in rc2 that fixed my issue, or if it was a fluke.

I updated via the WebGui - I selected the "Next" branch, and Check For Updates, then hit Install.

Thank you - I took the USB drive out of the machine (it's mounted internally), copied the /config directory off of it, used the USB creator tool to install a fresh copy on the same USB drive, copied my /config directory back, put it back in the machine, and it booted up just fine. I'll wait for a future RC, or perhaps just wait for the release version.

Where is this config folder? I'm logged into the CLI and there's no config folder in the root. I found a /boot/config folder, but insider is only an ssh folder... No other files or folders...

You are right - They are in Anaheim, CA. I was there like May or June of last year. Not sure why I thought they were in Europe... Anyhow, if there's not an easy CLI based roll back, I'll probably have to do as you suggest. I'm going to grab some dinner and check back in a bit.

Oh yea - I missed that I guess. I'm not much of a linux guy... I imagine one of the lime tech guys would know what to do. I think they are based in Europe though, so they are probably already sleeping.