From owner-freebsd-hackers  Tue Jul 15 10:57:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA13403
          for hackers-outgoing; Tue, 15 Jul 1997 10:57:15 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA13268
          for <hackers@FreeBSD.ORG>; Tue, 15 Jul 1997 10:55:41 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id KAA15135;
	Tue, 15 Jul 1997 10:18:42 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd015133; Tue Jul 15 17:18:39 1997
Message-ID: <33CBB063.237C228A@whistle.com>
Date: Tue, 15 Jul 1997 10:16:19 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: "Serge A. Babkin" <babkin@hq.icb.chel.su>
CC: Michael Smith <msmith@atrad.adelaide.edu.au>, jhay@mikom.csir.co.za,
        hackers@FreeBSD.ORG
Subject: Re: IPX routing?
References: <199707150926.PAA08078@hq.icb.chel.su>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Serge A. Babkin wrote:
> 
> > > I do have code that do the Novel 802.3 protocol, but it only works
> > > on the ed0 type cards because I use link1 in ifconfig to set it
> > > and most other cards use that for something else like switching
> > > 10BT on/off.
> >
> > Erk.  Do I take it then that it's not possible to do the 802.[23] protocols
> > as well as Ethernet_II simultaneously on the same interface?
> 
> It's possible to receive both types of frames. But how to know
> which kind of encapsulation to use when you SEND the packets ?
> The only way to use both encapsulations I see is to keep a table
> that maps each network address to encapsulation type and fill
> it using the received packets.

This is done by keeping the framing type in an IPX ARP equivalent.

> 
> I've looked ayt the Linux code and it seems to me that they
> just allow the applied software to  decide which encapsulation
> type to use: they just fill the full IPX header (that includes
> Ethernet header) in user-level software rather than in driver.
> It would be not bad to make the IPX implementation more
> Linux-like so it would be easy to port Netware emulators.
> 
> -SB