When you create the bridge, first assign the two unused NICs to the bridge, do not change the the physical NIC port your pc is connected to at that point. Next re-assign the LAN to the bridge interface, you'll appear to lose the connection, at this point you need to connect your physical LAN cable to one of the two NICs assigned to the bridge, wait about 30 seconds, refresh your browser and you should be back in business, now add the third NIC to your bridge and you are done.
So is there a setting I am missing to allow all network communications between all NICs connected to the bridge.
That's the preferred method. Really depends how much traffic is on the individual ports. In my case it's Port2 _> Modem_Lan for monitoring purposes and Port1 -> rest of LAN. I could of course have put the modem onto a second network address range and achieved the same thing, but I went from using a switch to a bridge as it was quicker.
Although I have bridge set up as a unmanaged switch now, I am interested if there is a more efficient way to set this up. Not sure if the unmanage switches are smart enough i that they only route traffic onto the port where the device is connected...or it 'broadcasts' it on all ports hoping one has the device with that IP is connected. May i the future need to make work smarter to reduce network loading (especially if I add a few more IP cameras).
Not sure if there are many strong cases for software bridging these days given how cheap the hardware is?