Adam ,
Thanks,
Ok, if you cant see the SYN/ACK from 10.56.233.99, it could be;
- if the box is multi-homed the SYN/ACK may be being routed out a different
interface
- the traffic may be being dropped by iptables (which sits between tcpdump
and the OS)
I have only one network interface in
Thanks a lot for your response .
I used sniffer tool to catch the packet in both Poly graph Server
(10.56.233.99) and Squid server side (198.18.24.3).
I could see 198.18.24.3 send out SYNs, they SYNs were also could be
captured in PolyServer(10.56.233.99) side , but no ack were genenated
by
Henrik , and all ,
Do you guys think the issue I met was caused by multiplesquid
intanstance NAT traverse problem ?
I am using Squid 2.6 Stable 19
Thanks,
-Arkin
On Fri, Jul 25, 2008 at 3:24 PM, Arkin Y [EMAIL PROTECTED] wrote:
Adam ,
Thanks a lot for your response .
I used sniffer tool to
Adam ,
Thanks a lot for your response .
I used sniffer tool to catch the packet in both Poly graph Server
(10.56.233.99) and Squid server side (198.18.24.3).
I could see 198.18.24.3 send out SYNs, they SYNs were also could be
captured in PolyServer(10.56.233.99) side , but no ack were genenated
Hey ,Guys
We met a performance issue when Squid working with NAT ...
Thanks in advance for your attention.
There are two squid servers, Squid1 and Squid 2.
And We use web polygraph to do the performance test. So there are
another two servers, PolyClient and PolyServer.
Firstly, the 4
part of netstat -na in squid2 output like following:
tcp0 1 198.18.24.3:46304 10.56.233.99:
SYN_SENT
This shows that 198.18.24.3 cant communication with 10.56.233.99, so assuming
no firewalling, you have a routing problem (which could be a NAT problem). Run
