The server is setup with 3 NICS, 1 main/management nic and 2 different VLAN nics - non routed. I am trying to bridge the VLAN nics together for a home-built WAN emulator. Below are the network configs:

ifcfg-br0:
NAME=br0
DEVICE=br0
ONBOOT=yes
TYPE=Bridge
STP=on
Delay=0
BOOTPROTO=none
IPV6INIT=no
USERCTL=no

ifcfg-eth1(192.168.2.128/26):
TYPE=Ethernet
BOOTPROTO=none
ONBOOT=yes
BRIDGE=br0
DEVICE=eth1
HWADDR=XX:XX:XX:XX:XX:XX
IPV6INIT=no
USERCTL=no

ifcfg-eth2(192.168.2.192/26):
TYPE=Ethernet
BOOTPROTO=none
ONBOOT=yes
BRIDGE=br0
DEVICE=eth2
HWADDR=XX:XX:XX:XX:XX:XX
IPV6INIT=no
USERCTL=no


firewall IP: 192.168.2.194/26
router IP: 192.168.2.193/26

firewall --(network 192.168.2.128/26)-- eth1 |PC| eth2 --(network 192.168.2.192/26)-- router

I had to split the network up like this so that there was not a straight path on the network around the emulator. Also the hypervisor would not allow 2 different VLANS to have the same network assigned.

If I setup a temp IP on the bridge and take down either eth1 or eth2, I can ping the firewall/router that it is attached to, but not the other. If both VLAN interfaces are up, I can only access the VLAN of the nic that has the same mac as the bridge. The outcome I want is to be able to go from either end to the other end.

I'm not a networking expert but I don't see where you are creating or using a vlan anywhere in your description. I would expect the vlan id to be part of the interface name. Also the ifcfg script should have VLAN=yes.

The VLAN-ID is set in the settings of the VM on the hypervisor (Hyper-V). Would I still need to setup the vlan tag within the eth configs?

Depends where you want to see the VLAN tags, I guess. You can do trunk mode to the VMs, but not sure what you do on the bridge in that case. I've only ever set it up in normal mode.

https://mthode.org/posts/2012/Oct/vl...ng-to-kvm-vms/

So since these are different vlans, should I setup the interfaces as regular eths with an IP and use route to get traffic back and forth?

I was going down the wrong path with bridging. I had to remove the bridge, setup an IP on each eth of the PC, and use routes (route-ethX) to get traffic from one nic to the other.