Quick Solution to the Same Subnet Load balancing problem

26
Mar/10
0

You have a load balancer using ultra monkey which works just fine when you access it from a remote site (different subnet) but it doesn’t work locally. The reason for this is the transparent options where clients IP’s are provided causes the web servers to respond directly. There are a few ways to fix this however my prefered is fairly simple.

Set the IP of the webserver to have a /32 subnet (single IP). Hard code in the route for the default gateway:

route add -host xx.xx.xx.xx dev ethX

and then confirm your default gateway is set and pingable. Now regardless of destination your responses will go via the correct gateway as everything is on a different subnet. Remember this means you now likely can’t directly access the system in other ways (ssh) so I’d suggest having a backup interface on a different subnet to do your normal administration.

Comments (0) Trackbacks (0)

No comments yet.

Leave a comment

No trackbacks yet.