With 25.04.1 we have the ability to set alias IPs to Apps.
I have 2 network interfaces with the following setup:
eno1: 192.168.178.10/24
eno2: no ip as it is member of br2 and br2 is at: 10.10.20.1/24
For both the eno1 and br2, I can add aliases to use as a “unique” ip for an app.
eno1 aliases are unbridged and work fine on Apps, e.g. Storj, Syncthing etc are at 192.168.178.12 (.13 etc).
br2 aliases also work fine (as you would expect) and I have apps at 10.10.20.2 (.3 etc).
I always understood that you need a bridge for apps to talk to each other (and/or the host system?). Previous TN Scale versions had all the docker apps on the br2 bridge (which was DHCP at the time for me).
Here I get confused and I am not seeing it clearly.
Two questions:
-
if an app has an alias on eno1, will it still route its traffic through the br2 to eno1? As all apps are docker based and I assume docker is fixed to br2?
I am asking this as I saw traffic on br2 while the app that was generating traffic has an alias on eno1. -
Should I remove br2 and just put those aliases on directly eno2? I think all the apps work independent from each other anyway. (is aliases making bridges obsolete?)
Thanks for any clarification.