Re: Persistance and LVS

To: " users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>, Julian Anastasov <ja@xxxxxx>, Horms <horms@xxxxxxxxxxxx>
Subject: Re: Persistance and LVS
From: Joseph Mack <mack.joseph@xxxxxxx>
Date: Fri, 30 Apr 2004 07:00:16 -0400
Julian Anastasov wrote:
>         Hello,
> On Thu, 29 Apr 2004, Joseph Mack wrote:
> > if you're doing LVS-NAT then you have a smaller limit for
> > ports, since all ports are coming from the director.
> >
> > when NAT'ing you only have ports 61000-65xxx, ie 4000 ports to
> > choose from.
>         These ranges are only for the connections created from
> the 2.2 masquerading code, not for the LVS connections:

I'm not thinking at all clearly. 

With LVS-NAT running a persistent connection virtual service 
(eg VIP:https) all connections will be coming out of the director 
from VIP:https. I was thinking about connections originating 
from boxes NAT'ed behind a NAT router, where the client
connections come from high ports.

In regular (non-lvs) NAT for 2.4, the client (high) ports are no longer
restricted to 61k-64k?

Do the NAT'ed ports collide with ports from connections made by clients
on the NAT-router like they could with 2.2?

Horms wrote

> LVS does not use the source port at all
> in persistance templates. In fact it is set to 0 internally
> so LVS can differentiate between a persistance template and
> a connection entry.

want to explain to me about persistence templates?

Is there a separate structure for a persistence virtual service?


Joseph Mack PhD, High Performance Computing & Scientific Visualization
SAIC, Supporting the EPA Research Triangle Park, NC 919-541-0007
Federal Contact - John B. Smith 919-541-1087 - smith.johnb@xxxxxxx
<Prev in Thread] Current Thread [Next in Thread>