I have created a proxy appliance by setting up a veeam virtual lab. I use this proxy appliance for additional testing purposes which I do "outside" of a normal SureBackup-Job.
For example if I wannt to test a new setting for our DC's I will do a Instant Recovery of our DC's, connect them to the test-Network (which is also assigned to the proxy appliance) and connect via RDP to those vm's using proxy appliance in between. Because of the setup made when I creating the virtual lab, the proxy appliance will redirect all traffic from my subnet 192.168.254.0 to the "internal" subnet 192.168.0.0 and of course, it will do a NATing.
Everything is working as expected but now it's getting excited: Sometimes there is an existing vm (lets say with ip 192.168.0.33) in my testlab, which will be needed in the future and has been suspended before. When I do a IR of the same source-vm and start it in my lab, proxy appliance won't route the traffic of 192.168.254.33 to 192.168.0.33. What I have to do then is to shut down the previous existing vm (which has been suspended before) and if I start the "new" vm, proxy appliance will route as expected.
Now the question is why proxy appliance acts the way it does. I suspect that this problem is related to the different mac-addresses both vm's have and proxy appliance does not update it's routing table between IP and MAC provided by ARP and therefore sends the layer-2-frame to the wrong recepient. Or is it maybe a configuration issue within vmware's virtual switch?
Thank you for your thoughts.