X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed; reply-type=original
Message-id: <31C7318849A24F8390A11960BF755036@dev.null>
From: Gisle Vanem <gvanem AT broadpark DOT no>
To: djgpp AT delorie DOT com
Cc: sezeroz AT gmail DOT com
References: <201301131923 DOT r0DJNA3A013357 AT delorie DOT com>
 <EDE35F6A6122464DB54FFEEAB001DC47 AT dev DOT null>
 <CAA2C=vABHG3-ZBAV5UZtzC2=pDs5HFmACSzmrihm4SS7Nd5Y7w AT mail DOT gmail DOT com>
Subject: Re: ANNOUNCE: tcp/ip library Watt-32 (version 2.2 dev-rel. 10)
 compiled with DJGPP.
Date: Wed, 16 Jan 2013 14:10:33 +0100
X-Priority: 3
X-MSMail-priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Reply-To: djgpp AT delorie DOT com

"Ozkan Sezer" <sezeroz AT gmail DOT com> wrote:

> Is the packet reassembly fixed in the new version? I am
> much interested in that.

No, but it's on my TODO list and I'd be happy to get some help 
with this. Would you be willing to have a look at my latest version
and test it etc.? 

I've searched many different implementations & algorithms for the
best IP-defragmentations. Most of them requires lots of malloc() 
at run-time. This is big no-no on low-mem systems DOS (esp. 16-bit). 
Prone to DoS attacks too.

Your Hexen (?) game-program must be the only program I'm aware of that
*requires* IP-fragments. Can it really not use TCP streams or UDP packetized 
traffic like other well behaved programs? 

--gv