netdev - Re: TCP packet size and delivery packet decisions

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]

Message-Id: <20100906.223010.173858342.davem@davemloft.net>
Date:	Mon, 06 Sep 2010 22:30:10 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	leandroal@...il.com
Cc:	eric.dumazet@...il.com, netdev@...r.kernel.org
Subject: Re: TCP packet size and delivery packet decisions

From: ツ Leandro Melo de Sales <leandroal@...il.com>
Date: Tue, 7 Sep 2010 02:21:42 -0300

> This is a embedded system implemented in a proprietary hardware that I
> can send TCP commands to turn on/off relays. It will be very difficult
> to find the reason for this behaviour. Since it needs to receive very
> small data, probably it is not necessary to scaling window.

The small 78 byte window is why the sending system is splitting up the
writes into smaller pieces.

I presume that the system advertises exactly a 78 byte window because
this is how large the commands are.  But this is an extremely foolish
and baroque thing to do, and it's why you are having problems.
--
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