From owner-freebsd-hackers Tue Dec 5 10:39:40 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA25837 for hackers-outgoing; Tue, 5 Dec 1995 10:39:40 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA25824 for ; Tue, 5 Dec 1995 10:39:31 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA02904; Tue, 5 Dec 1995 13:38:59 -0500 Date: Tue, 5 Dec 1995 13:38:59 -0500 From: "Garrett A. Wollman" Message-Id: <9512051838.AA02904@halloran-eldar.lcs.mit.edu> To: Terry Lambert Cc: wollman@lcs.mit.edu (Garrett A. Wollman), hackers@FreeBSD.org Subject: Re: ipx on 802.3 In-Reply-To: <199512051726.KAA01996@phaeton.artisoft.com> References: <9512051629.AA02695@halloran-eldar.lcs.mit.edu> <199512051726.KAA01996@phaeton.artisoft.com> Sender: owner-hackers@FreeBSD.org Precedence: bulk < said: > Once in, another cleanup could be done. The hard part on the 802.3 LLC > is codifying the state table. I've seen companies buy code from Microsoft > and hack COFF objects from MSVC 2.x into something usable by GCC to get > an 802.3 before. Which is just fine, since we already have 99% of what's needed anyway. The original question, which you seem to have never grasped, is: How can you tell an Ethernet interface to use 802.3 encapsulation rather than Ethernet v2? Or, to spell it out more explicitly: How can you tell an Ethernet interface to send an 802.3-style length field and 802.3-style LLC header rather than the two-byte type field specified in Ethernet v2? -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant