|
I think, You are right, but what can I do ?
First I tried port mapping within the director. It is not working.
Mapping of the IP-address is also not working.
I wanted to run the same application several times within the director and
use the loadbalancing.
Harald Sammer
-----Ursprüngliche Nachricht-----
Von: Horms [mailto:horms@xxxxxxxxxxxx]
Gesendet: Dienstag, 4. März 2003 05:40
An: LinuxVirtualServer.org users mailing list.
Betreff: Re: Port Mapping
On Mon, Mar 03, 2003 at 03:40:03PM +0100, Harald Sammer wrote:
> The output after one try is:
>
> IP Virtual Server version 1.0.6 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> Remote Address:Port Forward Weight ActiveConn InActConn
> TCP <official IP address>:5000 rr persistent 30
> -> 192.168.0.1:5000 Local 1 0
> 1
Ok, from memory, this is what is going to happen.
The connection will come in for <official IP address>.
LVS will pick this up and send it to the real
sever 192.168.0.1. As that is a local IP address, it will just
be sent directly to the local port without any modification.
That is, the destination IP address will still be
<official IP address>, not 192.168.0.1. So I am guessing
that an application that is only bound to 192.168.0.1 will
not get this connection.
--
Horms
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
