From owner-freebsd-questions  Fri Apr 26 15:33:05 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA08869
          for questions-outgoing; Fri, 26 Apr 1996 15:33:05 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA08864
          for <questions@FreeBSD.org>; Fri, 26 Apr 1996 15:33:03 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA28112; Fri, 26 Apr 1996 15:28:00 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199604262228.PAA28112@phaeton.artisoft.com>
Subject: Re: TCP/IP questions (not necessarily FreeBSD)
To: PLAZAS_CHRISTIAN@mercury.csg.peachnet.edu (Christian)
Date: Fri, 26 Apr 1996 15:28:00 -0700 (MST)
Cc: questions@FreeBSD.org
In-Reply-To: <E50FAB26F8@mercury.csg.peachnet.edu> from "Christian" at Apr 26, 96 01:38:52 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-questions@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>     I am looking for information regarding the relative strengths of 
> TCP/IP vs. NetBEUI.  I realize that this is not really a FreeBSD 
> question but since I know that many of the people on this list are 
> either very knowledgeable about TCP/IP or have even written code for 
> FreeBSD's implementation of TCP/IP, I thought I'd try here first.
> I'm not necessarily looking for someone to directly answer my 
> question, pointers to further information on this topic would be 
> greatly appreciated.  I would like to have some factual information 
> on this topic because there are these Microsoft-brainwashed weenies 
> here at my school that were claiming that NetBEUI was better than 
> TCP/IP because xxx, and because yyy.  I want to be able to claim that 
> TCP/IP is better because xxx, and also because yyy.  xxx and yyy 
> would of course be reasons provided by somebody on the list or from 
> some other source.

NetBEUI:

	o	existing standard at some sites
	o	do not need to assign network addresses to
		machines; machines self identify
	o	overall simpler clinet configuration

TCP/IP:

	o	can be routed; your machines can be on the
		other side of a router or on an IP tunnel
		over the public internet to create a
		private intranet.
	o	no "broadcast storms"
	o	offensive machines (for whatever reason)
		can be tracked by assigned address
	o	offensive machines can be partitioned at router
		level and identified for illegal use of
		address (security issues, etc.)
	o	Can interconnect easily with internet
	o	Can run most software requiring NetBEUI over
		TCP/IP with simple low level stack change
		(two files publically downladable from the
		ftp.microsoft.com site)
	o	SL/IP or PPP for remote connectivity over
		standard modem lines

That's without listing by drawbacks, which are much larger for
NetBEUI than TCP/IP (example LLC code, etc.).


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.