|
Hello,
On Fri, 19 Oct 2001, Scheunemann, Kevin wrote:
> This is the debug message that I got when the person tried to connect.
>
> Oct 19 14:12:09 redir kernel: IPVS: look/in TCP
> 209.223.234.21:2547->209.150.197.150:80 not hit
> Oct 19 14:12:09 redir kernel: IPVS: Bind-masq fwd:R s:NONE
> c:209.223.234.21:2547 v:209.150.197.150:80 d:209.150.197.153:80
> flg:470100 cnt:4 destcnt:2
> Oct 19 14:12:09 redir kernel: IPVS: Schedule masq fwd:R s:NONE
> c:209.223.234.21:2547 v:209.150.197.150:80 d:209.150.197.153:80
> flg:470100 cnt:4
> Oct 19 14:12:09 redir kernel: IPVS: Set-state masq fwd:R s:NONE
> c:209.223.234.21:2547 v:209.150.197.150:80 d:209.150.197.153:80
> flg:470100 cnt:4
> Oct 19 14:12:12 redir kernel: IPVS: look/in TCP
> 209.223.234.21:2547->209.150.197.150:80 hit
> Oct 19 14:12:18 redir kernel: IPVS: look/in TCP
> 209.223.234.21:2547->209.150.197.150:80 hit
> Oct 19 14:13:19 redir kernel: IPVS: Unbind-masq fwd:R s:SYN_RECV
> c:209.223.234.21:2547 v:209.150.197.150:80 d:209.150.197.153:80
> flg:470000 cnt:1 destcnt:2
Can we assume you don't see these packets from director to
real server with tcpdump running on director. Can you provide tcpdump
for the in and out devices in director? Can the real servers' OS be
a problem (not ECN aware, for example)?
> Kevin,
Regards
--
Julian Anastasov <ja@xxxxxx>
|
