Setting up a DHCP server with a unique approach requires guidance.
Setting up a DHCP server with a unique approach requires guidance.
The other systems each have just one port. Therefore, situation 2 will be the one for me. Thank you for this, I'll try it and share the outcomes. Yes, I'm aware of this change. It would be ideal if there weren't only two 10Gbps ports. Could be just my thinking, but it's definitely possible that you can't link three systems with just two ports on a switch.
Correct, not all three at 10Gb. It's a good change and should function if you only need two at 10Gb while many 1Gb clients connect to those 10Gb devices that can total 10Gb together—each one still 1Gb individually. Used switches on eBay are likely the best option for more than two ports under $1k.
In reality, the most affordable option with more than two ports is the Netgear XS505M, featuring four 10Gbps ports. However, it's a bit pricey compared to my budget. I'll keep monitoring it and plan to purchase when prices drop. For now, I'm hoping situation two works out.
Attempted this again and still ran into "layer 8" problems. Just pinging directly over the connections works now, similar to before, but not from server 2 to PC. I can't determine the static routes. I've attached a screenshot of my current setup, though it looks incorrect. Setting the network mask to 255.255.255.0 isn't possible (maybe it shouldn't be) because the destination can't be more specific than the mask. The gateway error suggests adding the "from" IP might help. Need more details.
For static routes, focus on the exact PC rather than the whole network. Use precise details: destination IP 10.10.2.2, subnet 255.255.255.255, gateway 10.10.2.1. If you need a /24, set destination to 10.10.2.0 with subnet 255.255.255.0. Set the metric to 1 so the route takes priority over others for those networks.
I came in to mention that this seems like either a missing routing setup or a problem with the routing configuration. Looking through the details, it appears they’ve provided solid guidance.
Good spotting, indeed. The destination IP must be 10.10.2.0, not .1. I kept the samples in manageable /24 ranges for simplicity, but I usually use /30 for peer-to-peer links or /31 when supported.
They simplify things a lot, which makes me feel confused because I’m struggling to get it to function. Follow the setup exactly as instructed, but still can’t connect from PC to server2. I tried both options, and neither works. I need another configuration file to display the settings, including the routing table since it shows the metric, but it doesn’t match 1, so I’m not sure if it’ll help. No harm in sharing it anyway.
Confirm the correctness of ports 1 and 2 under the interfaces. Have you attempted to swap them? Just to verify, did you assign static IP addresses to those ports as 2.1 and 1.1 on the dual NIC server?