Now, if I type h ** p in the browser: //192.168.252.199 (http must be removed from the link), I want its call to be redirected to 201 and display the page (if I type and I can access the page 201).
Is there any setting I missed? [ I use sticky sessions, which is why it is mainly on server 2), but the connection is never received.
Its purpose is to deceive the real server by replacing the real client IP address in the request with a KEMP ip address. Therefore, using snat, the real server will pass KEMP instead of directly to the client Send response. If you don’t have other NAT mechanisms upstream of KEMP, you must use snat, because the client will not accept replies from different ips from which it sent the request (for example, if it requests from KEMP but gets a reply directly from the real server ).
You can easily sniff the truth on the real server, for example, if the source IP of the get request is your client IP address instead of the KEMP (snat:ed) address.
I don’t remember what they called the option, but vaguely recalled that it was one of the checkboxes under the network option. A quick look at the configuration guide, it may be “Enable server nat” or “Subnet initiate request”.
I am setting up load balancing through KEMP LoadMaster. I have set up everything and reached the point where the real server starts, the virtual server starts, ping works but http requests cannot pass. < p>
Now, if I type h ** p in the browser: //192.168.252.199 (http must be removed from the link), I want its call to be redirected to 201 and display the page (If I type, I can access this page 201).
Is there any setting I missed? [ I use sticky sessions, which is why it is mainly on server 2), but the connection is never received.
I haven’t fiddled with our KEMP for a while , But vaguely recall the origin of NAT (snat) function is vaguely recorded. Maybe this is what is missing?
Its purpose is to deceive the real server by replacing the real client IP address in the request with a KEMP ip address. Therefore, using snat, the real server will pass KEMP instead of directly to the client Send response. If you don’t have other NAT mechanisms upstream of KEMP, you must use snat, because the client will not accept replies from different ips from which it sent the request (for example, if it requests from KEMP but gets a reply directly from the real server ).
You can easily sniff the truth on the real server, for example, if the source IP of the get request is your client IP address instead of the KEMP (snat:ed) address.
I don’t remember what they called the option, but vaguely recalled that it was one of the checkboxes under the network option. A quick look at the configuration guide, it may be “Enable server nat” or “Subnet initiate request”.