May 4, 20188 yr Short answer is there an advantage using bridge over custom eth0 when setting up a docker, they both seem to work or is it just to run whatever the default is which seems to be bridge? i'm running the latest unRAID 6.5.2- rc1
May 5, 20188 yr Bridge mode - shares IP with unRAID - usually ok but sometimes annoying because container wants a specific port that's already in use by unRAID or another container. - your network cannot distinguish between container traffic and NAS services (hard to perform QoS or specific VPN routing) Custom eth0/br0 - allows your container to have a different IP from unRAID. - This is mostly OK since this means stuff like QoS and selective VPN routing can be done. - However, this prevents all communications between the container and unRAID (which prevents stuff like reverse proxying) unless you have VLANs or extra network interfaces.
April 13, 20224 yr On 5/5/2018 at 7:52 AM, ken-ji said: Bridge mode - shares IP with unRAID - usually ok but sometimes annoying because container wants a specific port that's already in use by unRAID or another container. - your network cannot distinguish between container traffic and NAS services (hard to perform QoS or specific VPN routing) Custom eth0/br0 - allows your container to have a different IP from unRAID. - This is mostly OK since this means stuff like QoS and selective VPN routing can be done. - However, this prevents all communications between the container and unRAID (which prevents stuff like reverse proxying) unless you have VLANs or extra network interfaces. Hey - I know its been a while but was curious what the difference is between Custom: eth0 and Custom: br0? Thanks
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.