[lvs-users] Natting Issue
enno+lvs at groeper-berlin.de
Thu Mar 29 18:55:54 BST 2012
Am 29.03.2012 15:31, schrieb Reet Vyas:
> cause this is external ip of server eth0: 188.8.131.52 and eth0:1 has
> 184.108.40.206 (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 220.127.116.11:5000 rr
> TCP 18.104.22.168:5001 rr
> TCP 22.214.171.124:80 rr
> -> 192.168.3.3:80 Masq 1 0 0
> TCP 126.96.36.199: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:
Only one (.138) has real servers configured.
Since you try to connect to 188.8.131.52:5004 and there is no LVS
service configured for this, it simply can't work.
If you let your client connect to 184.108.40.206:5004, it should look like:
TCP 220.127.116.11: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
18.104.22.168: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.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://lists.graemef.net/pipermail/lvs-users/attachments/20120329/328ff66f/attachment-0001.bin
More information about the lvs-users