|
Client A ------------------- LoadBalancer ---------------------
RealServer
192.168.10.100 192.168.10.1 192.168.5.1 |
192.168.5.100
(Outside) (Inside) |
|
|-------- Client B
192.168.5.105
When Client A connects to the LoadBalancer's outside address,
192.168.10.1, LVS-NAT redirects the packets to the RealServer at
192.168.5.100, and everything works great!
However, when Client B attempts to connect using the LoadBlancer's
external address, the connection to the RealServer fails. Unfortunately,
for reasons it would take too long to explain, having Client B connect
directly to the RealServer is not an option. It has to go through the
load balancer.
Is there a way to make LVS handle this scenario?
--
Eric Robinson
Director of Information Technology
Physician Select Management, LLC
775.720.2082
Disclaimer - October 12, 2007
This email and any files transmitted with it are confidential and
intended solely for lvs-users@xxxxxxxxxxxxxxxxxxxxxxx If you are not the
named addressee you should not disseminate, distribute, copy or alter
this email. Any views or opinions presented in this email are solely
those of the author. Warning: Although the message sender has taken
reasonable precautions to ensure no viruses are present in this email,
neither Physician Select Management nor Physician's Managed Care can
accept responsibility for any loss or damage arising from the use of
this email or attachments.
|
