You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In traditional load balancer, SNAT could choose local IP addresses created/assigned to local network interface, it has two main benefits as far as I know:
local backend server/endpoint gateway pointed to the load balancer local network ip, when deploy load balancer, no need to change backend server/endpoint gateway IP
select pool of local IP addresses can increase concurrent connection to backend server > 64k since 4 tuples concurrent connection is limited to 64k
now loxilb only support one arm deployment with assigned IP address on interface as SNAT source ip.
Describe the solution you'd like
Maybe create a bpf map with pool of IP addresses which are also assigned to local network interface, when doing SNAT, loxilb could round robin select the IP in the pool of IP addresses as source ip for each connection
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
in loxilb HA environment, this pool of IP addresses can be "floating" IP addresses in HA, meaning this pool of IP addresses follows the active loxilb unit and get assigned to the active loxilb.
Is your feature request related to a problem? Please describe.
In traditional load balancer, SNAT could choose local IP addresses created/assigned to local network interface, it has two main benefits as far as I know:
local backend server/endpoint gateway pointed to the load balancer local network ip, when deploy load balancer, no need to change backend server/endpoint gateway IP
select pool of local IP addresses can increase concurrent connection to backend server > 64k since 4 tuples concurrent connection is limited to 64k
now loxilb only support one arm deployment with assigned IP address on interface as SNAT source ip.
Describe the solution you'd like
Maybe create a bpf map with pool of IP addresses which are also assigned to local network interface, when doing SNAT, loxilb could round robin select the IP in the pool of IP addresses as source ip for each connection
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
ipfire user https://community.ipfire.org/t/can-the-ipfire-support-bi-directional-nat/11645 expressed similar request, bpfire with loxilb could meet this requirement with eBPF technology instead of traditional netfilter SNAT/DNAT.
The text was updated successfully, but these errors were encountered: