From owner-freebsd-hackers  Mon Jul 22 21:44:38 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA13652
          for hackers-outgoing; Mon, 22 Jul 1996 21:44:38 -0700 (PDT)
Received: from hq.icb.chel.su (icb-rich-gw.icb.chel.su [193.125.10.34])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA13609
          for <hackers@FreeBSD.org>; Mon, 22 Jul 1996 21:43:53 -0700 (PDT)
Received: (babkin@localhost) by hq.icb.chel.su (8.7.5/8.6.5) id KAA17937; Tue, 23 Jul 1996 10:37:53 +0600 (GMT+0600)
From: "Serge A. Babkin" <babkin@hq.icb.chel.su>
Message-Id: <199607230437.KAA17937@hq.icb.chel.su>
Subject: Re: Ethernet-like loopback & IPX
To: louie@TransSys.COM (Louis A. Mamakos)
Date: Tue, 23 Jul 1996 10:37:52 +0600 (ESD)
Cc: jhay@mikom.csir.co.za, hackers@FreeBSD.org
In-Reply-To: <199607230410.AAA24684@whizzo.transsys.com> from "Louis A. Mamakos" at Jul 23, 96 00:10:32 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > > > By the way, I have fixed the bug (in my opinion) in IPX. It allowed
> > > > > only one link-level (i.e. Ethernet) address for all interfaces.
> > > > > Was it a real bug or feature ?
> > > > > 
> > > > 
> > > > It is a leftover from its XNS days. If you send me the patches for
> > > > IPX, I will look it over and commit it.
> > > 
> > > It's not a bug, but a feature.  Having a single address for your
> > > end-station make quite a few other weirdnesses in the protocol stack
> > > and application just go away.
> > 
> > But if you have a single address you need to set it for all
> > Ethernet cards or they will not accept the packets with this
> > address. The current implementation does not do this and I
> > think that it's not a very good idea.
> 
> Sure, it's true that the current drivers do not allow the MAC address
> to be set on the various LAN interfaces, but this would argue for
> fixing the device drivers, and not the protocol design.

I'm not shure that the ability to change the MAC address accidentally
is good. For example if you configure an interface for IP and then for IPX
you'll get lots of troubles if it sent any ARP response with the
old MAC address.

> While you may believe that the single address per IPX host is an
> error, it is fundamental to the protocol's design.  I wouldn't

Nope. Netware (the "native" protocol implementattion) has different MAC
addresses on different interfaces. Or did you meant the FreeBSD
implementation ?

> characterize changing this as "fixing" it, unless it's the same way a
> veteranarian "fixes" something.

IMHO it _must_ be fixed in any of two ways: by allowing several addresses
or by setting the MAC addresses of cards. But in its current state it
just doesn't allow to have more than one IPX interface.

-SB