From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <a69de218aae6262a9394aa7b3913284e@coraid.com>
References: <a69de218aae6262a9394aa7b3913284e@coraid.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0A927737-4E25-11D9-901F-00112430C042@gmail.com>
Content-Transfer-Encoding: 7bit
From: jim <jim.whitson@gmail.com>
Subject: Re: [9fans] (no subject)
Date: Tue, 14 Dec 2004 23:08:18 +0000
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Topicbox-Message-UUID: 163deb76-eace-11e9-9e20-41e7f4b1d025


On 14 Dec 2004, at 22:50, Brantley Coile wrote:

>> I'd love to
>> know how real coders do tcp/ip headers :-S.
>
>> From my netometer project
>
> typedef struct TCP TCP;
> struct	TCP	{
> 	short	src;
> 	short	dest;
> 	ulong	seq;
> 	ulong	ack;
> 	ushort	flags;	/* and header length */
> 	ushort	wnd;
> 	ushort	chksum;
> 	ushort	urgptr;
> 	ulong	options;
> };
>

Looks much like how mortals do it... I thought from what some posters 
have
said that there was some crazy way to deal with tcp that didn't involve 
struct
juggling...