From owner-freebsd-net Mon Nov 16 20:55:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13943 for freebsd-net-outgoing; Mon, 16 Nov 1998 20:55:27 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13937 for ; Mon, 16 Nov 1998 20:55:20 -0800 (PST) (envelope-from bp@butya.kz) Received: from localhost (bp@localhost) by lion.butya.kz (8.8.8/8.8.8) with SMTP id IAA06284; Tue, 17 Nov 1998 08:14:11 +0600 (ALMT) Date: Tue, 17 Nov 1998 08:14:11 +0600 (ALMT) From: Boris Popov To: "McKenna, Lee" cc: "'freebsd-net@FreeBSD.ORG'" Subject: RE: Frametypes (was: Re: Netware client for FreeBSD) In-Reply-To: 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 Mon, 16 Nov 1998, McKenna, Lee wrote: > You know...it may be easier just to add support for the additional frame > type to your Novell server :) -- Novell supports multiple frame types > bound to the same adapter for running IPX...beware that this doubles the > SAP/RIP traffic on your net since it does SAPs/RIPs on each frame > type...although I recall you can filter much of the unwanted broadcasts > starting with Novell 4.x?? At this moment this a good solution for many cases. But there always "good old 386" with ipx.com file tuned only for 802.3 frame. In my opinion, it is better to keep separate network configuration for each frame. BTW, netcon supports all of the frames, but as I understand it replace XNS protocol stack. -- Boris Popov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message