From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <d82982ea633d663fe7e528f285444d61@plan9.bell-labs.com>
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] udp headers
In-Reply-To: <7aad5668c13282235e072f0ddbf9f063@9fs.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Apr 2003 08:24:32 -0400
Topicbox-Message-UUID: 9280fe42-eacb-11e9-9e20-41e7f4b1d025

My first reaction is to just change the definition of Udphdr and
Udphdrsize and get everyone to recompile everything.  While I'm
at it maybe I should toss in whatever else people want to see:

typedef struct Udphdr Udphdr;
struct Udphdr
{
	uchar	raddr[IPaddrlen];	/* remote address */
	uchar	laddr[IPaddrlen];	/* local address */
	uchar	rport[2];
	uchar	lport[2];
	uchar	oaddr[IPaddrlen];	/* original dest address */
	uchar	tos;
	uchar	ttl;
};

I would prefer this than some intermediate solution where we
have two different header types until everyone is using the
new one.  I'm still regreting the headers4 control message
(which I just noticed happens to have a bug in the one place
its used).  While I'm at it, I'll nuke headers4.

Comments?  Anyone mind if I break udp headers?  I'll update
everything on sources but you'll have to take care of your own
programs.