This week the decision was made to tear down the home network and rebuild it to include a game hosting network. Knowing that a TCP/IP protocol would be utilized and the Gateway is already utilizing IPv6, both networks will utilize IPv4. Since my bandwidth is 1000Mbps/1000Mbps, I’ve given my home network an allocation of 100Mbps at the Gateway and the game hosting network 900Mbps. There was also a condition applied to the connection point of both networks in the Gateway to not allow each other to communicate. The game hosting network is fairly simple, a subnet is utilized to reduce the amount of open IP addresses which allows for further security as the game hosting platform utilizes docker to add containers within each server. The cool thing is that docker is not assigning additional IP addresses per game server, but instead using the servers IP and applied Port(s) to each game server for directing traffic. Ultimately, on that side of the home network, it only utilized one TCP/IP set.
On the side of the home network that was for my personal computer, xbox, phone, tablet and type-1 hypervisor, that would require two sets of TCP/IP’s. One would be for the hard lined ethernet and the other for the attached access point to deliver WiFi to the home itself. All of these items would fall under the 100Mbps side of the Home network, but as it is just myself and my dogs, really we don’t use much bandwidth. Even streaming, gaming, phone updating , tablet updating and my dogs watching the “Secret of Pets” on the XBox, nothing lags out. The hypervisor has 5 NIC’s in it, one for maint. on the hypervisor, 2 for home network servers, domain controllers, dns, ect and 2 nics that cross over to the Game Hosting network for additional quick servers that might need to be stood up for any reason.
This has been a fun week for sure. I’ve learned so much with protocols, VLAN’s, bandwidth management, allocations, CiDR, this doesn’t even really feel like learning, more like playtime!
Leave a Reply