X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:x-received:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=AybOzIjQ7lDAlK62FSa2+3IKwdBa2j0C832QLz4rImk=;
	b=qryBj11rXOKwOB5P7FkeWKsBB6FF0WIHEsRQ6pLOBzVg64v0wRw/rI8rca6KRnS4fq
	3tHvJpy4oeeYaKV0OpA/FTLZzzczkFoSO6/W7ToOfEoEeIPkc9Q9rcud7PJ1Qj2wei/9
	/Ip7tetTFgDtE0d1m6qQkVBHXEnz87nQY9INv+7tdtfE0mEzCifUdf+6/ybJAmQ0HIZB
	TpRHAadw99FtuY/o7MarJGxVlC0waS8FOSgQsMjcmzXT7EieKQXq+INRntrK1elW9hLV
	nIUumYbDcbTM/lRl50cbDPjaVUxM9mSaR0EoQhG87FzlLVGO+nAQq0O03ObWSVlp1jmc
	BWqg==
MIME-Version:	1.0
X-Received:	by 10.68.241.103 with SMTP id wh7mr3016209pbc.153.1358345871970;
	Wed, 16 Jan 2013 06:17:51 -0800 (PST)
In-Reply-To:	<31C7318849A24F8390A11960BF755036@dev.null>
References:	<201301131923 DOT r0DJNA3A013357 AT delorie DOT com>
	<EDE35F6A6122464DB54FFEEAB001DC47 AT dev DOT null>
	<CAA2C=vABHG3-ZBAV5UZtzC2=pDs5HFmACSzmrihm4SS7Nd5Y7w AT mail DOT gmail DOT com>
	<31C7318849A24F8390A11960BF755036 AT dev DOT null>
Date:	Wed, 16 Jan 2013 16:17:51 +0200
Message-ID:	<CAA2C=vD6g-ZQJr2Hm61SVzQ=f6AP7_6-WmRdzS+2O5_SnC+VAg@mail.gmail.com>
Subject:	Re: ANNOUNCE: tcp/ip library Watt-32 (version 2.2 dev-rel. 10)
	compiled with DJGPP.
From:	Ozkan Sezer <sezeroz AT gmail DOT com>
To:	djgpp AT delorie DOT com
Cc:	Gisle Vanem <gvanem AT broadpark DOT no>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 1/16/13, Gisle Vanem <gvanem AT broadpark DOT no> wrote:
> "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.?
>

Certainly.

> 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?

Of course I can change it to not cause frags, but doing that will break
backwards compatibility due to protocol changes.  The thing is an just
old game and what I am doing with it is just porting and maintaining it
with maximum compatibility.

>
> --gv
>
>

- Raw text -