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
{{ message }}
This repository has been archived by the owner on Aug 19, 2020. It is now read-only.
When keepalive is setup to nat to different backends (that can be on different hosts) how does the target host know to properly flip the source ip back to the vip address when replying? From observation the host seems to be directly returning the packets using it's own source address.
Curious if this feature was used for some type of proper Direct Server Return setup?
Thanks.
The text was updated successfully, but these errors were encountered:
keepalived/lvs will not do SNAT, but only DNAT.
you will have to achieve snat by yourself.
example, on the real server node , set the default gateway to the VIP.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When keepalive is setup to nat to different backends (that can be on different hosts) how does the target host know to properly flip the source ip back to the vip address when replying? From observation the host seems to be directly returning the packets using it's own source address.
Curious if this feature was used for some type of proper Direct Server Return setup?
Thanks.
The text was updated successfully, but these errors were encountered: