karldonteljames Posted October 22, 2018 Share Posted October 22, 2018 (edited) Evening All. I've got vlans setup at home, I use them in the following way. Vlan10) General Home Devices (laptops/ tablets etc) Vlan12) DMZ - Reverse Proxy, and a webserver Vlan50) Smart Home tech (amazon echo, smart switches etc. I've just moved my reverse proxy from a Sever 2016 VM running IIS to letsencrypt, however, I cannot seem to get the gateway to appear for vlan 12 within docker. I've attached two screenshots to show how I have my netwrok interface configured in unraid, and then when I open docker the gateway is not pulling across. I've tried adding in new vlans (say vlan 20, with a gateway, and restarting the unraid server, but it doesn't seem to make a difference. Anyone have any ideas? Unraid is connected to a layer three HP switch that has the unraid ports (bonded in a four port nic) untagged for vlan 10, and tagged for vlan 12. (VLAN 50 isn't currently in use in unraid, but will be when i finally finish HomeAssistant. Any help is very appreciated. Edited October 22, 2018 by karldonteljames Quote Link to comment
karldonteljames Posted October 27, 2018 Author Share Posted October 27, 2018 Does anyone have any ideas? Surely if the trunk is untagged and tagged, i should be able to use the docker on the second vlan? Quote Link to comment
ken-ji Posted October 28, 2018 Share Posted October 28, 2018 I can only speculate, but I think if unRAID has multiple IP on multiple VLAN, the docker subsystem gets confused with regards to using a different VLAN per interface.perhaps its a bug with the automatic creation of the docker networks on VLANs where unRAID has an IP and network information. What you can try and its what I'm using is to have no unRAID IP on the VLAN so that unRAID is not accessible on that VLAN; this disables the auto creation of the docker network br0.x, which you then manually create and fill out the desired details. 1 Quote Link to comment
karldonteljames Posted October 30, 2018 Author Share Posted October 30, 2018 I'm happy to remove the IP address to unraid on that VLAN, but how do I go about creating the docker network on the correct vlan? thanks so much Ken-Ji Quote Link to comment
karldonteljames Posted October 30, 2018 Author Share Posted October 30, 2018 Managed it! I removed the IP address from VLAN12, then added it to the docker config under advanced settings. all dockers are now accessible via VLAN12! PERFECT! THANK YOU! Quote Link to comment
karldonteljames Posted October 31, 2018 Author Share Posted October 31, 2018 (edited) Ken-ji, I now have sonarr, qbittorrent and deluge running, but i am unable to add the downloaders to sonarr, they are all in the same vlan 192.168.12.x. any ideas how i can allow them to communicate? it's a little odd as i'm also running homeassistant, appdaemon, influxdb and grafana and they all seem to be able to pull data between them... they are all configured the same way as far as I know. I am able to ping both qBit and Deluge from the sonarr docker. Edited October 31, 2018 by karldonteljames Quote Link to comment
karldonteljames Posted November 1, 2018 Author Share Posted November 1, 2018 A better explanation to the issue i'm having is here. it looks like it is being caused by the VPN Connection within the dockers. 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.