Defylimits

Well I had the same issue, thanks Celsian, Have to agree with Meep tho, very counter intuitive, been bugging me since uprgraded to 6.12.2. Weirdly it didn't get resolved when I tried to downgrade!

This Solution from Celsian worked - Thread - https://forums.unraid.net/topic/140858-vms-on-br0-cannot-access-the-internet-after-6120/#comment-1283343

Ok bit of an update, I reverted to 6.12.1 but appears to have made no difference However I did notice my Windows VM can access docker webpages that are either on my custom docker network "dockernet" and dockers that are assigned to the "host", but not any of the dockers on br0, so there appears to be something blocking the VMs from communicating with the main network. So I'm going to guess its something to do with the routing table, but not sure how to fix that tbh.

So I have 2 VMs I run constantly, my HAOS and a Windows 10 VM. They have both recently lost connection to my network, and it seems to be after I did an update 6.12.2. I do have VLANs running, a Server VLan (100) 10.10.10.0/24 and an IoT Vlan (20) 192.168.20.0/24. With both being on the 100 Vlan, and the HAOS having a second connection to the IoT VLan. The Unraid interface is on the 100 Vlan as well and is the default Vlan for the port the server is plugged into. I have tried updating the Network Source, from br0.100 to br0 and even virbr0 but no connection. Have also tried chaning the Network model to virtio-net from Virtio io but not luck then either. Weirdly I can access either of the IP's and the Window VM shows no connection, however in my Ubiquiti router I see all 3 connections and fixed IP's from the 2 VMs even after refreshing the MAC addresses from the Network connections as well. Am really confused, all the network connections for Dockers are working, some of which are host, others bridged and others on custom network. Not sure what the problem is or what to try, anyone have any idea? Diagnostics attached btw. tower-diagnostics-20230706-1638.zip

Idiot, didn't Stub the graphics! Tools >> System devices - Select IOMMU Group with Graphics card in and scroll to the bottom clicking "Bind Selected VFIO At Boot"

Looking at the Syslog I have these errors around the time having the issue? Am I missing something?

So I've got an interesting issue, if I assign a graphics card and then start the VM, my VM Manager seems to crash. When I click on the VMs tab or on VM Manager under settings both pages from the Unraid GUI it will not load, I also loose access to the Dashboard page which will not load correctly. VM's already running still appear to be accessible when this is happening though and Dockers appear to be online? To get the system back working I need to reboot, but I can't do this from the graphics and have to go power off the server physically and then restart it that way. I've got three graphics cards in my machine, a GT710 for Unraid, a Quadro P600 for Plex transcoding and the 1070 I'm looking at passing through to my VM. I tried this on the Windows VM I had, just by changing from VNC graphics to the 1070 and experienced this crash a number of times, reseting back to VNC graphics and everything works fine. Looking something up I found it might be an issue running the OVMF BIOS, so I setup another Ubuntu machine with SeaBios, but just had the same issue. Wondering if anyone has any ideas? Btw hello again everyone, last time I was in the forum was back in March 2020, pandemic kept me away from home for some time so I didn't have a chance to fiddle and bugger anything else up until now!

56GB of ECC RAM, as one of my 8GB sticks died. I did have up to 128gb when I was running an VMware system in a HP DL360, but that as too noisey for home usage when I had to move it out of the Data centre it was in. Also when I migrated to UnRaid and never looked back!

Thanks for the reply, Cheers, it would be good if you could just enter the network_ID's separated by a comma in the edit docker options Yes pretty much, I believe it is possible - https://support.zerotier.com/knowledgebase.php?entry=show&search-for=&article=ZWFhNWMyMTZjODY1ODcwNmFhZmJjYmRhN2I5MjRhOGQ_ Step 2 and 3 are easy to do. Its step 1 that requires some messing around with the IP tables within unraid/docker which would allow for the server to act as a NAT and forward traffic. (sorry not really a networking person!) Then you should be able to select on the client side whether you just want to connect to the zerotier network or use that network as a default gateway for all traffic. Unfortunately I've tried tower.local and it didn't work. Although I've had issues before with this on the local network it is on, so will have to look into the problem a little more. Thanks for pointing me towards the avahi daemon.

I have to say this is pretty awesome. Set up this afternoon and is working perfectly between my unraid server, my hosted VM on said server (I remote into) and my laptop I'm on in a different country! I do have a few queries however, Is it possible for the unraid server to be connected to two different ZeroTier networks and how would you enter 2 network ID's? (One for me and my devices and another for other users). How do I configure the unraid server to be able to act as a default/remote gateway. I've added the ability in my Zerotier network by adding the 0.0.0.0/0 route to the assigned IP of the unraid server on the Zerotier network, but I need to do routing at the server I believe? It would be nice if that was an easy configurable in the docker application. Lastly and not really applicable to the docker, but how would I configure DNS for this network. as in I have to use the IP of the unraid server on the Zerotier network to access it and not able to use //tower in the web browser. Cheers anyways!