June 11, 20251 yr I have been putting off asking this question because I wanted to find a solution but have not found one.Backgroundunraid server has a 4 port nic, each port is connected to a different vlan. (10 br0),(20 br1), (30 br5).10 for servers20 vpn vlan30 in house pc's4th nic not in useDockers are on either a proxynet, bridge, or brXRecently I've redone my media to follow the Trash guide, my issues was with the script that will stop qbit and move files and restart qbit.I posted about this and got help but i was ignoring the error, no route to host. I ignore it because "there's no way, it's on the same server"qbit is on (br1) or the vlan 20, no issues for the arrs that are on the proxynet, they can talk to it because each arr is also part of (br1) so basically they have an ip from proxynet so they can talk to each other and an ip from (br1) so they can talk to qbit (im sure there's a cleaner way but i like it this way)in the setup there's and api that talks to qbit and script that tells it to pause so mover can do its thing. All of that is working but its not talking to qbit.So when I did the most basic of tests (ping) qbit ip from the terminal ( on the dashboard i click the console button) and pinged qbit and no reply (hence the no route to host error).I thought easy fix add a route from unraids default network ( br0 or vlan 10) to qbit but that doesn't work because there's already routes to each brX network and it should work. Its not a firewall issue.I've added some visuals, the one highlighted is the proxynet for the dockers.I am sure if the was just a vanilla setup that only used bridge or host networking it would not be a problem.any help would be amazing
June 12, 20251 yr Community Expert Solution this seems more like a issue of vlan tagged and/or how you setup the vlans...unraid server has a 4 port nic, each port is connected to a different vlan. (10 br0),(20 br1), (30 br5).Usually unraid will show br0.10 to designate that the br0 interface over vlan10*Vlan Networking on Unraid s is a pain to explain...review post:https://forums.unraid.net/topic/190501-unraid-in-unifi/#findComment-1558254start at the top and go thorugh the whole post!Unraid is not networking equipment... untaged / taged vlan on a interface issue...############################the br-#### is normal to see that is a software bridge containing over and made for the docker usually something set to a custom br0 - macvlan/ipvlanGiving this info:as the dockers don't see br0.10 unraid is using default vlan1 when calling br0 for this docker and ip range. Thus a cros talk miscommunication issue...The fix is removed the br5, br1 and make a docker network at interface br5.vlan# etc etc...This is called vlan tagging... Other unraid settings need to be checked and setup...as example seen here*You shouldn't have to disable bridging...Make sure vlans are enabled in the unraid network interface tab...under docker settings.*I recommend using macvlan...Enable host custom access enable preserver custom docker settings...Move to macvlan is set to ipvaln*Macvlan is prefered due to isolation and the need for each service / device gettign a different mac address...under vm setting make sure the vm netowrk is not set to vmbir set it to br0as this changes things with unraid vm hyperv switch taht was a breaking point for how soem docker networks were created...then proced to make docker networks at br#.vlan at the ip scheme... (YOU MAY NEED TO DELETE EXISTING DOCKER NETRWORKS!Double check newotk settings . layer 3 swith settings . router setting to confirm a bridge...use console and test dockers suh as docker run bash connected to your docker vlan... Do to isseu with unraid and otehrs networking setups espcal with thoses who won't follow the instruction as seen in that post... I will no longer give commands nor help any further than saying it is possible but not easily done and setup on unraid due to many points of failure and netwroking hardware one uses...I hate unraid with Vlan setups wish its was easier and done in the web ui... unraid is not networking equipment...--May put in a feature request to have the ability to make docker networks within the web ui. and a area for vlan taging a interface... a lot of php code and terminal networking commands woudl need pre-programmed to make that work... doubt the devs will implement... (as I moved away form unraid do to similar issues and the inability to edit br0 docker network...good luck...
June 18, 20251 yr Author Thank you for the links and the time to explain, I am still digesting the info.Just to clear a few things up.pfsense is my choice of poison and a cisco 3850 is the managed switch.vlans are managed on pfsense and work as intended.Unraid was not setup with vlans at all, after watching the two youtubes i see where the br whatever can be confusing in my post. My br do not have the i.e. br0.10on my unraid 3 of the 4 ports are connected to a port on the switch that is on a assigned vlan, hence the 10 20 30.I used macvlan until one the of the updates for unraid stated it was better or more stable to use ipvlan with docker.I also noted that the two examples each user has only one network card and i can see if you have vlans on your network and want your containers or vm;s to have access you have to create the vlans.I may have to revamp my networking.thanks again for taking the time to reply.
June 18, 20251 yr Author So it seems I made this issue a bigger, i found my solution staring at me.Need to enable that and boom it worked.
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.