It has to do with link priority on the server. You’d imagine that a server that receives a packet that has a return address on the same subnet as it self logically would use that interface instead.
A similar thing happens in switches. For example if you have two vlans on a switch and both vlans have an ip assigned, connect a computer to one of the vlans. You will only be able to reach the switch on the non-routed connection. Even if you also are allowed to reach the second vlan through a router/Firewall.
My guess is that the server receives the packet from the client with src .11.101 dst .10.102 and tries to respond over the interface that has .11.102 assigned.
The client expects a response from src .10.102 and drops the packet.
But I would turn on a packet sniffer in the gateway to see if the returning traffic even passes the Firewall in scenario 1.
I'm in the process of finding a server to run as a homlab.
It will be running proxmox VE and have a couple of machines running at a time for testing purposes. These machines will run anything from server 2022 to debian and various other distros depending on what I wanna fiddle around with.
Does anyone have any experience with Xeon E-2400 Cores or their subsequent "consumer" variants in intel 14000-series running proxmox?
From what i gather in the forums there is a pretty substantial performance difference between e-cores and p-cores which are present in the Raptor Lake CPU's
So the question is:
Would you rather have a Xeon E-2400 8C/16T CPU or an i9 14900 8p16E/32T in a proxmox hypervisor?
It has to do with link priority on the server. You’d imagine that a server that receives a packet that has a return address on the same subnet as it self logically would use that interface instead.
A similar thing happens in switches. For example if you have two vlans on a switch and both vlans have an ip assigned, connect a computer to one of the vlans. You will only be able to reach the switch on the non-routed connection. Even if you also are allowed to reach the second vlan through a router/Firewall.