LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: [lvs-users] Natting Issue

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [lvs-users] Natting Issue
From: Enno Gröper <enno+lvs@xxxxxxxxxxxxxxxxx>
Date: Fri, 30 Mar 2012 20:03:16 +0200
Am 30.03.2012 07:33, schrieb Reet Vyas:
> Ports from 5000 to 5008 are not all http request .As we are implementing
> chat server for this .Below are the details.
> Chat ports :
> 
>    5004: Client Chat Login
> 
>    5005: Client Chat message receiver.
> 
> 
> 
> Broadcast ports:
> 
>   5001: Client message receiver
> 
>   5002: Client updated receiver
> 
>   5003:  Client Message Update receiver.
> 
> 
> 
> File Transfer Ports:
> 
>   5006: File Transfer login.
> 
>   5007: File transfer login.
> 
> 
> 
> Logout:
> 
>  5008: Log out user
> 
> 
> 122.166.233.133 iis my lvs router IP and and 122.166.233.136 is VIp on this
> and for internal n/w on eth1 192.168.3.1 and vip on eth1 is 192.168.3.10 as
> u know my real server ip's . I followed documentation still its broken
> could find any logs can u pls tell me how to check logs or info whats wrng
> with configuration
Sorry. I'm not using piranha and I have no knowledge about it.
If you don't want to configure ipvs directly using ipvsadm, you could
use ldirectord, which is pretty straight forward.
It is configured using a plain text file.

It is obvious what is wrong with your configuration. No logs needed.
You can see what is configured using "ipvsadm -Ln".
I wrote to you in my last email what should be configured for port 5004.
It's pretty simple to make the same configuration for other ports, once
the configuration for port 5004 is correct.


> On Thu, Mar 29, 2012 at 11:25 PM, Enno Gröper 
> <enno+lvs@xxxxxxxxxxxxxxxxx>wrote:
>> If you let your client connect to 122.166.233.133:5004, it should look
>> like:
>> TCP 122.166.233.133:5004 rr
>>  -> 192.168.3.2:5004             Masq    1      0          0
>>  -> 192.168.3.3:5004             Masq    1      0          0
>>
>> This configuration would distribute requests directed to
>> 122.166.233.133:5004 to the services listening on port 5004 on the real
>> servers 192.168.3.2 and 192.168.3.3.
>> Of course you could configure the virtual service to listen on your VIP.
>> But then your client should try to connect to the VIP and not the
>> "external IP"! Both IPs are on the same net. They should work both.

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

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
<Prev in Thread] Current Thread [Next in Thread>