We actually have a setup like this (but we do have a router and need external access) and I had vMix (Trial) running on 5 computers, 4 as ndi source (with cameras / mics) and 5th for recording via NDI.

We have our main router (Asus 68R running merlin f/w) and 2 Gigabit switches. The vMix source pc's are wired to one of the switches as is a access point. Each switch is wired to the 68R as is the recording PC. Another access point is connected to the 2nd switch as is a couple other PC's (servers) and devices for other things. The access points and 68R provide wireless coverage (dual bands) for the entire location (but no NDI traffic).

For now you just need a switch. I have good experiences with TP-Link, for example the TL-SG105 or TL-SG108.
You can add an access point or router later.

Thank you guys!

I will use a gigabit switch to keep it simple, and Plug-and-play. No management needed.

even then i wouldn't use a router since it adds too much overhead. unless you need to receive and send packets of data from outside your intranet i would always stick with a application switch such as a layer 3 or 4-7. with NDI using a cheap router for dhcp or VLANS or QoS will be much slower than a layer3 switch or 4-7. i only say this because ive tested it with fantastic results using PC7xxx's connecting multiple networks across multiple /20's just using the internal routing tables of a layered switch. using routers instead added TTL's and 100ms lat. Just throwing other options out there if your not routing packets across other nodes outside a physical gateway.

plus i would be happy to test anything since i'm lucky enough to be sitting over hundred different servers and core switches while i get ready to sell them :)

-King

Setting static IPS in a network in my opinion is a must.

OK if you have a visiting laptop or two etc. Have a dhcp range.

But any fixed device on an IP network should have a fixed IP.
I've spent most of my working life around networks of one sort or another and I don't know anyone that builds there infrastructure on dhcp. In a consumers home network it's great you plug it in and it works.. for the layman it's great. But when building integrate systems no way.

In my productions I have multiple networks running over multiple subnets, 1 for NDI, 1 for comms, 1 for remote management, 1 for the outgoing video feeds for streaming, 1 for general internet use. and I dont trust any of it to dhcp, except the general use network.
It makes any testing / trouble shooting easier. It's easier for routing / port forwarding etc. Dhcp has it use, but not here..


A.

PS
This is a forum where people answer others problems with ideas that are intended to help them. Give ideas that they have maybe not thought about etc. people have opinions and on a forum there neither right or wrong. I do believe however it is important to be able to voice opinions, and to be able to freely make an observation on any site, be it here or any other site. I think you will agree it's healthy to scrutinise sites and posts, but only to make them better. By all means post your own ideas and solutions but I see no relevance in the above two posts quoting what I had posted before ? In my mind it belittles tth original, it adds argument with encourages trolling etc, It adds a tone of insult. Again discussion is good and free speech is good, but with relation to the message you want to put over.