|
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
On Thu, Mar 29, 2012 at 11:25 PM, Enno Gröper <enno+lvs@xxxxxxxxxxxxxxxxx>wrote:
> Hi,
>
> Am 29.03.2012 15:31, schrieb Reet Vyas:
> > cause this is external ip of server eth0: 122.166.233.133 and eth0:1 has
> > 122.166.233.136 (VIP) my ipvsadm -l -n
> You should be able to reach your server from extern using the VIP.
> It's simply an additional IP.
>
>
> > TCP 122.166.233.136:5000 rr
> > TCP 122.166.233.137:5001 rr
> > TCP 122.166.233.138:80 rr
> > -> 192.168.3.3:80 Masq 1 0 0
> > TCP 122.166.233.139:5004 rr
> This looks completely broken.
> I suppose piranha has generated this. But I really don't know why.
> I reckon piranha is configured wrong.
>
> Is this the complete output?
> There are 4 virtual services:
> TCP 122.166.233.136:5000
> TCP 122.166.233.137:5001
> TCP 122.166.233.138:80
> TCP 122.166.233.139:5004
>
> Only one (.138) has real servers configured.
> Since you try to connect to 122.166.233.133:5004 and there is no LVS
> service configured for this, it simply can't work.
>
>
> 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.
>
> HTH,
> Enno
>
>
> _______________________________________________
> 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
>
_______________________________________________
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
|
