Hi all,
Currently, VyOS only supports load balancing using the “Source IP, Destination IP, Source Port and Destination Port” method.
https://docs.vyos.io/en/latest/configuration/loadbalancing/wan.html#flow-and-packet-based-balancing
A connection tracking table is used to track flows by their source address, destination address and port.
This leads to errors with the websites that use session key management method by IP address (automatically log out, cannot log in, …)
This can be solved by the load balancing method based on only “source-address / source IP address”, this ensures that an IP will go on 1 WAN, will avoid similar errors, and is easy to troubleshoot, a network with many clients still can use multi-WAN normally.
I see that we now have this load-balancing mechanism for NAT Load Balance.
https://docs.vyos.io/en/stable/configuration/nat/nat44.html#nat-load-balance
NAT Load Balance uses an algorithm that generates a hash and based on it, then it applies corresponding translation. This hash can be generated randomly, or can use data from the ip header: source-address, destination-address, source-port and/or destination-port. By default, it will generate the hash randomly.
Mikrotik also supports this mechanism through the PCC feature and marks-connection as the source address.
[Per connection classifier - RouterOS - MikroTik Documentation]
So I see that we can completely deploy this feature.