|
Hi all, thanks for all your help in pointing me in the
direction in the past few days/week.
I now have a new problem with LVS-NAT. I still have the same
set-up as before:
1 client, 1 director and 2 real servers:
Client IP = 192.168.1.254
Director OUtside IP = 192.168.1.110
Director Inside IP = 10.1.1.1
Real Server 1 IP = 10.1.1.2
Real Server 2 IP = 10.1.1.3
And I have upgraded the director kernel to 2.2.16, patched
it and compiled the latest ipvsadm. Running Joe's scripts
works, o.k. on the director, but as I don't have a default
gateway for the director, the two real server scripts don't
run properly. I am sure that they are working correctly
though. What I need to know is this:
Do the real servers also have to be kernel 2.2.16?
I was under the impression that they don't, but at the
moment if I try to view pages using my client, the lvs will
only provide two connections to each real server and then
stop responding (If I reload the pages I get nothing, the
browser says the www connection cannot be made, but I can
still ping the machines from the director, and still ping
the director from the client.)
The output of IPVSADM on the director is as follows:
IP Virtual Server 0.9.15 (size=4096)
TCP extdirector.icepicc.co.uk:www wlc
-> real2.server.net:www Masq 1 0 0
-> real1.server.net:www Masq 1 0 0
TCP extdirector.icepicc.co.uk:telnet rr
-> rea1.server.net:telnet Masq 1 0 0
The directors 'route' output is as follows:
CORSICA.icepicc * 255.255.255.255 UH 0 0 0 eth0
extdirector.ice * 255.255.255.255 UH 0 0 0 eth0
director.server * 255.255.255.255 UH 0 0 0 eth0
10.0.0.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
10.1.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
The IP chains output for the director is as follows:
Chain input (Policy ACCEPT)
Chain forward (policy ACCEPT)
MASQ tcp ----- real1.server.net anywhere www -> any
MASQ tcp ----- real2.server.net anywhere www -> any
MASQ tcp ----- real1.server.net anywhere telnet -> any
Chain output (policy ACCEPT)
There is no ipchains output for the real servers.
The route output for the real servers is as follows:
For real 1:
real1.server.ne * 255.255.255.255 UH 0 0 0 eth0
10.1.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 eth0
default director.ser 0.0.0.0 UG 0 0 0 eth0
For real 2:
real2.server.ne * 255.255.255.255 UH 0 0 0 eth0
10.1.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 eth0
default director.ser 0.0.0.0 UG 0 0 0 eth0
Have I missed something?
--------------------
talk21 your FREE portable and private address on the net at
http://www.talk21.com
|
