From owner-freebsd-current Tue Nov 17 02:03:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17954 for freebsd-current-outgoing; Tue, 17 Nov 1998 02:03:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17920 for ; Tue, 17 Nov 1998 02:02:52 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru (8.9.1a.NOMIME/8.9.1) with ESMTP id NAA03779 for ; Tue, 17 Nov 1998 13:02:13 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Tue, 17 Nov 1998 13:02:12 +0300 (MSK) From: "Roman V. Palagin" To: current@FreeBSD.ORG Subject: Inconsistency in udp_var.h and ip_var.h 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 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? ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message