Hi,
On 25 January 2018 at 09:58, Wolf Humble <wolfhumble(a)gmail.com> wrote:
--snippet--
> The devices, ip addresses and gateways are as following:
>
> eth1 – ip1: aaa.189.aaa.254 - GW: aaa.189.aaa.253
> eth1 – ip2: bbb.143.bbb.214 - GW: bbb.143.bbb.213
>
> eth2 – ip3: ccc.170.ccc.202 - GW: ccc.170.ccc.201
> eth2 – ip4: ddd.180.ddd.101 - GW: ddd.180.ddd.100
--/snippet--
On Thu, Jan 25, 2018 at 8:03 AM, Jamie Bainbridge
<jamie.bainbridge(a)gmail.com> wrote:
--snippet--
As far as I understand, your interfaces are both in different
broadcast domains. You cannot join these two together with any link
aggregation like teaming or bonding.
If you need bridging (to join VMs or containers to each network) then
set them up separately. eth1 in br1, this bridge has access to
networks aaa and bbb. eth2 in br2, this bridge has access to networks
ccc and ddd.
--/snippet--
Thanks!
On more question about teaming -- that wouldn't work in my case since
I want ALL IPs to answer at the same time -- but just curious:
It seems like teaming with activebackup would work even for interfaces
that are in different broadcast domains, as long as you don't mind
that only IPs connected to eth1 will answer when eth1 and eth2 are up,
and only IPs connected to eth2 willl answer when eth1 is down. (From
what I remember when testing the activebackup mode earlier in my
setup).
Do I understand that correctly?
Thanks again,
Wolf