Hi, I am running website regression tests and sometimes see connection resets as a consequence of premature port reuse. Most of the time, happens after the 200th to 400th connection to the same destination.
I'm on snv_134, connections over iwk r...@haggis:~# ndd /dev/tcp tcp_time_wait_interval 60000 Does anyone have any pointers or advise? ## First http connection on the port is fine haggis:/var/tmp$ snoop -V -i /var/tmp/v.snoop port 61299 | sed -e ... -e ... | egrep 'IP D| TCP ' 1 0.00000 192.168.178.116 -> WEBSITE IP D=IP S=192.168.178.116 LEN=64, ID=33579, TOS=0x0, TTL=64 1 0.00000 192.168.178.116 -> WEBSITE TCP D=80 S=61299 Syn Seq=3266796870 Len=0 Win=64240 Options=<mss 1460,nop,nop,tstamp 4722460 0,nop,wscale 1,nop,nop,sackOK> 2 0.01770 WEBSITE -> 192.168.178.116 IP D=192.168.178.116 S=IP LEN=44, ID=23932, TOS=0x0, TTL=55 2 0.01770 WEBSITE -> 192.168.178.116 TCP D=61299 S=80 Syn Ack=3266796871 Seq=3970989964 Len=0 Win=49420 Options=<mss 1452> 3 0.00003 192.168.178.116 -> WEBSITE IP D=IP S=192.168.178.116 LEN=40, ID=33580, TOS=0x0, TTL=64 3 0.00003 192.168.178.116 -> WEBSITE TCP D=80 S=61299 Ack=3970989965 Seq=3266796871 Len=0 Win=65340 4 0.00045 192.168.178.116 -> WEBSITE IP D=IP S=192.168.178.116 LEN=280, ID=33581, TOS=0x0, TTL=64 4 0.00045 192.168.178.116 -> WEBSITE TCP D=80 S=61299 Push Ack=3970989965 Seq=3266796871 Len=240 Win=65340 5 0.01760 WEBSITE -> 192.168.178.116 IP D=192.168.178.116 S=IP LEN=40, ID=23933, TOS=0x0, TTL=55 5 0.01760 WEBSITE -> 192.168.178.116 TCP D=61299 S=80 Ack=3266797111 Seq=3970989965 Len=0 Win=49420 6 0.00058 WEBSITE -> 192.168.178.116 IP D=192.168.178.116 S=IP LEN=253, ID=23934, TOS=0x0, TTL=55 6 0.00058 WEBSITE -> 192.168.178.116 TCP D=61299 S=80 Push Ack=3266797111 Seq=3970989965 Len=213 Win=49420 7 0.00002 192.168.178.116 -> WEBSITE IP D=IP S=192.168.178.116 LEN=40, ID=33582, TOS=0x0, TTL=64 7 0.00002 192.168.178.116 -> WEBSITE TCP D=80 S=61299 Ack=3970990178 Seq=3266797111 Len=0 Win=65340 8 0.00028 WEBSITE -> 192.168.178.116 IP D=192.168.178.116 S=IP LEN=58, ID=23935, TOS=0x0, TTL=55 8 0.00028 WEBSITE -> 192.168.178.116 TCP D=61299 S=80 Fin Push Ack=3266797111 Seq=3970990178 Len=18 Win=49420 9 0.00001 192.168.178.116 -> WEBSITE IP D=IP S=192.168.178.116 LEN=40, ID=33583, TOS=0x0, TTL=64 9 0.00001 192.168.178.116 -> WEBSITE TCP D=80 S=61299 Ack=3970990197 Seq=3266797111 Len=0 Win=65340 10 0.00057 192.168.178.116 -> WEBSITE IP D=IP S=192.168.178.116 LEN=40, ID=33584, TOS=0x0, TTL=64 10 0.00057 192.168.178.116 -> WEBSITE TCP D=80 S=61299 Fin Ack=3970990197 Seq=3266797111 Len=0 Win=65340 11 0.01670 WEBSITE -> 192.168.178.116 IP D=192.168.178.116 S=IP LEN=40, ID=23936, TOS=0x0, TTL=55 11 0.01670 WEBSITE -> 192.168.178.116 TCP D=61299 S=80 Ack=3266797112 Seq=3970990197 Len=0 Win=49420 ## tcp port reused after 9.16 seconds: 12 9.16063 192.168.178.116 -> WEBSITE IP D=IP S=192.168.178.116 LEN=64, ID=35071, TOS=0x0, TTL=64 12 9.16063 192.168.178.116 -> WEBSITE TCP D=80 S=61299 Syn Seq=3289434026 Len=0 Win=64240 Options=<mss 1460,nop,nop,tstamp 4723381 0,nop,wscale 1,nop,nop,sackOK> # destination acks some weird sequence number (could be generated by a firewall) 13 0.01702 WEBSITE -> 192.168.178.116 IP D=192.168.178.116 S=IP LEN=40, ID=25796, TOS=0x0, TTL=55 13 0.01702 WEBSITE -> 192.168.178.116 TCP D=61299 S=80 Ack=1011510153 Seq=783566464 Len=0 Win=49420 # client sends RST 14 0.00006 192.168.178.116 -> WEBSITE IP D=IP S=192.168.178.116 LEN=40, ID=35072, TOS=0x0, TTL=64 14 0.00006 192.168.178.116 -> WEBSITE TCP D=80 S=61299 Rst Seq=1011510153 Len=0 Win=64240 15 0.43343 192.168.178.116 -> WEBSITE IP D=IP S=192.168.178.116 LEN=64, ID=35073, TOS=0x0, TTL=64 15 0.43343 192.168.178.116 -> WEBSITE TCP D=80 S=61299 Syn Seq=3289434026 Len=0 Win=64240 Options=<mss 1460,nop,nop,tstamp 4723427 0,nop,wscale 1,nop,nop,sackOK> 16 0.01597 WEBSITE -> 192.168.178.116 IP D=192.168.178.116 S=IP LEN=64, ID=35073, TOS=0x0, TTL=46 16 0.01597 WEBSITE -> 192.168.178.116 TCP D=61299 S=80 Rst Ack=3289434027 Win=64240 Options=<mss 1452,nop,nop,tstamp 4723427 0,nop,wscale 1,nop,nop,sackOK> _______________________________________________ networking-discuss mailing list [email protected]
