If both networks 10.100.100.0/24? And 10.20.20.0/24 share the same level 2 Ethernet segment/vlan/broadcast domain, you don’t even need the third nic, you can setup a secondary IPv4 address on the private nic on the 10.20.20.0/24 network.

I would not call that best practice, but if the number of host on the network is reasonable and you are aware of the security problems created, there’s nothing really wrong with this setup.

Having two nics on the same Ethernet network is actually trickier since you have to do ARP filtering.

I have no experience about what you are trying to achieve, but rdma and related technologies (infiniband, qlogic, sr-iov, ROCE) is not it. These are network technologies that permit high bandwidth/low latency data transfer between hosts. Most of these bypass the IP stack entirely.

Infiniband is a network stack that enable RDMA, it’s only vendor is now NVIDIA which acquired mellanox. Qlogic was another vendor, but it got acquired by Intel that tried to market it as Omnipath, but it was spinned off to Cornelis network.

Sr-iov is a way to share an infiniband card to a virtual machine on the same host.

ROCE is an implementation of the rdma software stack over ethernet instead of infiniband.

Assuming you meant heat and not hear. Upgrading your cooling should not lower the total heat output of your PC (it’s more likely to increase it). The only exception is if you somehow send the heat out of the room, but that would be a crazy complicated setup. Your PC always turn the same amount of electric energy into heat energy and dissipate it in the room. if it’s more efficient it will cool down the components more, possibly giving them the opportunity to increase frequency further, which increase the power draw, which is turn into more heat that is dissipated in the room.

The target storage device for the image can be over the network if that’s an option for you.

I admit the downvote is weird.

I’m not sure about the point of your setup but let’s ignore that :

• Create a vlan “servers” on router B, assign a port (WITHOUT vlan tagging) to this vlan, patch a cable between this port and any port on rouer A
• Put a static IP address 0.x on router B in this vlan
• Enable routing between the default vlan and vlan “servers” on router B .
• Configure router A to not distribute this IP address (by setting up a permanent DHCP lease for example)
• On all your servers put a static route that says : “192.168.20.0/24 via 192.168.0.x”
• If you can setup this route on A, things connected to A will work whether they have the route or not (it’s not a big deal but the routing would be assymetrical)

If you can create a VLAN and a route on A, you can create a distinct “interconnect” VLAN and make all of that nice and clean without the extra static routes on the servers.

Relaunched it to replay the demo : “uplink”, it really lived up to my memory. A self contained half hour of half life fun, with an original map that show off diverse game mechanics. This was really a great demo back in the day.

I’m confused by this device. The point of the parking disc is that you can’t change your arrival hour without being there physically. It seems that it would be easy to make a device like this that automatically reset when the time is up. Are these certified in any way?