linux-kernel - Re: Bug? Kernels 2.6.2x drops TCP packets over wireless (independent of card used)

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 Feb 2008 08:17:51 -0800
From:	Stephen Hemminger <shemminger@...ux-foundation.org>
To:	Marcin Koziej <marcinkoziej@...pl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Bug? Kernels 2.6.2x drops TCP packets over wireless
 (independent of card used)

On Thu, 07 Feb 2008 10:04:00 +0100
Marcin Koziej  <marcinkoziej@...pl> wrote:

> 
> Hello, I have problem with wireless network connectivity;
> I have tested this on two wireless cards, both giving same results:
> These are:
> 1) 02:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
> working under madwifi-0.9.3.3
> 2) 00:0a.0 Ethernet controller: Linksys, A Division of Cisco Systems [AirConn] INPROCOMM IPN 2220 Wireless LAN Adapter (rev 01)
> working under ndiswrapper on neti2220 driver
> 
> On kernel 2.6.19 both cards are working fine (with same network configuration)
> 
> Problems arise on kernels 2.6.2x, information below is from 2.6.23, but 2.6.24-rc8-git7 also was tested:
> Both cards can associate with ap, and get TCP/IP configuration from the router.
> Both cards can ping the router (0% packet loss), resolve hostnames using DNS (suggesting UDP is working fine).
> However, when any kind of TCP connection is made, it hangs after initial handshake and maybe some ammount of data interchanged. This is checked by tcpdump provided below.
> 
> This happens every time to all tcp connections.
> 

You have the wrong mailing list:

1. You are using proprietary drivers (ndiswrapper and madwifi both have binary only parts).
2. The network developers read netdev@...r.kernel.org

Sounds like you have a TCP corrupting firewall that mangles the window scaling.
This is a known issue with buggy middleboxes that can not be fixed in Linux without
limiting performance.  Complain to the middlebox vendors or IETF.

-- 
Stephen Hemminger <stephen.hemminger@...tta.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/