Guest Posted January 18, 2020 Share Posted January 18, 2020 I have a fairly complicated setup and my unraid VM can not talk to my dockers. Can someone help me sort it out? eth0 = 192.168.10.19 Dockers are run in bridge mode as well br.90 = VM 192.168.90.22 I can currently curl 192.168.10.19 and get the header however I can not curl any of the docker ports on the same ip. Quote Link to comment
Siwat2545 Posted January 18, 2020 Share Posted January 18, 2020 You have 2 Options 1. Set subnet to 255.255.0.0 2. Change br.90 lan group to be the same as eth0 Quote Link to comment
Guest Posted January 18, 2020 Share Posted January 18, 2020 8 minutes ago, Siwat2545 said: You have 2 Options 1. Set subnet to 255.255.0.0 2. Change br.90 lan group to be the same as eth0 Can you explain option 2? Quote Link to comment
Siwat2545 Posted January 18, 2020 Share Posted January 18, 2020 (edited) 26 minutes ago, SRPick said: Can you explain option 2? be.90 is on 192.168.90.x it need to be 192.168.90.x Idealy use the same bridge for VM and docker Edited January 18, 2020 by Siwat2545 Quote Link to comment
Guest Posted January 18, 2020 Share Posted January 18, 2020 7 minutes ago, Siwat2545 said: be.90 is on 192.168.90.x it need to be 192.168.90.x Idealy use the same bridge for VM and docker Was trying to isolate traffic. is there another way to do it without opening up unraid to the same network as the vm? Quote Link to comment
Siwat2545 Posted January 18, 2020 Share Posted January 18, 2020 Was trying to isolate traffic. is there another way to do it without opening up unraid to the same network as the vm?Then give your VM 2 interface, one with eth and one with br I'm surprised that you managed to make a http get request to your Container with your current configuration are you sure that the header is returning from your Container?Sent from my Pixel 3 using Tapatalk Quote Link to comment
Guest Posted January 18, 2020 Share Posted January 18, 2020 (edited) 5 hours ago, Siwat2545 said: Then give your VM 2 interface, one with eth and one with br I'm surprised that you managed to make a http get request to your Container with your current configuration are you sure that the header is returning from your Container? Sent from my Pixel 3 using Tapatalk the curl is returning from unraid (port 80) itself. Edited January 18, 2020 by SRPick Quote Link to comment
Siwat2545 Posted January 18, 2020 Share Posted January 18, 2020 the curl is returning from unraid (port 80) itself. Try giving your VM 2 Interface and use Windows Firewall to permit only docker port If not then you need to setup a NAT Quote Link to comment
Guest Posted January 18, 2020 Share Posted January 18, 2020 I'll give that a try. just seems weird that it isn't routing via the switch when it should be. it's like unraid is snatching it up trying to route it and failing to do so. Quote Link to comment
Guest Posted January 18, 2020 Share Posted January 18, 2020 (edited) Ok, seriously stuck on this now. I have given the dockers their own network in hopes it would allow it since its no longer the host ip. Its still not working. Edit: I have for the time being been able to get a hardware nic passed through. I feel as if this is a banded for what i need to do as i am now limited by the ports i can pass through. Edited January 18, 2020 by SRPick 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.