From owner-freebsd-questions@FreeBSD.ORG Mon Oct 15 23:24:27 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1AC761E4 for ; Mon, 15 Oct 2012 23:24:27 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mail-ia0-f182.google.com (mail-ia0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id D16558FC0A for ; Mon, 15 Oct 2012 23:24:26 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id k10so5426727iag.13 for ; Mon, 15 Oct 2012 16:24:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ACC3KztxkaoBVg4H0HtX3dadevEFNS6KdtI2gXA0HWI=; b=tJAw1QuGAIeVsZeAwOouPqMvMsc+BPx2a1UupHnDh5g41WTXxNEppUsvBYYjdg0Nje MuI5xxiqO1JT1tm9FB1CkIcp7Gm5ZuoN/tC7Yx+WnH0/e5cDE5vyFDqgocVe/Zsqurss gWvlnszO+CZXDwo0DbWWwgoCmRUvRKI0usxS3O+Iy9iZBdC0BS1Jz4TTPM2TyHqe1sBs JtjMlId3x3qD/beGSL65zYAvNyTJ0KiGAUc9zlGPE7mMJoYviFs0WCJLiKxBgvfsnVyN zpg/l6ve3nXvrJJRPELvJxHhmODslLCns74OoFXDl5yRM+aF2qkNwYttm5wDQGbJcZJU PmDQ== MIME-Version: 1.0 Received: by 10.42.80.207 with SMTP id w15mr681446ick.40.1350343465784; Mon, 15 Oct 2012 16:24:25 -0700 (PDT) Received: by 10.64.30.11 with HTTP; Mon, 15 Oct 2012 16:24:25 -0700 (PDT) In-Reply-To: References: Date: Mon, 15 Oct 2012 19:24:25 -0400 Message-ID: Subject: Re: How does freebsd supports ipx? From: "illoai@gmail.com" To: YC Wang Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2012 23:24:27 -0000 On 15 October 2012 02:23, YC Wang wrote: ... > > I rebuilt the kernel with "option IPX", but it didn't seem to work. > Below was what I did: > > 1) create a new configure file IPXKERNEL enabling "option IPX" > freebsd-yc# cat /sys/i386/conf/IPXKERNEL > include GENERIC > ident IPXKERNEL > options IPX > > 2) make buildkerel KERNCONF=IPXKERNEL. When finised, I found that the > ipx source code did get compiled, but hadn't been linked into a kernel > module. > freebsd-yc# find /usr/obj/usr/src/sys/IPXKERNEL/ | grep ipx > /usr/obj/usr/src/sys/IPXKERNEL/modules/usr/src/sys/modules/arcnet/opt_ipx.h > /usr/obj/usr/src/sys/IPXKERNEL/modules/usr/src/sys/modules/if_ef/opt_ipx.h > /usr/obj/usr/src/sys/IPXKERNEL/modules/usr/src/sys/modules/if_tun/opt_ipx.h > /usr/obj/usr/src/sys/IPXKERNEL/modules/usr/src/sys/modules/netgraph/iface/opt_ipx.h > /usr/obj/usr/src/sys/IPXKERNEL/modules/usr/src/sys/modules/smbfs/opt_ipx.h > /usr/obj/usr/src/sys/IPXKERNEL/modules/usr/src/sys/modules/sppp/opt_ipx.h > /usr/obj/usr/src/sys/IPXKERNEL/modules/usr/src/sys/modules/wlan/opt_ipx.h > /usr/obj/usr/src/sys/IPXKERNEL/opt_ipx.h > /usr/obj/usr/src/sys/IPXKERNEL/ipx.o > /usr/obj/usr/src/sys/IPXKERNEL/ipx_cksum.o > /usr/obj/usr/src/sys/IPXKERNEL/ipx_input.o > /usr/obj/usr/src/sys/IPXKERNEL/ipx_outputfl.o > /usr/obj/usr/src/sys/IPXKERNEL/ipx_pcb.o > /usr/obj/usr/src/sys/IPXKERNEL/ipx_proto.o > /usr/obj/usr/src/sys/IPXKERNEL/ipx_usrreq.o > > 3) Still I installed the new kernel with "make installkernel > KERNCONF=IPXKERNEL", and as expected, it was exactly the same to the > old one. > freebsd-yc# ls /boot/kernel > kernel.txt > freebsd-yc# ls /boot/kernel.old/ > kernelold.txt > freebsd-yc# diff kernel.txt kernelold.txt > > So do you have any idea about this? The information of my system is: > freebsd-yc# uname -a > FreeBSD freebsd-yc.vm 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Mon Oct 15 > 11:20:49 CST 2012 > root@freebsd-yc.vm:/usr/obj/usr/src/sys/IPXKERNEL i386 > % kldstat -v | grep ipx might be enlightening. I don't know if you're trying to connect to a netware server, but . . . Back in the old-old days of FreeBSD 4.6 or so, I connected to a netware (4-something, IIRC) server using ipx/spx & ncp (options IPX, options NCP, options NWFS) & it seemed to work pretty well. But I haven't used it since 6.x, & I no longer connect to any netware machines, so I have no idea if it sill works. I believe at the time it may have also required "options LIBMCHAIN" & "options FLOWTABLE", but that might have been a local issue. In the local network, I also had to have ethernet frames compiled in with at a minimum 8023 & SNAP support (& I think ETHER_II for sap/rip): device ef options ETHER_II options ETHER_8023 options ETHER_8022 options ETHER_SNAP (the ifconfig lines get ridiculous after a while) I also believe that nwfs.ko & libmchain.ko could be loaded as modules, but that ncp didn't play nicely when loaded as a module & ipx/spx had to be compiled into the kenel. Good luck. -- --