|
Hello,
On Fri, 21 Sep 2001, Dmitry Dan Brovkovich wrote:
> Hi,
>
> Ok that's what I thought, and I think that I've done that but I can't
> telnet
> into the cluster (aka telnet into the director). I've got some tcpdump
> output, I hope it'll be useful:
It is not useful for me. Look, I spent more time than you on
writing email :) Still nobody knows your IP addresses and LVS setup. I
don't know what you are testing. Please, tell us what are the values
for CIP, DIP, VIP and RIP, your 'ipvsadm -Ln' output (I don't need
the name of your real server). Then the outputs from:
director# tcpdump -ln host CIP
realserver# tcpdump -ln host CIP
try to run it on many devices (-i DEVNAME) if you have more
> >From the director to the real server:
Seen on the director or on the real server?
> 12:32:10.046938 172.16.1.2 > 172.16.1.3: icmp: redirect 172.16.1.1 to host
> 172.16.1.1 [tos 0xc0]
Hm, may be these errors are not related to LVS
> >From the director to the client:
This is a wrong direction, the director does not talk with
the client (for the LVS-DR traffic).
> 12:30:10.365644 172.16.1.3.1041 > 172.16.1.1.23: S 86960724:86960724(0) win
> 8192 <mss 1460> (DF)
> Where will it be getting the IP 172.16.1.23 from? I can't remember ever
> entering it in.
It is 172.16.1.1 with port 23.
> Any suggestions?
No more, just the previous ones:
- the traffic from the rs to the client should not go through the
director
- the real server must listen to VIP:23 and VIP must be hidden there,
try:
realserver# telnet VIP
It should work
Regards
--
Julian Anastasov <ja@xxxxxx>
|
