Bug 76674

Summary: FreeBSD 5.3 not returning ack when talking with windows 2003 server (seems to happen with other versions too)
Product: Base System Reporter: Alexandre NERAT <gz>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 5.3-RELEASE   
Hardware: Any   
OS: Any   

Description Alexandre NERAT 2005-01-25 18:40:30 UTC
The background: I have a FreeBSD 5.3-release with a samba on it. When doing a 'big' transfer, the tcp connection seems to be screwed up at one time.
First, I noticed it happen when FreeBSD echoed the first "sack 2", but when turning net.inet.tcp.sack.enable to 0, the problem still appeared (insted, FreeBSD just sent normal acks).

It may come from packet data and tcp routine, since I noticed the same kind of problem in the past (I couldn't transfer a file, either with samba or ftp).

Here is some extract of the tcpdump:
18:22:54.320915 IP 10.0.0.3.445 > 10.0.100.143.3284: . ack 2192789 win 65535
18:22:54.320932 IP 10.0.0.3.445 > 10.0.100.143.3284: . ack 2192789 win 65535
18:22:54.688850 IP 10.0.100.143.3284 > 10.0.0.3.445: . 2192789:2194249(1460) ack 49770 win 17367
18:22:55.438829 IP 10.0.100.143.3284 > 10.0.0.3.445: . 2192789:2194249(1460) ack 49770 win 17367
18:22:57.079427 IP 10.0.100.143.3284 > 10.0.0.3.445: . 2192789:2194249(1460) ack 49770 win 17367
18:23:00.251249 IP 10.0.100.143.3284 > 10.0.0.3.445: . 2192789:2194249(1460) ack 49770 win 17367
18:23:06.594879 IP 10.0.100.143.3284 > 10.0.0.3.445: . 2192789:2194249(1460) ack 49770 win 17367
-> and then the tcp connection disappears from windows 2003 (which is 10.0.100.143), but still remains 'ESTABLISHED' on FreeBSD (10.0.0.3).

I have tcpdump capture file if you want, but it's more than 4Mb, so I prefer have you to ask it if you need it.. ;)

Anyway, thank you for developping and supporting my favorite OS ;)

How-To-Repeat: I can repeat it by launching the transfer.
Comment 1 Alexandre NERAT 2005-01-26 13:51:46 UTC
Hi,

You can discard this report, actually it was an old hp procurve
switch that screwed some specific packets.

Sorry for the inconvenience..

----- Original Message ----- 
From: <FreeBSD-gnats-submit@FreeBSD.org>
To: "Alexandre NERAT" <gz@poliris.com>
Sent: Tuesday, January 25, 2005 7:40 PM
Subject: Re: kern/76674: FreeBSD 5.3 not returning ack when talking with
windows 2003 server (seems to happen with other versions too)


> Thank you very much for your problem report.
> It has the internal identification `kern/76674'.
> The individual assigned to look at your
> report is: freebsd-bugs.
>
> You can access the state of your problem report at any time
> via this link:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=76674
>
> >Category:       kern
> >Responsible:    freebsd-bugs
> >Synopsis:       FreeBSD 5.3 not returning ack when talking with windows
2003 server (seems to happen with other versions too)
> >Arrival-Date:   Tue Jan 25 18:40:30 GMT 2005
>
Comment 2 Maxim Konovalov freebsd_committer freebsd_triage 2005-01-26 14:33:33 UTC
State Changed
From-To: open->closed

Closed at the submitter's request.