|
pb wrote:
>
> > I don't know if this is a problem: what happens if a
> > client
> > gets a different address for the server in the
> > middle of a connection?
>
> I'm assuming whichever director the packet sneaks
> into, will route out and returns???
Hmm, I don't think my scenario is going to happen.
I was thinking if the client got a new IP for the
LVS in the middle of a tcp session (which may only
be seconds long). However once you have the tcp session,
you already have the IP and you won't be asking DNS
for IPs after that.
> Well, I thought about putting 2 NICs in each Real
> Server, and each
> /etc/sysconfig/network-scripts/ifcfg-ethX script lets
> you put a different gateway, but the
> /etc/sysconfig/network configuration file has the
> DEFAULT GATEWAY... so I am assuming there is no way to
> work around all this? Any thoughts on this???
^^^^
I still don't know what this is.
You can have multiple default gw (according to the tcpip
spec). You can't do it with route, but you can probably
do it with iproute2. But I don't think this is your problem.
> > > Direct Routing work yet, without having to apply
> > some
> > > patch??? Specificially Red Hat kernels?
> >
> > on the director or the realservers?
>
> Well, in this case, on the Linux directors, because
> the Real Servers would be stripped-down FreeBSD (aka.
> MOS).
When you patch with ip_vs you get all forwarders if this
is what you mean
Joe
--
Joseph Mack PhD, Senior Systems Engineer, SAIC contractor
to the National Environmental Supercomputer Center,
ph# 919-541-0007, RTP, NC, USA. mailto:mack.joseph@xxxxxxx
|
