Multiple NICs - Bridge To VMs

[brian.cline2]

I have searched and searched and I feel really stupid, so I'm tucking my tail and asking.

TLDR:

Why do I lose connection to the UnRaid webUI when I enable a bridge connection on a separate NIC?

 

Long Versioin:

I am running an older Dell R720 (circa 2014).  Thing runs great and I have been running UnRaid very happily for quite awhile.  Currently running 6.10.3

 

I'm wanting to start loading up some VMs to play around, so I thought I would bridge a couple NICs over for them.

My current setup is eth0 and eth1 bonded using 802.3ad (192.168.2.10).  Working beautifully.

When I bridge over eth2 (192.168.100.10), I lose connection via the webUI at .2.10.  I have to then connect using .100.10.  Almost like the new bridge is taking over the host connection or something.

 

When looking through the help, I saw this:
"Select which interfaces are member of the bridged interface. By default eth0 is a member, while other interfaces are optional."

 

So my question is - because I'm bridging eth 2, does that "take over" the "main" connection (eth0 and eth1 because they are bonded) into UnRaid's webUI?  And if so, should I take my bonded connection to eth2 and eth3 since they are optional bridges and set the VM bridges to eth0 and eth1?  How does UnRaid know which connection to use?

This is a little out of my comfort zone, so hopefully this is enough info for someone to provide me guidance.  If I'm missing anything, please let me know.

 

I appreciate the help in advance all!

[brian.cline2]

bump

[JorgeB]

On 8/31/2022 at 9:42 PM, brian.cline2 said:

because I'm bridging eth 2, does that "take over" the "main" connection (eth0 and eth1 because they are bonded) into UnRaid's webUI?

Not really a network guy but it won't take over unless you include eth0 and/or eth1 in that bridge, but why not just use the current bridge or pass-trough the NICs to the VMs directly?

 

 

[brian.cline2]

On 9/13/2022 at 9:57 AM, JorgeB said:

Not really a network guy but it won't take over unless you include eth0 and/or eth1 in that bridge, but why not just use the current bridge or pass-trough the NICs to the VMs directly?

 

 

From what I was seeing in the help is that bridges automatically include eth0.  Am I interpreting incorrectly?

 

The VMs I want to use are on a separate VLAN, so my understanding (limited at best) is that I would need to create a network bridge for those VMs.  Is my thinking not correct?  I have tried to research and watched videos, but I'm kind of struggling to find concise information on this topic.

 

My home network is .20.x which is where unRaid lives.

I have a work network of .100.x which I want 1 VM.

I have an IoT network of .50.x which I want 1 VM

 

When I create the bridge for those networks, they connect to the network correctly (get the correct IP address), but unRaid then is no longer accessible via the .20.x network.  Also, my docker UIs are no longer available (Plex / Overseer / Sonarr / Radarr / etc).  I have to use the .100 or .50 address to access unRaid's webUI.

 

Again, if my thinking is completely off, please let me know.  I'm more than happy learn the "proper" way if this is not it.

[JorgeB]

Lets see if @bonienlcan take a look, not my area of expertize.