LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Tcpdump output

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Tcpdump output
From: Roberto Nibali <ratz@xxxxxxxxxxxx>
Date: Mon, 14 Jan 2002 11:01:11 +0100
Hello,

Maybe I've missed previous postings of yours but I've been out of
business for several months.

> I know I've been whinging a lot lately, but its really because I'm not
> 100% sure of the working mechanisms of LVS, I've read the
> documentation, but I'm still a little uncertain.

Which part is difficult for you to understand? Don't get me wrong here,
I just want to improve our documentation.

> IP Virtual Server version 0.9.5 (size=4096) Prot LocalAddress:Port
> Scheduler Flags -> RemoteAddress:Port           Forward Weight
> ActiveConn InActConn TCP  196.36.239.60:21 rr persistent 10 ->
> 128.1.30.2:21                Route   1      0          0 ->
> 128.1.30.1:21                Route   1      0          0 TCP
> 196.36.239.60:80 rr -> 128.1.30.2:80                Route   1 0 218 ->
> 128.1.30.1:80                Route   1      0 219

How does your routing on the director box look like. You might use
following scriptlet to give me the output:

ip ru ls | while read rule; do
   set -- $rule
   ip ro show table $(eval echo \$${#*})
done

> now when I do a tcpdump on the load balancer I get this:
>
> # tcpdump -ln port 80 Kernel filter, protocol ALL, TURBO mode (575
                                                     ^^^^^
Is this a RedHat tcpdump? Do you by any chance use a RH kernel?
Btw, also note that tcpdump doesn't always show the packet how it is.
Depending on when tcpdump actually gets a copy of the packet you might
miss packets.

> frames), datagram packet socket tcpdump: listening on all devices
> 10:02:00.396618 eth0 < 196.36.119.175.40157 > 196.36.239.60.www: S
> 117897522:117897522(0) win 4096 <mss 1460,nop,nop,sackOK> (DF)
> 10:02:00.396694 eth0 > 196.36.119.175.40157 > 196.36.239.60.www: S

This could be anything ranging from missing arp-hiding, rp_filter, wrong
routing, missing or 'not corresponding to the interface' ipvsadm entries.

> Surely I should see a redirected packet to the realservers, regardless
> of whether my network setup was right or not? Surely if my network
> setup was wrong, it would just fail? But according to the tcpdump,
> its not even rewriting and forwarding the packet. The thing is that
> if I do straight forward port redirection to the realservers, the

What do you mean when you say you do port redirection? Do you set it up
or do you think the LVS does it? Because the LVS in your setup (LVS-DR) cannot do port forwarding.

> realservers register that they have been hit. If I just use this
> setup the dont register any hits at all.

At the RS?

> My apologies to Joseph, for previously not including my network setup.

Where was the initial thread?

> I have not included again here, because this question is theoretical,
> and shouldnt need my network to be shown to get an answer.

You might be surprised sometimes :)

> Many Thanks.

Cheers,
Roberto Nibali, ratz





<Prev in Thread] Current Thread [Next in Thread>