|
> I assume this is LVS-NAT.
Yes.
> Are you prepared to have your program ssh to the director, which
> has all the info (IPs, ports), which you'll have to parse out etc
> after looking at the connections on the RIP.
Yuck!
I was hoping that the VIP would be somewhere in the TCP packet for me to
pull out. If not, sshing to the director won't scale. Any other ideas?
Here is my utlimate goal. My director has many VIPs on it. The program
running on the realserver is a POP server. I want to do a lookup on the VIP
to get the domainname that a user is connecting to and append that
domainname to the end of the username if it isn't supplied. Currently I
have one POP server listening for each domainname that is on the system.
Each pop server knows it's own domainname so it can append it to the
username if it isn't supplied. But this is beggining not scale well itself,
as we add more domains we need to start another popserver running on it's
own virtual interface on each realserver. I figured that if I could pull
the VIP out, I could do a reverse lookup on that and get the domain, thus I
would only need one pop server running on each realserver.
|
