From owner-freebsd-current Tue Nov 17 02:59:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23843 for freebsd-current-outgoing; Tue, 17 Nov 1998 02:59:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23838 for ; Tue, 17 Nov 1998 02:59:32 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA05238; Tue, 17 Nov 1998 10:52:44 GMT Date: Tue, 17 Nov 1998 10:52:44 +0000 (GMT) From: Doug Rabson To: "Roman V. Palagin" cc: current@FreeBSD.ORG Subject: Re: Inconsistency in udp_var.h and ip_var.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Roman V. Palagin wrote: > hello! > > just found this kind of error in -current (cvsup'd about hour ago): > > in udp_var.h: > > struct udpiphdr { > struct ipovly ui_i; /* overlaid ip structure */ > struct udphdr ui_u; /* udp header */ > }; > #define ui_next ui_i.ih_next > #define ui_prev ui_i.ih_prev > > in ip_var.h: > > struct ipovly { > u_char ih_x1[9]; /* (unused) */ > u_char ih_pr; /* protocol */ > u_short ih_len; /* protocol length */ > struct in_addr ih_src; /* source internet address */ > struct in_addr ih_dst; /* destination internet address */ > }; > > as you can see, there is no ih_next and ih_prev members in ipovly. should > ui_next and ui_prev go away? Yes they should. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message