murkus
Members
-
Joined
Solutions
-
murkus's post in vhost0@eth0 is using the same IP as eth0 -> this is an IP collision, how to do better? was marked as the answerI investigated further wit different settings for Docker and I found that vhost0@eth0 will only then get an IP (and then it is the same IP as eth0) if both of these are enabled (if only one of these is enabled, vhost0 does not get an IP):
Host access to custom networks IPv4 custom network on interface eth0 (optional) I have no ides why both were enabled on my server (and it is quite possible I did this myself without knowing what I was doing).
Just to clarify whether I really need those, could someone confirm or correct my assumptions:
IPv4 custom network on interface eth0 (optional): I only need this, if I want to have a containter to use an IP from the subnet in which the IP of eth0 is located. Correct? Host access to custom networks: I only need this if the unraid host should access a service provided by some of the containers running on the the unraid host. Example an agent running natively on the unraid host needs to connect to a service (like NMS or backup) in a container. Correct?