netdev - Re: IPV4 TCP connection reset using iperf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 18 Jan 2013 09:43:16 +0530
From:	Madhvapathi Sriram <sriram.madhvapathi@...il.com>
To:	Rick Jones <rick.jones2@...com>
Cc:	netdev@...r.kernel.org
Subject: Re: IPV4 TCP connection reset using iperf

Hi,
I was looking into the driver code and found that the problem was with
merging the code and had messed up with skb_put in the receive path. I
have corrected that and everything works fine.
Thanks for the help.

Regards,
Madhvapathi Sriram

On Tue, Jan 8, 2013 at 11:09 PM, Rick Jones <rick.jones2@...com> wrote:
> On 01/08/2013 06:41 AM, Madhvapathi Sriram wrote:
>>
>> Hi,
>>
>> I have recently migrated to kernel version 3.6.10 from 3.2.1. I was
>> running iperf to routinely measure TCP throughput and I have been
>> facing problems eversince. I am using a wireless interface.
>>
>> wireless client: iperf -s -i 1 -w 1024K
>> wireless server: iperf -c 192.168.1.1 -i -1 -w 1024 -t 600
>>
>> While, the connection is maintained for sometime and the perf logs
>> keep going. Randomly, the connection breaks with the server side
>> resetting the connection. The tcp dump on the client shows RST sent by
>> the server. Switching back to 3.2.1 works. This issue starts from
>> kernel version 3.5 onnwards.
>>
>> I have tried to probe along some points to take a look at the air
>> logs, tcpdump on either sides but to no clue - everything seems normal
>> like, the tcp window values, very less/negligible retransmissions and
>> so on. The RST is set abruptly and randomly (no definite time - may
>> happen randomly).
>>
>> I am looking for some suggestions or pointers towards analyzing the issue.
>
>
> I cannot imagine that iperf bulk transfer would look all that much different
> from netperf bulk transfer, but I suppose you could see if a netperf
> TCP_STREAM test with similar configuration settings encounters the same RST
> issues.  Or, for that matter, an equally long-lived FTP or scp transfer.
>
> rick jones
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html