Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site sequel.UUCP Path: utzoo!linus!philabs!cmcl2!floyd!vax135!cornell!uw-beaver!tektronix!ogcvax!sequel!rbk From: rbk@sequel.UUCP Newsgroups: net.unix-wizards Subject: 4.1c Ether Addressing Problem Message-ID: <188@sequel.UUCP> Date: Thu, 23-Jun-83 12:20:48 EDT Article-I.D.: sequel.188 Posted: Thu Jun 23 12:20:48 1983 Date-Received: Mon, 27-Jun-83 21:56:10 EDT Organization: Sequel Computer Systems, Portland Lines: 25 The manual pages for 4.1c ethernet drivers specify that they fill in the 48-bit destination field in the packet with their *own* high-order 3-bytes, and 3-bytes of (low-order) destination address. The sources are consistent with this. This seems to imply that all the ethernet boards in your collection of systems must come from the same manufacturer, unless you have gateway(s). This is an undesireable restriction. Is this an accurate description of the problem? It seems that the inet code uses "struct sockaddr_in" to indicate addresses, and this contains a "struct in_addr" which uses a single (unsigned) long to store the address. There are comments that suggest this is "old style" inter-net addresses. Hence the questions: is this problem going to be fixed in 4.2? If not, does anyone have ideas on how to fix it? My fear is that changes might propogate throughout the TCP/IP code, due to the unusual size of the necessary addresses. -- Bob Beck Sequel Computer Systems ...ogcvax!sequel!rbk (503)627-9809