trott

yes, I just notice the same thing, I'm quite sure before 6.92, it is work as I had to manually add pcie_asmp=off to get rid of some PCIe Bus Error message

usually for wireguard, you only need to forwarder the wirguard port on UDM Pro to urnaid IP, all other port are still close to public

你要把硬盘直通给TRUENAS啊，和urnaid没关系了

yes, it is dual port, I'm only use one of them yet, will test it later

Guys, when I using the VF on VM, it cannot talk to the VM on br0, do you guys has this issue?

I follow the how-to in the forum and using SR-IOV to create some VFs , and create a VM using the VF, but the VM on VF cannot talked to the VM on br0 network 1. VM1 is assigned a direct VF, on network 192.168.2.0/24 2, VM2 is usinn the urnaid default br0 to 192.168.2.0/24 3. VM1 can access unraid host and internet 4. vm2 can access urnaid host and internet 5. other PC on same network can acess unraid host, vm1, vm2 6. But VM1 and VM2 cannot take to each others google search can find some post like below: https://community.intel.com/t5/Ethernet-Products/SR-IOV-on-82576-on-VM-on-VF-can-not-talk-to-VM-on-Bridged/td-p/196387 the solution is to use "bridge fdb add" command to add VF mac addresses and eth0 mac address to bridge forwarding but the issue here is unraid don't have the "bridge" command included, is there any other sulution for this issue?

this is the reason I asked if we can attached a VF to container in the thread, it can help to solve the issue and meet the requirement

如果主要为了moments，你第一时间就没必要选择unraid

never mind, I just find out the network-rules.cfg is changed, change it back fixed the issue

I just update to 6.9.1 today, but after reboot, I cannot access the unraid, it has no network at all, in syslog, I find below, how I can have unraid do not change the interface name to eth15

thanks for the how-to, is it possible to assign the VF to docker container?

check your bios setup, I believe the fan control setting in bios should be smartfan, I using the same board and plugin works without issue

+1

I reformat the cache, now the issue is gone