From owner-freebsd-hackers Sat Jul 12 20:23:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA02897 for hackers-outgoing; Sat, 12 Jul 1997 20:23:14 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA02892 for ; Sat, 12 Jul 1997 20:23:10 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA01113 for hackers@freebsd.org; Sun, 13 Jul 1997 12:53:08 +0930 (CST) From: Michael Smith Message-Id: <199707130323.MAA01113@genesis.atrad.adelaide.edu.au> Subject: IPX routing? To: hackers@freebsd.org Date: Sun, 13 Jul 1997 12:53:07 +0930 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] 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 Is there a document anywhere which describes the delicacies of setting up a FreeBSD box as an IPX router? I ask as a result of the following scenario, which I had hoped to turn into a minor triumph. A couple of weeks ago, I was contracted by a large secondary college to assemble an SMTP/POP mail server/web cache/web server system for their network of ~150 workstations. Modulo some connectivity problems with their provider, the system has performed faultlessly. Buoyed by this success (in the face of the endless unreliability of the preceeding Netware solution), they asked if the BSD system could be upgraded and used to route their three networks, as well as providing DHCP services for their clients. We installed the ISC DHCP server (and Ted & Paul, if you hear this, _Thankyou_ and congratulations on a fine piece of software!) and verified that it did not exhibit any of the untoward symptoms the Novell server has, and then proceeded to configure the system to route IPX traffic. It was at this point that things came unstuck; adding IPX support to the kernel was quite straightforward, as was assigning IPX addresses to the interface. Except that one can only assign a single net address to each interface, and Netware servers insist on using different net addresses for 802.2 and 802.3 frame types. This isn't discussed in any of the documentation. 8( Next, IPXrouted was started, and in trace mode it was certainly seeing a lot of relevant traffic, but it wasn't learning any routes from it. After much tinkering trying to make various things work, we had to back the system out and reinstate the Novell server, something that neither I nor the customer really wanted to do. So, any suggestions? I could probably be convinced to roll some longer words onthe subject if the information was available... -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[