192.168.7.xx is an IP assigned by the SMC Barricade router which in turn is connected to 80.33.22.xx external connection.
The issue IMO is clear here - target computer gets 2 packets from source IPs that are 82.35.224.xx or 80.33.22.xx and it does not know which interface to send them to, so it sends to default one, so one of the cards won't work: I think this is exactly what you saying.
I can't give same metric because my SKA server does smart software balancing on lines.
It all worked before when I used Linux router that worked with one physical connection and the other one was directly into server - now I understand that it must have been doing NAT thing by hiding source IP so that routing would work.
What I need is a NAT thingy that would replace source IP to NAT itself and then do another remap when it gets response: I don't understand why my SMC Barricade does not do it - the source IP there is external, not router's. I blame Chico's boss for inefficient networking protocol design
The issue IMO is clear here - target computer gets 2 packets from source IPs that are 82.35.224.xx or 80.33.22.xx and it does not know which interface to send them to, so it sends to default one, so one of the cards won't work: I think this is exactly what you saying.
I can't give same metric because my SKA server does smart software balancing on lines.
It all worked before when I used Linux router that worked with one physical connection and the other one was directly into server - now I understand that it must have been doing NAT thing by hiding source IP so that routing would work.
What I need is a NAT thingy that would replace source IP to NAT itself and then do another remap when it gets response: I don't understand why my SMC Barricade does not do it - the source IP there is external, not router's. I blame Chico's boss for inefficient networking protocol design

Comment