So I've noticed that if I connect to a tcp port on a VIP that has no
ipvs rules defined for forwarding, I 'fall through' to any potential
listening service on my director.
Is this expected behavior? How can I get rid of it?
For my deployment, I run the director and services on the director (e.g.
ssh for my administration of the director), but I don't control the port
forwarding configurations, or the realservers's configuration on the
back end. e.g. one day this week we may have forwarding rules for ssh
to some realservers, and the next day, no rules. The port forwarding
configurations are automatically generated based on
end-user/realserver-user input and can change "at will", and there are a
large number sets of realservers/vips.
Am I misconfigured? Is there an easy way to stop this behavior?
This email message is intended for the use of the person to whom it has been
sent, and may contain information that is confidential or legally protected. If
you are not the intended recipient or have received this message in error, you
are not authorized to copy, distribute, or otherwise use this message or its
attachments. Please notify the sender immediately by return e-mail and
permanently delete this message and any attachments. Verio, Inc. makes no
warranty that this email is error or virus free. Thank you.
Please read the documentation before posting - it's available at:
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users