From owner-freebsd-stable Sat Nov 29 04:40:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA00398 for stable-outgoing; Sat, 29 Nov 1997 04:40:23 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA00386 for ; Sat, 29 Nov 1997 04:40:10 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id MAA24039; Sat, 29 Nov 1997 12:25:40 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199711291225.MAA24039@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mark cc: freebsd-stable@freebsd.org Subject: Re: IPX router problems In-reply-to: Your message of "Wed, 26 Nov 1997 22:08:14 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Nov 1997 12:25:40 +0000 From: Brian Somers Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In message <199711261900.VAA13202@zibbi.mikom.csir.co.za> you wrote: > > > Mark, > > > > > > One problem might be because the FreeBSD IPX code only supports > > > > Ethernet_II framing, which is not the default for Netware servers. > > > > The default for Netware 3.x is 802.3 framing and I think for v4.x > > > > it is 802.2SNAP, but I'm not 100% sure. The easiest if you only > > > > have W95 machines will be to change the server to use Ethernet_II > > > > framing. (The default 95 setup will sense that automatically.) If > > > > you have older Win3.X machines and diskless machines it won't be > > > > that easy. If you can't do Ethernet_II framing, I do have a patch > > > > to enable 802.3 framing on the FreeBSD box. > > > > > > I was incorrectly told that Ethernet II was being used, but infact it's > > > 802.3 (Netware 3.12). I also have the requirement of forwarding IP > > > packets across the two interfaces and I gather from your previous > > > postings on this subject that it's not currently possible to have > > > two frame types on the same interface. Is this still the case? > > > Unfortunately there's no chance of moving to Eth. II. > > > > FreeBSD currently can't do more than one IPX frame type on an interface. > > You can use this patch to be able to do 802.3 on FreeBSD. It provides > > a sysctl to switch between Ethernet_II (default) and 802.3. Remember > > that it will switch it for IPX on all the interfaces. > > > > John > > Many thanks for that John, hopefully that will solve my problem. I was > also hoping to get ipx going over ppp for dial in access. Does pppd or > user ppp support ipx at all? and if so what do I need to do to get it > going? The dial-in machine is also W95. (I have got dial in working already > but only for tcp/ip) I plan to support IPX at some stage (in ppp), but I can't say when. The tun driver needs a bit of work before it can transport non-ip traffic, and I suspect things like divert sockets etc will have to change too. AFAIK, we basically need to prefix the traffic travelling through these ``raw'' mechanisms with at least the sa_family of the message so that the user-program has a chance of knowing what it's reading. > Thanks, > > Mark. > -- > -- Brian , , Don't _EVER_ lose your sense of humour....