From owner-freebsd-net Wed Jun 16 9:33:25 1999 Delivered-To: freebsd-net@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id C432614F53 for ; Wed, 16 Jun 1999 09:33:18 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10uIcc-0004TO-00; Wed, 16 Jun 1999 23:33:06 +0700 Date: Wed, 16 Jun 1999 23:33:06 +0700 (ALMST) From: Boris Popov To: "Justin C. Walker" Cc: freebsd-net@FreeBSD.ORG Subject: Re: Multiple ethernet frames for IPX In-Reply-To: <199906161602.JAA00643@walker3.apple.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 16 Jun 1999, Justin C. Walker wrote: > > In case of IPX protocol you have network numbers as a routing and > > forwarding criteria, and since one frame have only one corresponding > > network number it is easy to select outgoing interface. If host have no > > direct connection to destination network it will use routing entries > > gathered from RIP packets. So, it doesn't matter which frame type > was on > > incoming packet. As a special case consider routing between different > > frame types on a single ethernet segment. > I understand how routing works. What I'm missing is how the > sending host (whether originator or forwarder) decides how to > encapsulate a frame, i.e., in your case, how to chose which virtual > device to use. Is it the case that the network number determines the > encapsulation? Is ARP used, and if so, does the ARP reply dictate > how to encapsulate? I'm playing with IP now (and don't like how arp subroutines create packets) so can spoke only for IPX. And yes, you are right - network number determines outgoing interface and, therefore - encapsulation. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message