poldim Posted January 8, 2017 Share Posted January 8, 2017 I've got the following networks: I've setup my unraid server on the homelab network as well as the home automation and WLAN VLANs [settings]. I can access the GUI no problem from all three networks and its functioning as it should (eth ports are untagged for VLAN 20 + trunked [tagged] for for 30 + 40). The problem is that I cannot get the VMs to communicate at all. The two Win VMs are unable to ping anything and do not obtain DHCP IPs. I've assigned one to the default br and one to br.30 [options]. Behavior from both is the same with no connectivity. What am I doing wrong? Quote Link to comment
bit2bytes4fun Posted January 9, 2017 Share Posted January 9, 2017 unraid is not a router. When placing a VM on a VLAN, it is a single host on a single network. Layer 2 VLANs logically separate the layer 3 subnets from subnets on the same physical device. You need a router connect to all VLANs to route IP traffic from the VM to each other and if need be, provide DHCP services for each VLAN from a router or DHCP server. Hope this helps Quote Link to comment
poldim Posted January 9, 2017 Author Share Posted January 9, 2017 unraid is not a router. When placing a VM on a VLAN, it is a single host on a single network. Layer 2 VLANs logically separate the layer 3 subnets from subnets on the same physical device. You need a router connect to all VLANs to route IP traffic from the VM to each other and if need be, provide DHCP services for each VLAN from a router or DHCP server. Hope this helps The first screenshot of the networks list IS from my router. I'm not trying to use unraid as another router. Quote Link to comment
NeoDude Posted January 9, 2017 Share Posted January 9, 2017 Do you have a firewall rule allowing access between VLANs? Quote Link to comment
poldim Posted January 9, 2017 Author Share Posted January 9, 2017 Do you have a firewall rule allowing access between VLANs? All cross VLAN communication is up and running. I can access the GUI no problem from all three networks and its functioning as it should (eth ports are untagged for VLAN 20 + trunked [tagged] for for 30 + 40). Only the guest network is islanded. Quote Link to comment
bonienl Posted January 9, 2017 Share Posted January 9, 2017 You need to add routing for the VMs by CLI if you want VMs to communicate with each other. Your router knows all networks, but the VM bridges do not know the way back. For VM1 (VLAN 20): ip route add 192.168.3.0/24 dev br0 For VM2 (VLAN 30): ip route add 192.168.2.0/24 dev br0.30 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.