From owner-freebsd-hackers Tue Jul 15 14:58:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA26761 for hackers-outgoing; Tue, 15 Jul 1997 14:58:38 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA26745 for ; Tue, 15 Jul 1997 14:58:29 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA00460; Tue, 15 Jul 1997 14:57:32 -0700 From: Terry Lambert Message-Id: <199707152157.OAA00460@phaeton.artisoft.com> Subject: Re: IPX routing? To: jhay@mikom.csir.co.za (John Hay) Date: Tue, 15 Jul 1997 14:57:32 -0700 (MST) Cc: julian@whistle.com, hackers@FreeBSD.ORG In-Reply-To: <199707151912.VAA18020@zibbi.mikom.csir.co.za> from "John Hay" at Jul 15, 97 09:12:05 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This is done by keeping the framing type in an IPX ARP equivalent. > > And how do you handle RIP and SAP broadcasts? There may be more than > one router on that segment and they may not use the same framing, eg. > two other routers, one using 802.3 and the other Ethernet_II. As of Netware 3.1, an "internal wire segment" was defined for all routers. Effectively, prior to this, the architecture was: server | | | | net net segment segment 1 2 After this change, the architecture is: server | | --+----+---+--Internal segment | | | | net net segment segment 1 2 Effectively, then, broadcasts are handled as multicasts, and the hop count incremented accordingly (the server broadcasts to the internal segment, and it is "hopped" to each external segment attacked to the machine). A NetWare router, by default, will forward broadcasts up to 16 hops, after which time packets will be dropped. A correct IPX implementation, then, has an "internal network number" which identifies the server, and an "external network number" for each card which identifies the wire segment to which the card has been attached. The default convention for coexistance of IPX and IP networks is to assign the four tuple IP address of the card, minus the netmask, to each card, and the IP address of the machine to the internal segment (any IP address unique to the machine will do). If your IPX stack on your router does not match this description, your implementation is broken. The relevant documents are downloadable from the Utah State University archives (one of the usu.edu servers; I forget which one exactly... use Yahoo or Altavista to find out which one). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.